March 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4829) odata4 fails to return data on top of mongoDB view model

by Michael Echevarria (JIRA)

[ https://issues.jboss.org/browse/TEIID-4829?page=com.atlassian.jira.plugin... ] Michael Echevarria commented on TEIID-4829: ------------------------------------------- Yeah verified with odata2-works screenshot. Whats odd is that odata4 is the only thing checking that length. jdbc, preview and odata2 had no issue with the zero length > odata4 fails to return data on top of mongoDB view model > --------------------------------------------------------- > > Key: TEIID-4829 > URL: https://issues.jboss.org/browse/TEIID-4829 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.9.6_3 > Environment: Noticed in JDV 6.3.4 > Reporter: Michael Echevarria > Assignee: Steven Hawkins > Priority: Critical > Attachments: Screenshot from 2017-03-28 15-38-25.png, Screenshot from 2017-03-28 15-38-32.png, Screenshot from 2017-03-28 15-38-46.png, Screenshot from 2017-03-28 15-38-56.png, mongo-view-error.png, odata2-works.png, odata4-error.png > > > Description of problem: > Accessing either an exclusive view model or combined view model for a mongoDB datasource via odata4 results in an error. > The data returns via odata2, jdbc and preview in the designer > Version-Release number of selected component (if applicable): > JDV 6.3.4 > Actual results: > Property mapping error > Expected results: > Model data -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4835) Implement column level incoming dependencies

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4835: ------------------------------------- Summary: Implement column level incoming dependencies Key: TEIID-4835 URL: https://issues.jboss.org/browse/TEIID-4835 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.3 The original implementation of the usage table did not implement the ElementName column. Additional logic will be needed in the metadatavalidator to determine what contributes to the column. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4661) Subsequent queries hang after materialized view TTL expires.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4661?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4661. ----------------------------------- Resolution: Done > Subsequent queries hang after materialized view TTL expires. > ------------------------------------------------------------ > > Key: TEIID-4661 > URL: https://issues.jboss.org/browse/TEIID-4661 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12.x > Reporter: Colin Mondesir > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.12.10.6_3, 9.2, 9.1.2, 9.0.6 > > > With a VDB using lazy-invalidate in a clustered configuration initially the materialized view is cached correctly but when the TTL expires (10 minutes) and the query is run again the state of the view changes to LOADING and never reverts to "LOADED", so the next query hangs. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4834) Wrong pushdown of ST_Touches to Oracle

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4834?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4834: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1397953 Bugzilla Update: Perform > Wrong pushdown of ST_Touches to Oracle > -------------------------------------- > > Key: TEIID-4834 > URL: https://issues.jboss.org/browse/TEIID-4834 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 9.3, 8.12.10.6_3 > Reporter: Andrej Šmigala > Assignee: Steven Hawkins > > The ST_Touches is currently pushed down as SDO_TOUCHES to Oracle, however, the correct function name is SDO_TOUCH. > http://docs.oracle.com/database/121/SPATL/GUID-93B1E298-BE8D-45B9-A1D4-9B... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4833) Oracle JDBC Connector: Support for LISTAGG

by John Rodrigues (JIRA)

[ https://issues.jboss.org/browse/TEIID-4833?page=com.atlassian.jira.plugin... ] John Rodrigues updated TEIID-4833: ---------------------------------- Component/s: JDBC Connector (was: JDG Connector) > Oracle JDBC Connector: Support for LISTAGG > ------------------------------------------ > > Key: TEIID-4833 > URL: https://issues.jboss.org/browse/TEIID-4833 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Reporter: John Rodrigues > Assignee: Steven Hawkins > > Add support for the Oracle LISTAGG function to the Teiid Oracle connector. > Refer to this discussion for context: [OracleConnector LISTAGG function|https://developer.jboss.org/message/970282] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4834) Wrong pushdown of ST_Touches to Oracle

by Andrej Šmigala (JIRA)

Andrej Šmigala created TEIID-4834: ------------------------------------- Summary: Wrong pushdown of ST_Touches to Oracle Key: TEIID-4834 URL: https://issues.jboss.org/browse/TEIID-4834 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 9.3, 8.12.10.6_3 Reporter: Andrej Šmigala Assignee: Steven Hawkins The ST_Touches is currently pushed down as SDO_TOUCHES to Oracle, however, the correct function name is SDO_TOUCH. http://docs.oracle.com/database/121/SPATL/GUID-93B1E298-BE8D-45B9-A1D4-9B... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4833) Oracle JDBC Connector: Support for LISTAGG

by John Rodrigues (JIRA)

John Rodrigues created TEIID-4833: ------------------------------------- Summary: Oracle JDBC Connector: Support for LISTAGG Key: TEIID-4833 URL: https://issues.jboss.org/browse/TEIID-4833 Project: Teiid Issue Type: Feature Request Components: JDG Connector Reporter: John Rodrigues Assignee: Steven Hawkins Add support for the Oracle LISTAGG function to the Teiid Oracle connector. Refer to this discussion for context: [OracleConnector LISTAGG function|https://developer.jboss.org/message/970282] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4595) Wrong pushdown of several spatial functions to Oracle

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4595?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4595: ---------------------------------- Component/s: JDBC Connector > Wrong pushdown of several spatial functions to Oracle > ----------------------------------------------------- > > Key: TEIID-4595 > URL: https://issues.jboss.org/browse/TEIID-4595 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.12.x > Reporter: Andrej Šmigala > Assignee: Steven Hawkins > Fix For: 9.1.2, 9.2, 8.12.10.6_3 > > > There are several geospatial functions that are wrongly pushed down to oracle > # {{ST_DISTANCE}} is pushed as {{SDO_GEOM.DISTANCE}} which does not exist, should be {{SDO_GEOM.SDO_DISTANCE}}. This results in runtime error. > # {{ST_CROSSES}} and {{ST_OVERLAPS}} are both pushed as {{SDO_RELATE}} with mask {{"overlapbydisjoint"}} which does not exists, should be {{"overlapbdydisjoint"}} (sic} for {{ST_CROSSES}} and {{"overlapbdyintersect"}} for {{ST_OVERLAPS}}. This results in {{false}} being returned for all calls to the two functions > # Using {{ST_DISJOINT}} in the select clause (but not in criteria) results in the following error when evaluating to true: > {noformat} > org.teiid.jdbc.TeiidSQLException: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 SpatialModel: 99999 Unexpected exception while translating results: Fail to convert to internal representation > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135) > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71) > at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:706) > at org.teiid.jdbc.StatementImpl.access$100(StatementImpl.java:64) > at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:545) > at org.teiid.client.util.ResultsFuture.done(ResultsFuture.java:135) > at org.teiid.client.util.ResultsFuture.access$200(ResultsFuture.java:40) > at org.teiid.client.util.ResultsFuture$1.receiveResults(ResultsFuture.java:79) > at org.teiid.net.socket.SocketServerInstanceImpl.receivedMessage(SocketServerInstanceImpl.java:268) > at org.teiid.net.socket.SocketServerInstanceImpl.read(SocketServerInstanceImpl.java:306) > at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.teiid.net.socket.SocketServerConnectionFactory$ShutdownHandler.invoke(SocketServerConnectionFactory.java:98) > at com.sun.proxy.$Proxy18.read(Unknown Source) > at org.teiid.net.socket.SocketServerInstanceImpl$RemoteInvocationHandler$1.get(SocketServerInstanceImpl.java:405) > at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:554) > at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:1060) > at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:323) > at org.jboss.bqt.framework.AbstractQuery.execute(AbstractQuery.java:208) > at org.jboss.bqt.client.testcase.ProcessResults.executeTest(ProcessResults.java:280) > at org.jboss.bqt.client.testcase.ProcessResults.runTestCase(ProcessResults.java:166) > at org.jboss.bqt.client.TestClient.runScenario(TestClient.java:209) > at org.jboss.bqt.client.TestClient.runTest(TestClient.java:132) > at org.jboss.bqt.client.TestClient.runTest(TestClient.java:113) > at org.jboss.qe.bqt.BQTHelper.startTest(BQTHelper.java:59) > at org.jboss.dv.test.bqt.Utils.runScenarioTest(Utils.java:185) > at org.jboss.dv.test.bqt.TestPassRDBMS.testRdbms(TestPassRDBMS.java:210) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:86) > at org.testng.internal.MethodInvocationHelper$1.runTestMethod(MethodInvocationHelper.java:197) > at org.jboss.qe.DVQETestListener.run(DVQETestListener.java:266) > at org.testng.internal.MethodInvocationHelper.invokeHookable(MethodInvocationHelper.java:209) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:639) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:820) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1128) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112) > at org.testng.TestRunner.privateRun(TestRunner.java:782) > at org.testng.TestRunner.run(TestRunner.java:632) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:366) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319) > at org.testng.SuiteRunner.run(SuiteRunner.java:268) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1169) > at org.testng.TestNG.run(TestNG.java:1064) > at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:70) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:108) > at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:111) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:172) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:104) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:70) > Caused by: org.teiid.core.TeiidProcessingException: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 SpatialModel: 99999 Unexpected exception while translating results: Fail to convert to internal representation > at org.teiid.dqp.internal.process.DataTierTupleSource.exceptionOccurred(DataTierTupleSource.java:401) > at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:161) > at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:391) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282) > at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145) > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146) > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:472) > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:348) > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:274) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:280) > 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) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.teiid.core.TeiidException: 99999 Remote org.teiid.translator.TranslatorException: 99999 Unexpected exception while translating results: Fail to convert to internal representation > at org.teiid.translator.jdbc.JDBCQueryExecution.next(JDBCQueryExecution.java:351) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:436) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:236) > at sun.reflect.GeneratedMethodAccessor88.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) > at com.sun.proxy.$Proxy47.more(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:309) > 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) > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) > ... 6 more > Caused by: java.sql.SQLException: Remote java.sql.SQLException: Fail to convert to internal representation > at oracle.jdbc.driver.CharCommonAccessor.getBoolean(CharCommonAccessor.java:183) > at oracle.jdbc.driver.GeneratedStatement.getBoolean(GeneratedStatement.java:129) > at oracle.jdbc.driver.GeneratedScrollableResultSet.getBoolean(GeneratedScrollableResultSet.java:232) > at org.jboss.jca.adapters.jdbc.WrappedResultSet.getBoolean(WrappedResultSet.java:594) > at org.teiid.translator.jdbc.JDBCExecutionFactory.retrieveValue(JDBCExecutionFactory.java:1068) > at org.teiid.translator.jdbc.JDBCQueryExecution.next(JDBCQueryExecution.java:344) > ... 18 more > {noformat} > This is because it is pushed down as {{SDO_GEOM.RELATE}} with mask {{"disjoint"}}, which in oracle returns the string {{'DISJOINT'}} instead of the more expected {{'TRUE'}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4829) odata4 fails to return data on top of mongoDB view model

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4829?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4829: --------------------------------------- Have you verified the workaround? If so from here this issue should be changed to verify the mongodb import behavior, and spawn a Teiid designer validation issue for 0 length string columns. > odata4 fails to return data on top of mongoDB view model > --------------------------------------------------------- > > Key: TEIID-4829 > URL: https://issues.jboss.org/browse/TEIID-4829 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.9.6_3 > Environment: Noticed in JDV 6.3.4 > Reporter: Michael Echevarria > Assignee: Steven Hawkins > Priority: Critical > Attachments: Screenshot from 2017-03-28 15-38-25.png, Screenshot from 2017-03-28 15-38-32.png, Screenshot from 2017-03-28 15-38-46.png, Screenshot from 2017-03-28 15-38-56.png, mongo-view-error.png, odata2-works.png, odata4-error.png > > > Description of problem: > Accessing either an exclusive view model or combined view model for a mongoDB datasource via odata4 results in an error. > The data returns via odata2, jdbc and preview in the designer > Version-Release number of selected component (if applicable): > JDV 6.3.4 > Actual results: > Property mapping error > Expected results: > Model data -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4661) Subsequent queries hang after materialized view TTL expires.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4661?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4661: --------------------------------------- The integration test without the patch does reproduce the issue, so that is probably sufficient to mark this as resolved. For materialization, resultset-repl is not involved - jgroups is used directly. > Subsequent queries hang after materialized view TTL expires. > ------------------------------------------------------------ > > Key: TEIID-4661 > URL: https://issues.jboss.org/browse/TEIID-4661 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12.x > Reporter: Colin Mondesir > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.0.6, 9.1.2, 9.2, 8.12.10.6_3 > > > With a VDB using lazy-invalidate in a clustered configuration initially the materialized view is cached correctly but when the TTL expires (10 minutes) and the query is run again the state of the view changes to LOADING and never reverts to "LOADED", so the next query hangs. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2017