February 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3782) OData V4: Support system options over the operation based collections

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3782?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3782: --------------------------------------- It looks like this is somewhat of an upstream problem. ActionRequest and FunctionRequest do not have logic on them that reference system options, such as count. Is that expected? Alternatively it looks like we can visit the uri ourselves and determine this information. > OData V4: Support system options over the operation based collections > --------------------------------------------------------------------- > > Key: TEIID-3782 > URL: https://issues.jboss.org/browse/TEIID-3782 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.11 > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 8.12.x > > > Currently the system options like $top, $skip, $filter are not supported on results returned from Functions/Actions. Per OData specification this should be supported. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3960) Otherwise evaluatable constructs will inhibit pushdown

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3960?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3960: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1305538, https://bugzilla.redhat.com/show_bug.cgi?id=1306030 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1305538) > Otherwise evaluatable constructs will inhibit pushdown > ------------------------------------------------------ > > Key: TEIID-3960 > URL: https://issues.jboss.org/browse/TEIID-3960 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.2.6_2 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.13.1, 8.7.3.6_2 > > > TEIID-1522 introduced a corner case regression such that a constant projection was inlined (removing the need for a fake dependent join), but the resulting expressions were not seen as able to be pushded due to a curdate function preventing the pre-evaluation of non-pushable constructs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3963) Arrays returned by actions/functions from odata4 result in errors

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3963?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3963. ----------------------------------- Fix Version/s: 9.0 8.13.1 Resolution: Done Updated the return logic to account for array values. > Arrays returned by actions/functions from odata4 result in errors > ----------------------------------------------------------------- > > Key: TEIID-3963 > URL: https://issues.jboss.org/browse/TEIID-3963 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0, 8.13.1 > > > Actions/functions returning arrays result in exceptions as only primitive results are currently expected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3911) Nearly all odata4 errors reported as internal server errors

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3911?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3911: ------------------------------------- You are correct, without the change we can handle all the ODataApplicationException based exceptions and write to the log and response. However the ODataLibraryExceptions, unchecked exceptions will still be an issue. The above change will consolidate both into single place for handling. I will add back the unchecked exception handling, and push upstream. > Nearly all odata4 errors reported as internal server errors > ----------------------------------------------------------- > > Key: TEIID-3911 > URL: https://issues.jboss.org/browse/TEIID-3911 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Affects Versions: 8.12 > Reporter: Steven Hawkins > Fix For: 9.0 > > > From the TeiidServiceHandler we generally rethrow our exceptions as ODataApplicationExceptions that have a status code of 500 - however even using a different status code still results in a 500 error as the Olingo framework expects exception subclasses to be used (see ErrorHandler.handleException - a general application exception is always a 500 error). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3911) Nearly all odata4 errors reported as internal server errors

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3911?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3911: --------------------------------------- So without the changes you are suggesting that we convert all of our exceptions to writeError and add a server side log there as well? Then the only thing would be to handled unchecked exceptions from us and exceptions from the OData framework itself (for example if we provide an incompatible value, then olingo effectively swallows the SerializerException on the server side). With the changes it would still probably be good to have a general catch (Exception ) to ensure that a proper message is sent to the client even with unchecked exceptions. > Nearly all odata4 errors reported as internal server errors > ----------------------------------------------------------- > > Key: TEIID-3911 > URL: https://issues.jboss.org/browse/TEIID-3911 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Affects Versions: 8.12 > Reporter: Steven Hawkins > Fix For: 9.0 > > > From the TeiidServiceHandler we generally rethrow our exceptions as ODataApplicationExceptions that have a status code of 500 - however even using a different status code still results in a 500 error as the Olingo framework expects exception subclasses to be used (see ErrorHandler.handleException - a general application exception is always a 500 error). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3911) Nearly all odata4 errors reported as internal server errors

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3911?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3911: ------------------------------------- proposed changes https://github.com/rareddy/olingo-odata4/commit/6845169f073693e1239417aef... Looking back at the framework, the service methods instead of throwing exceptions, they can handle the exception and write the error response out directly without above change, as all Response objects support writeError(ODataServerError error) method. > Nearly all odata4 errors reported as internal server errors > ----------------------------------------------------------- > > Key: TEIID-3911 > URL: https://issues.jboss.org/browse/TEIID-3911 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Affects Versions: 8.12 > Reporter: Steven Hawkins > Fix For: 9.0 > > > From the TeiidServiceHandler we generally rethrow our exceptions as ODataApplicationExceptions that have a status code of 500 - however even using a different status code still results in a 500 error as the Olingo framework expects exception subclasses to be used (see ErrorHandler.handleException - a general application exception is always a 500 error). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3958) NPE Executing Against Web Service Source using invokeHttp() procedure without stream parameter

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3958?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3958: --------------------------------------- This may have been addressed by TEIID-3107. Can you validate that this still occurs with Teiid 8.9 and later, or provide a reproducing vdb? > NPE Executing Against Web Service Source using invokeHttp() procedure without stream parameter > ---------------------------------------------------------------------------------------------- > > Key: TEIID-3958 > URL: https://issues.jboss.org/browse/TEIID-3958 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1, 8.7.1.6_2 > Environment: Migrated web services model from EDS 5.3.1 that does not include 'stream' parameter in the invokeHttp() procedure > DV 6.1 - translator-ws-8.7.1.redhat-8.jar > DV 6.2 - translator-ws-8.7.1.6_2-redhat-6.jar > Reporter: Marc Shirley > Assignee: Steven Hawkins > > Appears to still be an issue similar to TEIID 2537. Executing against the invokeHttp() procedure generated by JBDS 5 for Teiid Designer 7.7.3 without a stream parameter results in a slightly different stack trace, but appears to be the same issue. > 2016-01-21 12:53:50,297 ERROR \[org.teiid.PROCESSOR\] (Worker22_QueryProcessorQueue117472) TEIID30019 Unexpected exception for request FzkQneotrSUs.5: java.lang.NullPointerException > at org.teiid.translator.ws.BinaryWSProcedureExecution.getOutputParameterValues(BinaryWSProcedureExecution.java:174) > at org.teiid.dqp.internal.datamgr.ProcedureBatchHandler.getParameterRow(ProcedureBatchHandler.java:86) [teiid-engine-8.7.2.6_2-redhat-1.jar:8.7.2.6_2-redhat-1] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:435) [teiid-engine-8.7.2.6_2-redhat-1.jar:8.7.2.6_2-redhat-1] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:207) [teiid-engine-8.7.2.6_2-redhat-1.jar:8.7.2.6_2-redhat-1] > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:301) [teiid-engine-8.7.2.6_2-redhat-1.jar:8.7.2.6_2-redhat-1] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) [teiid-engine-8.7.2.6_2-redhat-1.jar:8.7.2.6_2-redhat-1] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) [teiid-engine-8.7.2.6_2-redhat-1.jar:8.7.2.6_2-redhat-1] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_65] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.7.2.6_2-redhat-1.jar:8.7.2.6_2-redhat-1] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.7.2.6_2-redhat-1.jar:8.7.2.6_2-redhat-1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.7.2.6_2-redhat-1.jar:8.7.2.6_2-redhat-1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.7.2.6_2-redhat-1.jar:8.7.2.6_2-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_65] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_65] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_65] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3963) Arrays returned by actions/functions from odata4 result in errors

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3963: ------------------------------------- Summary: Arrays returned by actions/functions from odata4 result in errors Key: TEIID-3963 URL: https://issues.jboss.org/browse/TEIID-3963 Project: Teiid Issue Type: Bug Components: OData Affects Versions: 8.12 Reporter: Steven Hawkins Assignee: Steven Hawkins Actions/functions returning arrays result in exceptions as only primitive results are currently expected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3962) remove invalid character handling from Teiid odata4 logic

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3962: ------------------------------------- Summary: remove invalid character handling from Teiid odata4 logic Key: TEIID-3962 URL: https://issues.jboss.org/browse/TEIID-3962 Project: Teiid Issue Type: Quality Risk Components: OData Reporter: Steven Hawkins Assignee: Steven Hawkins Since we now have a better influence over the odata framework, we should remove the replacement character logic from Teiid and let that be handled by the serializers - as the current handling is intended for XML but will affect both JSON and XML results. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3960) Otherwise evaluatable constructs will inhibit pushdown

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3960?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3960: ---------------------------------- Fix Version/s: 8.7.3.6_2 9.0 8.12.5 8.13.1 > Otherwise evaluatable constructs will inhibit pushdown > ------------------------------------------------------ > > Key: TEIID-3960 > URL: https://issues.jboss.org/browse/TEIID-3960 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.2.6_2 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.13.1, 8.7.3.6_2 > > > TEIID-1522 introduced a corner case regression such that a constant projection was inlined (removing the need for a fake dependent join), but the resulting expressions were not seen as able to be pushded due to a curdate function preventing the pre-evaluation of non-pushable constructs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2016