[JBoss JIRA] (TEIID-4865) DISTINCT not pushed down to multisource sources
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4865?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4865:
----------------------------------
Issue Type: Enhancement (was: Bug)
Description:
Simple DISTINCT queries do not push down DISTINCT to the underlying sources (SQL Server, in this case) of a multisource schema. Instead, all values are selected, and the sorting out is done in teiid.
{noformat}
select distinct bic_status
from account;
{noformat}
Debug plan attached.
This is an enhancement request to support partial distinct pushdown in the multi-source case.
was:
Simple DISTINCT queries do not push down DISTINCT to the underlying sources (SQL Server, in this case) of a multisource schema. Instead, all values are selected, and the sorting out is done in teiid.
{noformat}
select distinct bic_status
from account;
{noformat}
Debug plan attached.
Ok, this has been updated to an enhancement.
As a workaround, you should be able to use a grouping instead:
select bic_status from account group by bic_status
> DISTINCT not pushed down to multisource sources
> -----------------------------------------------
>
> Key: TEIID-4865
> URL: https://issues.jboss.org/browse/TEIID-4865
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Affects Versions: 9.2.2
> Reporter: Harold Campbell
> Assignee: Steven Hawkins
> Attachments: DEBUG_LOG
>
>
> Simple DISTINCT queries do not push down DISTINCT to the underlying sources (SQL Server, in this case) of a multisource schema. Instead, all values are selected, and the sorting out is done in teiid.
> {noformat}
> select distinct bic_status
> from account;
> {noformat}
> Debug plan attached.
> This is an enhancement request to support partial distinct pushdown in the multi-source case.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4865) DISTINCT not pushed down to multisource sources
by Harold Campbell (JIRA)
[ https://issues.jboss.org/browse/TEIID-4865?page=com.atlassian.jira.plugin... ]
Harold Campbell commented on TEIID-4865:
----------------------------------------
The latter, yes. I'm dealing with millions of rows, so not doing an initial distinct at the lowest level is a pretty drastic performance hit.
> DISTINCT not pushed down to multisource sources
> -----------------------------------------------
>
> Key: TEIID-4865
> URL: https://issues.jboss.org/browse/TEIID-4865
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.2.2
> Reporter: Harold Campbell
> Assignee: Steven Hawkins
> Attachments: DEBUG_LOG
>
>
> Simple DISTINCT queries do not push down DISTINCT to the underlying sources (SQL Server, in this case) of a multisource schema. Instead, all values are selected, and the sorting out is done in teiid.
> {noformat}
> select distinct bic_status
> from account;
> {noformat}
> Debug plan attached.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4865) DISTINCT not pushed down to multisource sources
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4865?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4865:
---------------------------------------
Or are you requesting an enhancement for this case handling similar to the aggregate decomposition, such that the distinct is both pushed and processed again in the engine?
> DISTINCT not pushed down to multisource sources
> -----------------------------------------------
>
> Key: TEIID-4865
> URL: https://issues.jboss.org/browse/TEIID-4865
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.2.2
> Reporter: Harold Campbell
> Assignee: Steven Hawkins
> Attachments: DEBUG_LOG
>
>
> Simple DISTINCT queries do not push down DISTINCT to the underlying sources (SQL Server, in this case) of a multisource schema. Instead, all values are selected, and the sorting out is done in teiid.
> {noformat}
> select distinct bic_status
> from account;
> {noformat}
> Debug plan attached.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4865) DISTINCT not pushed down to multisource sources
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4865?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4865:
---------------------------------------
Is bic_status the partitioning column? If not, then we'll have to process the distinct in the Teiid layer.
> DISTINCT not pushed down to multisource sources
> -----------------------------------------------
>
> Key: TEIID-4865
> URL: https://issues.jboss.org/browse/TEIID-4865
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.2.2
> Reporter: Harold Campbell
> Assignee: Steven Hawkins
> Attachments: DEBUG_LOG
>
>
> Simple DISTINCT queries do not push down DISTINCT to the underlying sources (SQL Server, in this case) of a multisource schema. Instead, all values are selected, and the sorting out is done in teiid.
> {noformat}
> select distinct bic_status
> from account;
> {noformat}
> Debug plan attached.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4865) DISTINCT not pushed down to multisource sources
by Harold Campbell (JIRA)
Harold Campbell created TEIID-4865:
--------------------------------------
Summary: DISTINCT not pushed down to multisource sources
Key: TEIID-4865
URL: https://issues.jboss.org/browse/TEIID-4865
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 9.2.2
Reporter: Harold Campbell
Assignee: Steven Hawkins
Attachments: DEBUG_LOG
Simple DISTINCT queries do not push down DISTINCT to the underlying sources (SQL Server, in this case) of a multisource schema. Instead, all values are selected, and the sorting out is done in teiid.
{noformat}
select distinct bic_status
from account;
{noformat}
Debug plan attached.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4860) OData4 swallowing exception message
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4860?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4860:
-------------------------------------
Added and fixed in Olingo community with https://issues.apache.org/jira/browse/OLINGO-1112 this update will be available with 4.4.0 update.
In 6.3, If this bug cannot be workaround then I will update the Teiid's Olingo repo for the fix.
> OData4 swallowing exception message
> -----------------------------------
>
> Key: TEIID-4860
> URL: https://issues.jboss.org/browse/TEIID-4860
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.12.6.6_3
> Environment: JDV 6.3.2
> Windows 7
> Reporter: Steve Tran
> Assignee: Steven Hawkins
> Attachments: odata2_error_msg.png, odata4_error_msg.png
>
>
> The error message is being swallowed when accessing an endpoint via OData4. A much more useful message get displayed when accessing the same table via the OData2 interface. I'm assuming the same error message (or better) should be displayed via the version 4 interface.
> Here's the stacktrace when reproducing the error for OData4
> {code}
> 17:59:03,779 ERROR [org.teiid.ODATA] (http-0.0.0.0:8080-2) TEIID16052 Unable to process odata request due to: OData Library: An exception without message text was thrown.: org.apache.olingo.server.api.ODataApplicationException
> at org.teiid.olingo.service.TeiidServiceHandler.read(TeiidServiceHandler.java:174) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.apache.olingo.server.core.requests.DataRequest$EntityRequest.execute(DataRequest.java:332)
> at org.apache.olingo.server.core.requests.DataRequest.execute(DataRequest.java:255)
> at org.apache.olingo.server.core.ServiceDispatcher.internalExecute(ServiceDispatcher.java:160)
> at org.apache.olingo.server.core.ServiceDispatcher.execute(ServiceDispatcher.java:98)
> at org.apache.olingo.server.core.OData4HttpHandler.process(OData4HttpHandler.java:66)
> at org.teiid.olingo.web.ODataServlet.service(ODataServlet.java:43) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-2.jar:1.0.2.Final-redhat-2]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.teiid.olingo.web.ODataFilter.internalDoFilter(ODataFilter.java:231) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.teiid.olingo.web.ODataFilter.doFilter(ODataFilter.java:100) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.teiid.olingo.web.CorsFilter.doFilter(CorsFilter.java:80) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:512) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:150) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:854) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_121]
> Caused by: java.lang.NullPointerException
> at org.teiid.olingo.service.EntityCollectionResponse.isSameRow(EntityCollectionResponse.java:180) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.teiid.olingo.service.EntityCollectionResponse.isSameEntity(EntityCollectionResponse.java:154) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.teiid.olingo.service.LocalClient.executeSQL(LocalClient.java:280) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.teiid.olingo.service.TeiidServiceHandler.executeQuery(TeiidServiceHandler.java:349) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.teiid.olingo.service.TeiidServiceHandler.read(TeiidServiceHandler.java:172) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> ... 28 more
> {code}
> And here's the stack trace when reproduced from the OData 2 interface.
> {code}
> 18:01:20,885 WARN [org.teiid.ODATA] (http-0.0.0.0:8080-2) TEIID16012 Could not produce a successful OData response. Returning status ServerErrorException with message Complex key values cannot be null.
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4854) Google translator fails to update timestamp value reformatted after update
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4854?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4854:
----------------------------------
Fix Version/s: 9.3
> Google translator fails to update timestamp value reformatted after update
> --------------------------------------------------------------------------
>
> Key: TEIID-4854
> URL: https://issues.jboss.org/browse/TEIID-4854
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 9.3, 8.12.10.6_3
> Reporter: Lucie Fabrikova
> Assignee: Steven Hawkins
> Fix For: 9.3
>
> Attachments: gs-reformatted-timestamp.log
>
>
> Cell of type timestamp is reformatted after an update. Data inserted from teiid are in format "yyyy-mm-dd hh:mm:ss[.fffffffff]", which is reformatted to "dd/mm/yyyy hh:mm:ss[.fffffffff]". Subsequent update of such row throws exception "Could not convert source column Source.smalla.timestampvalue to the expected runtime type timestamp".
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4860) OData4 swallowing exception message
by Steve Tran (JIRA)
[ https://issues.jboss.org/browse/TEIID-4860?page=com.atlassian.jira.plugin... ]
Steve Tran commented on TEIID-4860:
-----------------------------------
Sorry, I chose the wrong version. The bug is in JDV 6.3.2, so I updated the affects version.
> OData4 swallowing exception message
> -----------------------------------
>
> Key: TEIID-4860
> URL: https://issues.jboss.org/browse/TEIID-4860
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.12.6.6_3
> Environment: JDV 6.3.2
> Windows 7
> Reporter: Steve Tran
> Assignee: Steven Hawkins
> Attachments: odata2_error_msg.png, odata4_error_msg.png
>
>
> The error message is being swallowed when accessing an endpoint via OData4. A much more useful message get displayed when accessing the same table via the OData2 interface. I'm assuming the same error message (or better) should be displayed via the version 4 interface.
> Here's the stacktrace when reproducing the error for OData4
> {code}
> 17:59:03,779 ERROR [org.teiid.ODATA] (http-0.0.0.0:8080-2) TEIID16052 Unable to process odata request due to: OData Library: An exception without message text was thrown.: org.apache.olingo.server.api.ODataApplicationException
> at org.teiid.olingo.service.TeiidServiceHandler.read(TeiidServiceHandler.java:174) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.apache.olingo.server.core.requests.DataRequest$EntityRequest.execute(DataRequest.java:332)
> at org.apache.olingo.server.core.requests.DataRequest.execute(DataRequest.java:255)
> at org.apache.olingo.server.core.ServiceDispatcher.internalExecute(ServiceDispatcher.java:160)
> at org.apache.olingo.server.core.ServiceDispatcher.execute(ServiceDispatcher.java:98)
> at org.apache.olingo.server.core.OData4HttpHandler.process(OData4HttpHandler.java:66)
> at org.teiid.olingo.web.ODataServlet.service(ODataServlet.java:43) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-2.jar:1.0.2.Final-redhat-2]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.teiid.olingo.web.ODataFilter.internalDoFilter(ODataFilter.java:231) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.teiid.olingo.web.ODataFilter.doFilter(ODataFilter.java:100) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.teiid.olingo.web.CorsFilter.doFilter(CorsFilter.java:80) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:512) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:150) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:854) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_121]
> Caused by: java.lang.NullPointerException
> at org.teiid.olingo.service.EntityCollectionResponse.isSameRow(EntityCollectionResponse.java:180) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.teiid.olingo.service.EntityCollectionResponse.isSameEntity(EntityCollectionResponse.java:154) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.teiid.olingo.service.LocalClient.executeSQL(LocalClient.java:280) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.teiid.olingo.service.TeiidServiceHandler.executeQuery(TeiidServiceHandler.java:349) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.teiid.olingo.service.TeiidServiceHandler.read(TeiidServiceHandler.java:172) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> ... 28 more
> {code}
> And here's the stack trace when reproduced from the OData 2 interface.
> {code}
> 18:01:20,885 WARN [org.teiid.ODATA] (http-0.0.0.0:8080-2) TEIID16012 Could not produce a successful OData response. Returning status ServerErrorException with message Complex key values cannot be null.
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4860) OData4 swallowing exception message
by Steve Tran (JIRA)
[ https://issues.jboss.org/browse/TEIID-4860?page=com.atlassian.jira.plugin... ]
Steve Tran updated TEIID-4860:
------------------------------
Affects Version/s: 8.12.6.6_3
(was: 8.7.11.6_2)
> OData4 swallowing exception message
> -----------------------------------
>
> Key: TEIID-4860
> URL: https://issues.jboss.org/browse/TEIID-4860
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.12.6.6_3
> Environment: JDV 6.3.2
> Windows 7
> Reporter: Steve Tran
> Assignee: Steven Hawkins
> Attachments: odata2_error_msg.png, odata4_error_msg.png
>
>
> The error message is being swallowed when accessing an endpoint via OData4. A much more useful message get displayed when accessing the same table via the OData2 interface. I'm assuming the same error message (or better) should be displayed via the version 4 interface.
> Here's the stacktrace when reproducing the error for OData4
> {code}
> 17:59:03,779 ERROR [org.teiid.ODATA] (http-0.0.0.0:8080-2) TEIID16052 Unable to process odata request due to: OData Library: An exception without message text was thrown.: org.apache.olingo.server.api.ODataApplicationException
> at org.teiid.olingo.service.TeiidServiceHandler.read(TeiidServiceHandler.java:174) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.apache.olingo.server.core.requests.DataRequest$EntityRequest.execute(DataRequest.java:332)
> at org.apache.olingo.server.core.requests.DataRequest.execute(DataRequest.java:255)
> at org.apache.olingo.server.core.ServiceDispatcher.internalExecute(ServiceDispatcher.java:160)
> at org.apache.olingo.server.core.ServiceDispatcher.execute(ServiceDispatcher.java:98)
> at org.apache.olingo.server.core.OData4HttpHandler.process(OData4HttpHandler.java:66)
> at org.teiid.olingo.web.ODataServlet.service(ODataServlet.java:43) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-2.jar:1.0.2.Final-redhat-2]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.teiid.olingo.web.ODataFilter.internalDoFilter(ODataFilter.java:231) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.teiid.olingo.web.ODataFilter.doFilter(ODataFilter.java:100) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.teiid.olingo.web.CorsFilter.doFilter(CorsFilter.java:80) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:512) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:150) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:854) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_121]
> Caused by: java.lang.NullPointerException
> at org.teiid.olingo.service.EntityCollectionResponse.isSameRow(EntityCollectionResponse.java:180) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.teiid.olingo.service.EntityCollectionResponse.isSameEntity(EntityCollectionResponse.java:154) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.teiid.olingo.service.LocalClient.executeSQL(LocalClient.java:280) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.teiid.olingo.service.TeiidServiceHandler.executeQuery(TeiidServiceHandler.java:349) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.teiid.olingo.service.TeiidServiceHandler.read(TeiidServiceHandler.java:172) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> ... 28 more
> {code}
> And here's the stack trace when reproduced from the OData 2 interface.
> {code}
> 18:01:20,885 WARN [org.teiid.ODATA] (http-0.0.0.0:8080-2) TEIID16012 Could not produce a successful OData response. Returning status ServerErrorException with message Complex key values cannot be null.
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months
[JBoss JIRA] (TEIID-4860) OData4 swallowing exception message
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4860?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4860:
---------------------------------------
The root exception has been fixed, but it's still a 500 error - it occurs whether the key is composite or not due to an NPE in EntityResponse.buildLocation. Since null is not allowed by the ParserHelper.keyValuePair, it seems expected that key values cannot be null.
Seems like we'll need to filter for this case and throw a better exception.
> OData4 swallowing exception message
> -----------------------------------
>
> Key: TEIID-4860
> URL: https://issues.jboss.org/browse/TEIID-4860
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.12.6.6_3
> Environment: JDV 6.3.2
> Windows 7
> Reporter: Steve Tran
> Assignee: Steven Hawkins
> Attachments: odata2_error_msg.png, odata4_error_msg.png
>
>
> The error message is being swallowed when accessing an endpoint via OData4. A much more useful message get displayed when accessing the same table via the OData2 interface. I'm assuming the same error message (or better) should be displayed via the version 4 interface.
> Here's the stacktrace when reproducing the error for OData4
> {code}
> 17:59:03,779 ERROR [org.teiid.ODATA] (http-0.0.0.0:8080-2) TEIID16052 Unable to process odata request due to: OData Library: An exception without message text was thrown.: org.apache.olingo.server.api.ODataApplicationException
> at org.teiid.olingo.service.TeiidServiceHandler.read(TeiidServiceHandler.java:174) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.apache.olingo.server.core.requests.DataRequest$EntityRequest.execute(DataRequest.java:332)
> at org.apache.olingo.server.core.requests.DataRequest.execute(DataRequest.java:255)
> at org.apache.olingo.server.core.ServiceDispatcher.internalExecute(ServiceDispatcher.java:160)
> at org.apache.olingo.server.core.ServiceDispatcher.execute(ServiceDispatcher.java:98)
> at org.apache.olingo.server.core.OData4HttpHandler.process(OData4HttpHandler.java:66)
> at org.teiid.olingo.web.ODataServlet.service(ODataServlet.java:43) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-2.jar:1.0.2.Final-redhat-2]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.teiid.olingo.web.ODataFilter.internalDoFilter(ODataFilter.java:231) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.teiid.olingo.web.ODataFilter.doFilter(ODataFilter.java:100) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.teiid.olingo.web.CorsFilter.doFilter(CorsFilter.java:80) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:512) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:150) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:854) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.5.17.Final-redhat-1.jar:7.5.17.Final-redhat-1]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_121]
> Caused by: java.lang.NullPointerException
> at org.teiid.olingo.service.EntityCollectionResponse.isSameRow(EntityCollectionResponse.java:180) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.teiid.olingo.service.EntityCollectionResponse.isSameEntity(EntityCollectionResponse.java:154) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.teiid.olingo.service.LocalClient.executeSQL(LocalClient.java:280) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.teiid.olingo.service.TeiidServiceHandler.executeQuery(TeiidServiceHandler.java:349) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> at org.teiid.olingo.service.TeiidServiceHandler.read(TeiidServiceHandler.java:172) [teiid-olingo-8.12.7.6_3-redhat-1.jar:8.12.7.6_3-redhat-1]
> ... 28 more
> {code}
> And here's the stack trace when reproduced from the OData 2 interface.
> {code}
> 18:01:20,885 WARN [org.teiid.ODATA] (http-0.0.0.0:8080-2) TEIID16012 Could not produce a successful OData response. Returning status ServerErrorException with message Complex key values cannot be null.
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 8 months