[JBoss JIRA] (TEIID-5136) Osisoft translator - NPE when running query with LATERAL JOIN
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-5136?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-5136:
------------------------------------------------
David Le Sage <dlesage(a)redhat.com> changed the Status of [bug 1509928|https://bugzilla.redhat.com/show_bug.cgi?id=1509928] from NEW to ON_QA
> Osisoft translator - NPE when running query with LATERAL JOIN
> -------------------------------------------------------------
>
> Key: TEIID-5136
> URL: https://issues.jboss.org/browse/TEIID-5136
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Reporter: Andrej Šmigala
> Assignee: Ramesh Reddy
> Fix For: 10.1
>
>
> Running the following query:
> {code:sql}
> SELECT bqt2.smalla.intkey, g2.intkey, bqt2.smalla.bytenum FROM bqt2.smalla LEFT JOIN LATERAL (SELECT intkey FROM bqt2.mediuma WHERE bqt2.smalla.bytenum = bqt2.mediuma.bytenum) AS g2 ON true
> {code}
> results in a NPE in teiid (before sending source src command).
> Stacktrace:
> {noformat}
> Connector worker process failed for atomic-request=vEbs99yd+srV.1.0.1: java.lang.NullPointerException
> at org.teiid.translator.jdbc.pi.PIExecutionFactory.translate(PIExecutionFactory.java:273) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4]
> at org.teiid.translator.jdbc.SQLConversionVisitor.append(SQLConversionVisitor.java:111) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4]
> at org.teiid.language.visitor.SQLStringVisitor.append(SQLStringVisitor.java:106) [teiid-api-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.language.visitor.SQLStringVisitor.visit(SQLStringVisitor.java:767) [teiid-api-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.language.Select.acceptVisitor(Select.java:110) [teiid-api-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.language.visitor.AbstractLanguageVisitor.visitNode(AbstractLanguageVisitor.java:51) [teiid-api-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.language.visitor.SQLStringVisitor.append(SQLStringVisitor.java:91) [teiid-api-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7]
> at org.teiid.translator.jdbc.SQLConversionVisitor.append(SQLConversionVisitor.java:130) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4]
> at org.teiid.translator.jdbc.TranslatedCommand.translateCommand(TranslatedCommand.java:76) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4]
> at org.teiid.translator.jdbc.JDBCBaseExecution.translateCommand(JDBCBaseExecution.java:120) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:114) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:363)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_141]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_141]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_141]
> at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_141]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
> at com.sun.proxy.$Proxy79.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_141]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:284)
> 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:1149) [rt.jar:1.8.0_141]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_141]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_141]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (TEIID-5172) Missing message for key "TEIID31262"
by Andrej Šmigala (JIRA)
Andrej Šmigala created TEIID-5172:
-------------------------------------
Summary: Missing message for key "TEIID31262"
Key: TEIID-5172
URL: https://issues.jboss.org/browse/TEIID-5172
Project: Teiid
Issue Type: Bug
Affects Versions: 8.12.x-6.4
Reporter: Andrej Šmigala
Assignee: Steven Hawkins
When creating tests for TEIID-4557, I ran into missing message for an exception:
{noformat}
[org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue200) TEIID30019 Unexpected exception for request oekxHV8aThTk.100: org.teiid.core.TeiidComponentException: TEIID31261 TEIID31262 <Missing message for key "TEIID31262" in: org.teiid.query.i18n>
{noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (TEIID-5159) Quickstart hibernate-on-top-of-teiid usability issues
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-5159?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-5159:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1514849|https://bugzilla.redhat.com/show_bug.cgi?id=1514849] from NEW to MODIFIED
> Quickstart hibernate-on-top-of-teiid usability issues
> -----------------------------------------------------
>
> Key: TEIID-5159
> URL: https://issues.jboss.org/browse/TEIID-5159
> Project: Teiid
> Issue Type: Bug
> Components: Quick Starts
> Affects Versions: 8.12.x-6.4
> Reporter: Jan Stastny
> Assignee: Van Halbert
> Fix For: 8.12.x-6.4, 10.x
>
>
> There are two usability issues:
> 1. we're reusing Portfolio vdb. The thing is, that if user performed also dynamicvdb-dataroles quickstart, the Portfolio vdb will have limitations on data access. So it is crucial, for the functionality of hibernate qs for user to provide correct credentials. It has to be credentials allowing read access for the example query in the end.
> 2. mvn package is enough, no need for mvn install when building WAR file
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (TEIID-5171) Forward navigation of expand returns wrong results.
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-5171:
-------------------------------------
Summary: Forward navigation of expand returns wrong results.
Key: TEIID-5171
URL: https://issues.jboss.org/browse/TEIID-5171
Project: Teiid
Issue Type: Bug
Components: OData
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 9.3.6, 10.1, 10.0.1
On a self relationship expand, the reverse navigation will return the correct result:
Employee?$expand=Employee_FK0
But the same result will be returned for the forward as well:
Employee?$expand=FK0
The logic is not differentiating between the directions.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (TEIID-4397) Allow $it to be used in expand
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4397?page=com.atlassian.jira.plugin... ]
Steven Hawkins edited comment on TEIID-4397 at 11/27/17 12:52 PM:
------------------------------------------------------------------
> I don't think so. It should apply to the expanded entity, not the parent. I know there were several issues with self relationships and predicates. I'll double check this behavior in the upstream.
Employee_FK0 is the reverse navigation, FK0 is the forward navigation.
Employee?$expand=Employee_FK0($filter=$it/name%20eq%20%27president%27) should mean navigating from the pk. The expected result would expand all employees of an employee who has a name of president. This is functioning as expected.
Employee?$expand=FK0($filter=$it/name%20eq%20%27president%27) should mean navigating from the fk. The expected result would expand the manager of employees who have a name of president. This later case is not working correctly.
was (Author: shawkins):
> I don't think so. It should apply to the expanded entity, not the parent. I know there were several issues with self relationships and predicates. I'll double check this behavior in the upstream.
Employee_FK0 is the reverse navigation, FK0 is the forward navigation.
Employee?$expand=Employee_FK0 should mean navigating from the pk - so the iterator would reference the employees.
The expected result would expand all employees who have an employee with the name president.
Employee?$expand=FK0 should mean navigating from the fk - so the iterator would reference the manager.
The expected result would expand all employees who have a manager with the name president.
I don't think either of these are working as expected for a self relationship.
> Allow $it to be used in expand
> ------------------------------
>
> Key: TEIID-4397
> URL: https://issues.jboss.org/browse/TEIID-4397
> Project: Teiid
> Issue Type: Sub-task
> Components: OData
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.1, 8.12.x-6.4
>
>
> It should be possible to use $it in expand for correlated references.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month