April 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4135) Invalid query when using recursive CTE with translators that do not suport RCTE pushdown

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4135?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4135: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1326842|https://bugzilla.redhat.com/show_bug.cgi?id=1326842] from NEW to MODIFIED > Invalid query when using recursive CTE with translators that do not suport RCTE pushdown > ---------------------------------------------------------------------------------------- > > Key: TEIID-4135 > URL: https://issues.jboss.org/browse/TEIID-4135 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.12.x > Reporter: Andrej Šmigala > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5 > > > When running a recursive common table expression query against a source that does not support recursive cte pushdown, only the recursive part of the query is pushed, which fails, since it references a non-existent table (the cte). > E. g. the query > {code:sql} > WITH tmp_cte(id, fk, lvl) AS ( > SELECT id, fk, 0 as lvl FROM SourceModel.cte_source WHERE fk IS NULL > UNION ALL > SELECT e.id, e.fk, lvl + 1 as lvl FROM SourceModel.cte_source AS e INNER JOIN tmp_cte AS ecte ON ecte.id = e.fk > ) > SELECT * FROM tmp_cte > {code} > against a PostreSQL source results in {noformat}Remote org.postgresql.util.PSQLException: ERROR: relation "tmp_cte" does not exist{noformat} > because this query is pushed down: > {code:sql}SELECT g_0.id, g_0.fk, g_0.lvl FROM tmp_cte AS g_0{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4134) Oracle requires column alias list when using recursive CTE

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4134?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4134: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1326833|https://bugzilla.redhat.com/show_bug.cgi?id=1326833] from NEW to MODIFIED > Oracle requires column alias list when using recursive CTE > ---------------------------------------------------------- > > Key: TEIID-4134 > URL: https://issues.jboss.org/browse/TEIID-4134 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.12.x > Reporter: Andrej Šmigala > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5 > > > Running a recursive common table expression query against an Oracle source removes the columns alias list, which causes {noformat}ORA-32039: recursive WITH clause must have column alias list{noformat} > Note that there might be an issue with some specific versions of Oracle 11g, the columns alias list is required 11.2.0.4, but might not be in 11.2.0.2. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4042) OData returns status code 200 insteda of 204 if there are no expanded entities

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4042?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4042: ------------------------------------- The Text reads from spec as follows "If the relationship terminates on a collection, the response MUST be the format-specific representation of the collection of related entities. If no entities are related, the response is the format-specific representation of an empty collection. If the relationship terminates on a single entity, the response MUST be the format-specific representation of the related single entity. If no entity is related, the service returns 204 No Content So, only in the case where the the relation ship produces a single entity, and when that entity is not found it should return 204, the current 200 is correct per spec. > OData returns status code 200 insteda of 204 if there are no expanded entities > ------------------------------------------------------------------------------- > > Key: TEIID-4042 > URL: https://issues.jboss.org/browse/TEIID-4042 > 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/Customers(4)/Orders_FK0 > *Returned status code:* 200 > *Expected:* 204 and empty body > See http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-pr... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4042) OData returns status code 200 instead of 204 if there are no expanded entities

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4042?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-4042: -------------------------------- Summary: OData returns status code 200 instead of 204 if there are no expanded entities (was: OData returns status code 200 insteda of 204 if there are no expanded entities ) > OData returns status code 200 instead of 204 if there are no expanded entities > ------------------------------------------------------------------------------- > > Key: TEIID-4042 > URL: https://issues.jboss.org/browse/TEIID-4042 > 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/Customers(4)/Orders_FK0 > *Returned status code:* 200 > *Expected:* 204 and empty body > See http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-pr... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4116) XMLTABLE empty element parsed as integer causes invalid format

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4116?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4116: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1324071|https://bugzilla.redhat.com/show_bug.cgi?id=1324071] from NEW to MODIFIED > XMLTABLE empty element parsed as integer causes invalid format > -------------------------------------------------------------- > > Key: TEIID-4116 > URL: https://issues.jboss.org/browse/TEIID-4116 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12.5 > Reporter: Jan Stastny > Assignee: Steven Hawkins > > Function XMLTABLE provides ability to create a relational table from xml document, it also supports parsing various datatypes. > When the xml element is parsed as integer, and the matched element is empty, invalid format error occurs. > Invocation of XMLTABLE: > {code:sql} > CREATE VIEW EMPTY_ELEMENT_INTEGER_NO_PATH(x integer) AS select * from xmltable('/a' passing convert('<a></a>', xml) columns b integer) as x; > {code} > Exception occured: > {code:plain} > org.teiid.jdbc.TeiidSQLException: TEIID10072 Invalid integer format in String: > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135) > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71) > at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:703) > at org.teiid.jdbc.StatementImpl.access$100(StatementImpl.java:64) > at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:542) > at org.teiid.client.util.ResultsFuture.done(ResultsFuture.java:135) > at org.teiid.client.util.ResultsFuture.access$200(ResultsFuture.java:40) > at org.teiid.client.util.ResultsFuture$1.receiveResults(ResultsFuture.java:79) > at org.teiid.net.socket.SocketServerInstanceImpl.receivedMessage(SocketServerInstanceImpl.java:268) > at org.teiid.net.socket.SocketServerInstanceImpl.read(SocketServerInstanceImpl.java:306) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.teiid.net.socket.SocketServerConnectionFactory$ShutdownHandler.invoke(SocketServerConnectionFactory.java:98) > at com.sun.proxy.$Proxy6.read(Unknown Source) > at org.teiid.net.socket.SocketServerInstanceImpl$RemoteInvocationHandler$1.get(SocketServerInstanceImpl.java:405) > at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:551) > at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:404) > at org.teiid.jdbc.StatementImpl.executeQuery(StatementImpl.java:338) > at org.jboss.qe.functions.xml.XmlTableTest.testXmlTableEmptyElementIntegerNoPath(XmlTableTest.java:192) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291) > at org.testng.SuiteRunner.run(SuiteRunner.java:240) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:1198) > at org.testng.TestNG.runSuitesLocally(TestNG.java:1123) > at org.testng.TestNG.run(TestNG.java:1031) > at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:70) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:108) > at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:111) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:172) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:104) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:70) > Caused by: org.teiid.core.types.TransformationException: TEIID10072 Invalid integer format in String: > at org.teiid.core.types.basic.StringToIntegerTransform.transformDirect(StringToIntegerTransform.java:43) > at org.teiid.core.types.Transform.transform(Transform.java:47) > at org.teiid.core.types.DataTypeManager.transformValue(DataTypeManager.java:942) > at org.teiid.core.types.DataTypeManager.transformValue(DataTypeManager.java:928) > at org.teiid.query.function.FunctionDescriptor.importValue(FunctionDescriptor.java:322) > at org.teiid.query.processor.relational.XMLTableNode.getValue(XMLTableNode.java:376) > at org.teiid.query.processor.relational.XMLTableNode.processRow(XMLTableNode.java:341) > at org.teiid.query.processor.relational.XMLTableNode.nextBatchDirect(XMLTableNode.java:225) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282) > at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:150) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:282) > at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145) > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146) > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:470) > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:348) > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:274) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) > 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:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {code} > The problem applies also for invocation with path expression specified like this: > {code:sql} > CREATE VIEW EMPTY_ELEMENT_INTEGER(x integer) AS select * from xmltable('/a' passing convert('<a></a>', xml) columns x integer path 'b') as x; > {code} > But not for an invocation, where the xpath is specified as 'b/text()': > {code:sql} > CREATE VIEW EMPTY_ELEMENT_INTEGER(b integer) AS select * from xmltable('/a' passing convert('<a></a>', xml) columns b integer path 'b/text()') as x; > {code} > Root of this issue is in different string result of XMLTABLE invocation with 'b' vs. 'b/text()' paths. > For empty element : > * XMLTABLE(.... columns x string PATH 'b') returns empty string '' > * XMLTABLE(.... columns x string PATH 'b/text()') returns null > I think Teiid should be able to handle casting value of an empty element to any type without any extra precaution required. The contents retreived from an xml element can't be agnostic of the fact, that Teiid parses them as String first and then tries to cast them to appropriate type. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4148) Add "org.modeshape.jdbc" dependency to teiid jdbc translator module

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4148?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4148. ----------------------------------- Fix Version/s: 9.0 8.12.5 Resolution: Done Merged the pull requests. > Add "org.modeshape.jdbc" dependency to teiid jdbc translator module > ------------------------------------------------------------------- > > Key: TEIID-4148 > URL: https://issues.jboss.org/browse/TEIID-4148 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.12.5 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 9.0, 8.12.5 > > > the "org.jboss.teiid.translator.jdbc" module (where the query originates from) has to list "org.modeshape.jdbc" as a dependency so that ModeShape's CP can be accessible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2694) Support for Blob Input in Teiid REST services

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2694?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2694: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1327245|https://bugzilla.redhat.com/show_bug.cgi?id=1327245] from NEW to MODIFIED > Support for Blob Input in Teiid REST services > --------------------------------------------- > > Key: TEIID-2694 > URL: https://issues.jboss.org/browse/TEIID-2694 > Project: Teiid > Issue Type: Enhancement > Affects Versions: 8.5 > Environment: EAP 6.1 Alpha , Teiid 8.5 > Reporter: Madhu Garimilla > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5 > > > We are trying to upload large files as Blobs using Teiid REST service through VDB. Though we are writing the Blob objects to HttpUrlConnection object, it is not received on REST method. As per the conversation in the thread "https://community.jboss.org/thread/232840" Current parameter handling is done through strings and needs be enhanced to support Blob objects. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4042) OData returns status code 200 insteda of 204 if there are no expanded entities

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4042?page=com.atlassian.jira.plugin... ] Van Halbert reopened TEIID-4042: -------------------------------- Teiid still returns status code 200 (ER2 build) > OData returns status code 200 insteda of 204 if there are no expanded entities > ------------------------------------------------------------------------------- > > Key: TEIID-4042 > URL: https://issues.jboss.org/browse/TEIID-4042 > 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/Customers(4)/Orders_FK0 > *Returned status code:* 200 > *Expected:* 204 and empty body > See http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-pr... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4064) OData - missing non-nullable property

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4064?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4064: ------------------------------------- Now I have also ran through this exact same example using postgres database locally, and could not reproduce this. The stack seem to indicate your DB does not have the FK relation, can you check and see your $metadata and see if there is Order_FK0? > OData - missing non-nullable property > ------------------------------------- > > Key: TEIID-4064 > URL: https://issues.jboss.org/browse/TEIID-4064 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > Labels: Alpha3 > Fix For: 9.0, 8.12.5 > > > Change DDL for tables Customer and Orders in VDB as follows: > {code:sql} > CREATE FOREIGN TABLE Customers ( > id integer PRIMARY KEY OPTIONS (NAMEINSOURCE 'id'), > name varchar(10)) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.CUSTOMERS'); > CREATE FOREIGN TABLE Orders ( > id integer PRIMARY KEY OPTIONS (NAMEINSOURCE 'id'), > customerid integer, > place varchar(10), > FOREIGN KEY (customerid) REFERENCES Customers(id)) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.ORDERS'); > {code} > Note, that both tables have same name of primary key named "id". > Invoke GET method to URL http://localhost:8080/odata4/olingo_basic/Source/Customers/?$count=true&$... > *Result:* > {code:xml} > <error> > <code>400</code> > <message>The non-nullable property 'id' is missing.</message> > </error> > {code} > Here are selected part of Teiid's log: > *Query:* > {code:sql} > SELECT g10.id, g10.name, g11.id, g11.customerid, g11.place FROM Source.Customers AS g10 LEFT OUTER JOIN Source.Orders AS g11 ON g10.id = g11.customerid ORDER BY g10.id > {code} > *Result:* > |id|name|id|customerid|place| > |1|customer1|1|1|town| > |1|customer1|2|1|state| > |1|customer1|3|1|country| > |1|customer1|4|1|abroad| > |2|customer2|5|2|state| > |2|customer2|6|2|country| > |3|customer3|7|3|town| > |3|customer3|8|3|town| > |4|customer4|<null>|<null>|<null>| -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3462) Add support for semantic versioning of VDBs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3462?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3462: --------------------------------------- The initial commits replaced all the . in the version with _ for Rest access as that was the previous convention. After talking to Ramesh, that has been changed to just vdb_version for the context and war name. This is (and has been) different than OData which uses vdb.version, so I'll log a follow on issue to make things consistent. > Add support for semantic versioning of VDBs > ------------------------------------------- > > Key: TEIID-3462 > URL: https://issues.jboss.org/browse/TEIID-3462 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.7 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 9.0 > > > Semantic versioning [1] should be supported in the VDB versioning in order to be able to easier determine whether there are breaking changes from the client perspective and to more easily establish a link between client software versions and the VDBs they rely upon. > [1] http://semver.org/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 April 2016