[JBoss JIRA] (TEIID-4039) Resolving of entityid with additional system options fail
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4039?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-4039.
---------------------------------
> Resolving of entityid with additional system options fail
> ---------------------------------------------------------
>
> Key: TEIID-4039
> URL: https://issues.jboss.org/browse/TEIID-4039
> Project: Teiid
> Issue Type: Sub-task
> Components: OData
> Reporter: Juraj Duráni
> Assignee: Ramesh Reddy
> Fix For: 9.0, 8.12.5
>
>
> *URL:* http://localhost:8080/odata4/olingo_basic/Source/$entity/?$id=Customers(1...
> *Returned status code:* 404
> *URL:* http://localhost:8080/odata4/olingo_basic/Source/$entity/?$id=Customers(1...
> *Returned status code:* 500
> In this case response does not contain mandatory OData-version header and server throws exception:
> {code:plain}
> 12:20:40,911 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/odata4].[odata4]] (http-/127.0.0.1:8080-1) JBWEB000236: Servlet.service() for servlet odata4 threw exception: java.util.EmptyStackException
> at java.util.Stack.peek(Stack.java:102) [rt.jar:1.8.0-internal]
> at org.apache.olingo.server.core.uri.parser.UriParseTreeVisitor.visitSelectSegment(UriParseTreeVisitor.java:2195)
> at org.apache.olingo.server.core.uri.antlr.UriParserParser$SelectSegmentContext.accept(UriParserParser.java:3611)
> at org.apache.olingo.server.core.uri.parser.UriParseTreeVisitor.visitSelectItem(UriParseTreeVisitor.java:2168)
> at org.apache.olingo.server.core.uri.antlr.UriParserParser$SelectItemContext.accept(UriParserParser.java:3541)
> at org.apache.olingo.server.core.uri.parser.UriParseTreeVisitor.visitSelectEOF(UriParseTreeVisitor.java:2153)
> at org.apache.olingo.server.core.uri.parser.Parser.parseUri(Parser.java:228)
> at org.apache.olingo.server.core.ErrorHandler.handleServerError(ErrorHandler.java:93)
> at org.apache.olingo.server.core.ErrorHandler.handleException(ErrorHandler.java:85)
> at org.apache.olingo.server.core.OData4HttpHandler.process(OData4HttpHandler.java:70)
> at org.teiid.olingo.web.ODataServlet.service(ODataServlet.java:50) [teiid-olingo-8.12.5.redhat-2.jar:8.12.5.redhat-2]
> 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.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.teiid.olingo.web.ODataFilter.doFilter(ODataFilter.java:194) [teiid-olingo-8.12.5.redhat-2.jar:8.12.5.redhat-2]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:512) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.5.4.Final-redhat-4.jar:7.5.4.Final-redhat-4]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:150) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:854) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.5.11.Final-redhat-1.jar:7.5.11.Final-redhat-1]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0-internal]
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[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 closed TEIID-3911.
---------------------------------
> Nearly all odata4 errors reported as internal server errors
> -----------------------------------------------------------
>
> Key: TEIID-3911
> URL: https://issues.jboss.org/browse/TEIID-3911
> Project: Teiid
> Issue Type: Sub-task
> Components: OData
> Affects Versions: 8.12
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.0, 8.12.5
>
>
> 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
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (TEIID-4089) Teiid JDBC driver does not reset the update count when calling getMoreResults(int)
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4089?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-4089.
---------------------------------
> Teiid JDBC driver does not reset the update count when calling getMoreResults(int)
> ----------------------------------------------------------------------------------
>
> Key: TEIID-4089
> URL: https://issues.jboss.org/browse/TEIID-4089
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Driver
> Affects Versions: 8.11.2
> Environment: Windows 7 Pro 64bit
> Java 8u66 64bit
> Reporter: Jesse Shaffer
> Assignee: Steven Hawkins
> Fix For: 9.0, 8.12.5, 8.13.3
>
>
> I have run across a situation with the JDBC driver. Looking at {{StatementImpl.getMoreResults(int)}}, it does not clear the update counts, whereas {{StatementImpl.getMoreResults()}} does. Long story short, this is preventing me from integrating the JDBC driver properly into my application, due to the runtime's (3rd party) handling of statements. It gets stuck in an infinite loop because to close the statement, they call {{StatementImpl.getMoreResults(Statement.CLOSE_CURRENT_RESULT);}}, but then they have a check for a -1 value to be returned from {{getUpdateCount()}} before exiting the loop. In my case, that value is always 1, and thus the infinite loop.
> It seems logical to me that {{getMoreResults(int)}} should behave the same as {{getMoreResults()}} seeing as they both always return false, only the latter is the only one that closes the resultset/clearing the update count.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (TEIID-4580) ST_PointOnSurface returns point on the boundary of the polygon
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4580?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-4580.
---------------------------------
> ST_PointOnSurface returns point on the boundary of the polygon
> --------------------------------------------------------------
>
> Key: TEIID-4580
> URL: https://issues.jboss.org/browse/TEIID-4580
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.x, 8.12.7.6_3
> Reporter: Andrej Šmigala
> Assignee: Steven Hawkins
> Fix For: 9.1.2, 9.2, 8.12.9.6_3
>
>
> Calling ST_PointOnSurface with a polygon argument returns one of the points of the polygon boundary.
> E.g.
> {code:sql}
> SELECT ST_AsText(ST_PointOnSurface(ST_GeomFromText('POLYGON ((67 13, 67 18, 59 18, 59 13, 67 13))')));
> {code}
> returns {{POINT (67 13)}}
> The spec says
> bq. PointOnSurface( ):Point—A point guaranteed to be on this Surface.
> which might not be completely clear, but [several|http://gis.stackexchange.com/questions/76498/how-is-st-pointonsur...] [sources|http://workshops.boundlessgeo.com/postgis-intro/geometry_returnin...] indicate that "on this surface" means _inside_ the surface.
> When running the same query against a postgis instance (not through teiid), the result is {{POINT(63 15.5)}}, which is actually inside the polygon.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (TEIID-4096) AssertionError with independent side of a dependent join that has an ordered limit
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4096?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-4096.
---------------------------------
> AssertionError with independent side of a dependent join that has an ordered limit
> ----------------------------------------------------------------------------------
>
> Key: TEIID-4096
> URL: https://issues.jboss.org/browse/TEIID-4096
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.11
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 9.0, 8.12.5, 8.13.3
>
>
> An independent side with a nested ordered limit:
> with a (x, y, z) as (select e1, e2, e3 from pm1.g1) SELECT a.x, b.e1 from a, /*+ makeind */ (SELECT * from pm1.g2, a where e1 = x and z = 1 order by e2 limit 2) as b where a.x = b.e1
> will cause an assertion error in sorting the dependent values:
> java.lang.AssertionError: Assertion failed.
> at org.teiid.core.util.Assertion.failed(Assertion.java:73)
> at org.teiid.core.util.Assertion.assertTrue(Assertion.java:68)
> at org.teiid.core.util.Assertion.assertTrue(Assertion.java:60)
> at org.teiid.query.processor.relational.SortUtility.<init>(SortUtility.java:151)
> at org.teiid.query.processor.relational.SortUtility.<init>(SortUtility.java:187)
> at org.teiid.query.processor.relational.DependentCriteriaProcessor$TupleState.sort(DependentCriteriaProcessor.java:113)
> Because the schema being used is from the below the limit/order by and effectively the source node.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (TEIID-4635) Mongo translator - NAMEINSOURCE option is ignored
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4635?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-4635.
---------------------------------
> Mongo translator - NAMEINSOURCE option is ignored
> -------------------------------------------------
>
> Key: TEIID-4635
> URL: https://issues.jboss.org/browse/TEIID-4635
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.12.8.6_3
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
>
> Mongo translator ignores NAMEINSOURCE table/column option.
> For table \[1\], no data is returned. For column \[2\], all values in column are NULL.
> {code:sql|title=\[1\] Sample DDL - table}
> CREATE FOREIGN TABLE MyNewName (
> id integer PRIMARY KEY,
> name varchar(25)
> ) OPTIONS(UPDATABLE 'TRUE', NAMEINSOURCE 'RealCollectionName');
> {code}
> {code:sql|title=\[2\] Sample DDL - column}
> CREATE FOREIGN TABLE MyCollection (
> id integer PRIMARY KEY,
> myColName varchar(25) OPTIONS(NAMEINSOURCE 'realName')
> ) OPTIONS(UPDATABLE 'TRUE');
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months