March 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4088) Disable session invalidation when redeploying VDB

by Hisanobu Okuda (JIRA)

Hisanobu Okuda created TEIID-4088: ------------------------------------- Summary: Disable session invalidation when redeploying VDB Key: TEIID-4088 URL: https://issues.jboss.org/browse/TEIID-4088 Project: Teiid Issue Type: Feature Request Components: VDB Affects Versions: 8.7.2.6_2 Environment: JDV 6.2.x Reporter: Hisanobu Okuda Assignee: Barry LaFond When redeploying VDB, exisiting sessions are invalidated. Need option to disable session invalidation and keep it alive when redeploying. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4021) MSSQL Pagination

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4021?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4021: ---------------------------------- Component/s: JDBC Connector Fix Version/s: 9.1 > MSSQL Pagination > ---------------- > > Key: TEIID-4021 > URL: https://issues.jboss.org/browse/TEIID-4021 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Reporter: Mark Tawk > Assignee: Steven Hawkins > Fix For: 9.1 > > > I'm using Teiid 8.11.3 with mssql translator. > I have a huge table over sql server 2008 on which i'm applying pagination. > I noticed slowliness in the query execution over this table at each time I increase the pagination. > I monitored the JDBC queries execute by teiid and found out that it is using top n according to the limit used into the query. > For example: > in teiid : Select * from mytable LIMIT 90 , 10 > is translated in JDBC: select top 100 from mytable > Since my table contains millions of records, when fetching the last page, the executed jdbc query is retrieving the whole table top n, to return in result the last 10 records. And the execution is taking too much time. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4078) Oracle translator - query fails - ORA-00979: not a GROUP BY expression

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4078?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4078. ----------------------------------- Resolution: Done Removed the check for nested casts so that the expression is preserved. > Oracle translator - query fails - ORA-00979: not a GROUP BY expression > ---------------------------------------------------------------------- > > Key: TEIID-4078 > URL: https://issues.jboss.org/browse/TEIID-4078 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5 > > > Query: > {code:sql} > SELECT A.INTKEY, A.BOOLEANVALUE FROM BQT1.SMALLA AS A GROUP BY A.INTKEY, A.BOOLEANVALUE HAVING CONVERT(A.BOOLEANVALUE, STRING) >= (SELECT MIN(CONVERT(B.BOOLEANVALUE, STRING)) FROM BQT1.SMALLA AS B WHERE A.INTKEY = B.INTKEY) > {code} > Source specific command: > {code:sql} > SELECT trunc(g_0."INTKEY"), CASE WHEN g_0."BOOLEANVALUE" = 0 THEN 0 WHEN g_0."BOOLEANVALUE" IS NOT NULL THEN 1 END FROM "DV"."SMALLA" g_0 GROUP BY trunc(g_0."INTKEY"), CASE WHEN g_0."BOOLEANVALUE" = 0 THEN 0 WHEN g_0."BOOLEANVALUE" IS NOT NULL THEN 1 END HAVING CASE WHEN g_0."BOOLEANVALUE" = 0 THEN 'false' WHEN g_0."BOOLEANVALUE" IS NOT NULL THEN 'true' END >= (SELECT MIN(CASE WHEN g_1."BOOLEANVALUE" = 0 THEN 'false' WHEN g_1."BOOLEANVALUE" IS NOT NULL THEN 'true' END) FROM "DV"."SMALLA" g_1 WHERE trunc(g_1."INTKEY") = trunc(g_0."INTKEY")) > {code} > Exception: > {code:plain} > 07:59:09,071 WARN [org.teiid.CONNECTOR] (Worker5_QueryProcessorQueue54) Connector worker process failed for atomic-request=gVALrvEkz/+o.7.3.8: org.teiid.translator.jdbc.JDBCExecutionException: 979 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT trunc(g_0."INTKEY"), CASE WHEN g_0."BOOLEANVALUE" = 0 THEN 0 WHEN g_0."BOOLEANVALUE" IS NOT NULL THEN 1 END FROM "DV"."SMALLA" g_0 GROUP BY trunc(g_0."INTKEY"), CASE WHEN g_0."BOOLEANVALUE" = 0 THEN 0 WHEN g_0."BOOLEANVALUE" IS NOT NULL THEN 1 END HAVING CASE WHEN g_0."BOOLEANVALUE" = 0 THEN 'false' WHEN g_0."BOOLEANVALUE" IS NOT NULL THEN 'true' END >= (SELECT MIN(CASE WHEN g_1."BOOLEANVALUE" = 0 THEN 'false' WHEN g_1."BOOLEANVALUE" IS NOT NULL THEN 'true' END) FROM "DV"."SMALLA" g_1 WHERE trunc(g_1."INTKEY") = trunc(g_0."INTKEY"))] > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.12.5.redhat-2.jar:8.12.5.redhat-2] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:359) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0-internal] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0-internal] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0-internal] > at java.lang.reflect.Method.invoke(Method.java:483) [rt.jar:1.8.0-internal] > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) > at com.sun.proxy.$Proxy22.execute(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0-internal] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0-internal] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0-internal] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0-internal] > Caused by: java.sql.SQLSyntaxErrorException: ORA-00979: not a GROUP BY expression > at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:450) > at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399) > at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1059) > at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:522) > at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:257) > at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:587) > at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:225) > at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:53) > at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:774) > at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:925) > at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1111) > at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:4798) > at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:4845) > at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1501) > at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:462) > at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:123) [translator-jdbc-8.12.5.redhat-2.jar:8.12.5.redhat-2] > ... 18 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3968) OData 4 array type handling

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3968?page=com.atlassian.jira.plugin... ] Work on TEIID-3968 started by Ramesh Reddy. ------------------------------------------- > OData 4 array type handling > --------------------------- > > Key: TEIID-3968 > URL: https://issues.jboss.org/browse/TEIID-3968 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.0, 8.12.5 > > > To ensure we are appropriate returning the correct error messages, creating the right upstream changes, etc. we have several paths to validate wrt array handling. There are: > In the translator - ODataProcedureExecution.getQueryParameters, ODataFilterVisitor.visit(Function) and ODataFilterVisitor.visit(ColumnReference), ODataExpressionToSQLVisitor.visitAlias, ODataUpdateVisitor.visit(Update) > In the OData service - ODataExpressionToSQLVisitor.visit(Alias) > From the spec it appears that a uri should be able to specify arrays, but olingo and other frameworks may have limitations. For example it should be possible to have an array argument to a function, but the olingo framework will complain that arrays are not allowed in the resource part of the uri. > At the very least we'll capture what won't work with this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3968) OData 4 array type handling

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3968?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3968: -------------------------------- Fix Version/s: 9.0 8.12.5 > OData 4 array type handling > --------------------------- > > Key: TEIID-3968 > URL: https://issues.jboss.org/browse/TEIID-3968 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5 > > > To ensure we are appropriate returning the correct error messages, creating the right upstream changes, etc. we have several paths to validate wrt array handling. There are: > In the translator - ODataProcedureExecution.getQueryParameters, ODataFilterVisitor.visit(Function) and ODataFilterVisitor.visit(ColumnReference), ODataExpressionToSQLVisitor.visitAlias, ODataUpdateVisitor.visit(Update) > In the OData service - ODataExpressionToSQLVisitor.visit(Alias) > From the spec it appears that a uri should be able to specify arrays, but olingo and other frameworks may have limitations. For example it should be possible to have an array argument to a function, but the olingo framework will complain that arrays are not allowed in the resource part of the uri. > At the very least we'll capture what won't work with this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3906) OData v4 - definition of OData-Isolation header is either being ignored or is not implemented correctly

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3906?page=com.atlassian.jira.plugin... ] Work on TEIID-3906 started by Ramesh Reddy. ------------------------------------------- > OData v4 - definition of OData-Isolation header is either being ignored or is not implemented correctly > ------------------------------------------------------------------------------------------------------- > > Key: TEIID-3906 > URL: https://issues.jboss.org/browse/TEIID-3906 > Project: Teiid > Issue Type: Sub-task > Components: OData > Affects Versions: 8.12.3 > Environment: Teiid - OData v4 > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > Fix For: 9.0, 8.12.5 > > > Teiid does not process header *OData-Isolation: snapshot* defined in request correctly. > * if service (Teiid) does not support this option it must return error 412 > * if Teiid does supports this option then it is not processed correctly, because modifications made during request are visbile > See http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-pr... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-3906) OData v4 - definition of OData-Isolation header is either being ignored or is not implemented correctly

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3906?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-3906: -------------------------------- Fix Version/s: 9.0 8.12.5 > OData v4 - definition of OData-Isolation header is either being ignored or is not implemented correctly > ------------------------------------------------------------------------------------------------------- > > Key: TEIID-3906 > URL: https://issues.jboss.org/browse/TEIID-3906 > Project: Teiid > Issue Type: Sub-task > Components: OData > Affects Versions: 8.12.3 > Environment: Teiid - OData v4 > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > Fix For: 9.0, 8.12.5 > > > Teiid does not process header *OData-Isolation: snapshot* defined in request correctly. > * if service (Teiid) does not support this option it must return error 412 > * if Teiid does supports this option then it is not processed correctly, because modifications made during request are visbile > See http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-pr... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4086) OData - Math functions floor and ceiling doesn't accept number as parameter

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4086?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4086: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1318434 Bugzilla Update: Perform > OData - Math functions floor and ceiling doesn't accept number as parameter > --------------------------------------------------------------------------- > > Key: TEIID-4086 > URL: https://issues.jboss.org/browse/TEIID-4086 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Michal Sanitrak > Assignee: Ramesh Reddy > > Basic functionality of math functions floor and ceiling works properly as \[1\] describes, but these functions doesn't accept number as parameter. > Reference service which supports OData V4: > *ULR:* http://services.odata.org/V4/Northwind/Northwind.svc/Employees/?$filter=E... > *Result:* Employee with ID 4 > *ULR:* http://localhost:8080/odata4/olingo_basic/Source/SimpleTableView/?$filter... > *Actual result:* {"error":{"code": null, "message": "TEIID30069 The function 'FLOOR(\?)' has more than one possible signature."}} > *Expected result:* Entity with intkey 4 > *ULR:* http://localhost:8080/odata4/olingo_basic/Source/SimpleTableView/?$filter... > *Actual result:* {"error": {"code": null, "message": "TEIID30069 The function 'CEILING(\?)' has more than one possible signature."}} > *Expected result:* Entity with intkey 5 > See [\[OData-ABNF\]|http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/abnf/odata-abnf-construction-rules.txt] _Line:_ 539 - Math functions accepts _commonExpr_ > \[1\] http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part2-ur... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4085) OData doesn't support mulitiple usage of arithmetic operators

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4085?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4085: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1318433 Bugzilla Update: Perform > OData doesn't support mulitiple usage of arithmetic operators > -------------------------------------------------------------- > > Key: TEIID-4085 > URL: https://issues.jboss.org/browse/TEIID-4085 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Michal Sanitrak > Assignee: Ramesh Reddy > > Cannot use more than one arithmetic operator in single OData query. Each arithmetic operator has same problem: add,sub,mul,div and mod. > *URL:* http://localhost:8080/odata4/olingo_basic/Source/SimpleTableView/?$filter... > *Actual result:* {"error":{"code": null,"message": "TEIID30067 Type was null for (? + ?) in function ((? + ?) + ?)"}} > *Expected result:* Entity with intkey 7 > See: [\[OData-ABNF\]|http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/abnf/odata-abnf-construction-rules.txt] _Line:_ 384 and 561 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIID-4087) OData - Math function round doesn't accept decimal number as parameter

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4087?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4087: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1318435 Bugzilla Update: Perform > OData - Math function round doesn't accept decimal number as parameter > ---------------------------------------------------------------------- > > Key: TEIID-4087 > URL: https://issues.jboss.org/browse/TEIID-4087 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Michal Sanitrak > Assignee: Ramesh Reddy > > Reference service which supports OData V4: > *ULR:* http://services.odata.org/V4/Northwind/Northwind.svc/Employees/?$filter=E... > *Result:* Employee with ID 4 > *URL:* http://localhost:8080/odata4/olingo_basic/Source/SimpleTableView/?$filter... > *Actual result:* {"error": {"code": null, "message": "TEIID30558 Error converting parameter number 1 with value \"4,2\" of class java.math.BigDecimal to expected type integer." }} > *Expected result:* Entity with intkey 4 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2016