May 2017 - teiid-issues - Jboss List Archives

[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 updated TEIID-4860: ---------------------------------- Fix Version/s: 10.x (was: 9.3) Changing the community fix version to 10.x for whenever an appropriate olingo fix is provided. > 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: Johnathon Lee > Fix For: 10.x > > 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)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4901) Add parallel source query handling for when IN criteria values exceed MaxInCriteriaSize for translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4901?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4901. ----------------------------------- Resolution: Done Added a new rule that will push these in predicates as dependent sets and a doc note. > Add parallel source query handling for when IN criteria values exceed MaxInCriteriaSize for translator > ------------------------------------------------------------------------------------------------------ > > Key: TEIID-4901 > URL: https://issues.jboss.org/browse/TEIID-4901 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.12.10.6_3 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 9.3 > > > Add the capability to split an independent accessnode into multiple parallel source queries when the number of IN criteria values exceed the translator's MaxInCriteriaSize value. This would be similar handling to what we perform on the dependent side of a dependent join when the number of values exceed the size. > The background for this request is regarding input to an SAP gateway source which has a MaxInCriteriaSize of 3 due to URL length restrictions. Currently, if 4 values are submitted the full result set is returned to be processed within the Teiid engine. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4901) Add parallel source query handling for when IN criteria values exceed MaxInCriteriaSize for translator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4901?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4901: ---------------------------------- Component/s: Query Engine Fix Version/s: 9.3 > Add parallel source query handling for when IN criteria values exceed MaxInCriteriaSize for translator > ------------------------------------------------------------------------------------------------------ > > Key: TEIID-4901 > URL: https://issues.jboss.org/browse/TEIID-4901 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.12.10.6_3 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 9.3 > > > Add the capability to split an independent accessnode into multiple parallel source queries when the number of IN criteria values exceed the translator's MaxInCriteriaSize value. This would be similar handling to what we perform on the dependent side of a dependent join when the number of values exceed the size. > The background for this request is regarding input to an SAP gateway source which has a MaxInCriteriaSize of 3 due to URL length restrictions. Currently, if 4 values are submitted the full result set is returned to be processed within the Teiid engine. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4903) Create a new server quickstart for the new infinispan hotrod connector/translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4903?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-4903: -------------------------------- Component/s: Infinispan > Create a new server quickstart for the new infinispan hotrod connector/translator > --------------------------------------------------------------------------------- > > Key: TEIID-4903 > URL: https://issues.jboss.org/browse/TEIID-4903 > Project: Teiid > Issue Type: Task > Components: Infinispan, Quick Starts > Affects Versions: 9.3.1 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > > Create a new server quickstart for the new infinispan hotrod connector/translator. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4904) Add support for identify security to the infinispan connector

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4904?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-4904: -------------------------------- Component/s: Infinispan (was: JDG Connector) > Add support for identify security to the infinispan connector > ------------------------------------------------------------- > > Key: TEIID-4904 > URL: https://issues.jboss.org/browse/TEIID-4904 > Project: Teiid > Issue Type: Enhancement > Components: Infinispan > Reporter: Van Halbert > Assignee: Steven Hawkins > > Add support for identify secuirty to the new infinispan connector/translator. This is needed for openshift. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4896) Two VDB's referencing same teiid_ispn:cache is not using the same cache

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4896?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-4896: ------------------------------------- Fix Version/s: 9.3.1 Affects Version/s: 9.3 (was: 9.3.1) Assignee: (was: Steven Hawkins) > Two VDB's referencing same teiid_ispn:cache is not using the same cache > ----------------------------------------------------------------------- > > Key: TEIID-4896 > URL: https://issues.jboss.org/browse/TEIID-4896 > Project: Teiid > Issue Type: Bug > Components: JDG Connector > Affects Versions: 9.3 > Reporter: Van Halbert > Fix For: 9.3.1 > > Attachments: jdg-remote-cache-ddl-vdb.xml, jdg-remote-cache-registered-pb-vdb.xml > > > I have 2 VDB's where they both reference the same cache using OPTIONS property: > "teiid_ispn:cache" 'datasourceCache' > However, when I insert into one VDB, its not seen by the other VDB. > This was testing out the translators ability to use an already registered protobuf in Infinispan. > The first VDB (jdg-remote-cache-vdb.xml) was deployed and then inserted and selected the results. This registered the protobuf. > The second VDB (jdg-remote-cache-registered-pb-vdb.xml) was then deployed and was expecting to be able to read the same cache. The metadata was derived correctly, but it appears that one of the two are using the default cache, not the specified cache. > I'll attach the vdb's. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4904) Add support for identify security to the infinispan connector

by Van Halbert (JIRA)

Van Halbert created TEIID-4904: ---------------------------------- Summary: Add support for identify security to the infinispan connector Key: TEIID-4904 URL: https://issues.jboss.org/browse/TEIID-4904 Project: Teiid Issue Type: Enhancement Components: JDG Connector Reporter: Van Halbert Assignee: Steven Hawkins Add support for identify secuirty to the new infinispan connector/translator. This is needed for openshift. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4903) Create a new server quickstart for the new infinispan hotrod connector/translator

by Van Halbert (JIRA)

Van Halbert created TEIID-4903: ---------------------------------- Summary: Create a new server quickstart for the new infinispan hotrod connector/translator Key: TEIID-4903 URL: https://issues.jboss.org/browse/TEIID-4903 Project: Teiid Issue Type: Task Components: Quick Starts Affects Versions: 9.3.1 Reporter: Van Halbert Assignee: Van Halbert Priority: Minor Create a new server quickstart for the new infinispan hotrod connector/translator. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4902) Create embedded example for the new infinispan hotrod translator/connector

by Van Halbert (JIRA)

Van Halbert created TEIID-4902: ---------------------------------- Summary: Create embedded example for the new infinispan hotrod translator/connector Key: TEIID-4902 URL: https://issues.jboss.org/browse/TEIID-4902 Project: Teiid Issue Type: Task Components: Quick Starts Affects Versions: 9.3 Reporter: Van Halbert Assignee: Van Halbert Priority: Minor Create an embedded quickstart for the new infinispan hotrod connector/translator. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4901) Add parallel source query handling for when IN criteria values exceed MaxInCriteriaSize for translator

by Marc Shirley (JIRA)

Marc Shirley created TEIID-4901: ----------------------------------- Summary: Add parallel source query handling for when IN criteria values exceed MaxInCriteriaSize for translator Key: TEIID-4901 URL: https://issues.jboss.org/browse/TEIID-4901 Project: Teiid Issue Type: Feature Request Affects Versions: 8.12.10.6_3 Reporter: Marc Shirley Assignee: Steven Hawkins Add the capability to split an independent accessnode into multiple parallel source queries when the number of IN criteria values exceed the translator's MaxInCriteriaSize value. This would be similar handling to what we perform on the dependent side of a dependent join when the number of values exceed the size. The background for this request is regarding input to an SAP gateway source which has a MaxInCriteriaSize of 3 due to URL length restrictions. Currently, if 4 values are submitted the full result set is returned to be processed within the Teiid engine. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2017