[JBoss JIRA] (TEIID-5135) REPEAT function truncates strings to 4000 characters
by dalex dalex (JIRA)
dalex dalex created TEIID-5135:
----------------------------------
Summary: REPEAT function truncates strings to 4000 characters
Key: TEIID-5135
URL: https://issues.jboss.org/browse/TEIID-5135
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 9.3.4
Environment: teiid-9.3.4 on WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final)
Reporter: dalex dalex
Assignee: Steven Hawkins
Priority: Critical
Probably it's not bug. When running the following queries:
{code:sql}
Select Length(Repeat('abcde', 9000));; /* 4000 chars */
Select Length(Repeat('a', 9000));; /* 4000 chars */
{code}
Teiid returns 4000 instead of 9000. Can the internal truncation be avoided (maybe in some cases) or not?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIID-5133) XmlTable path language is not always identical to XPathValue expressions
by dalex dalex (JIRA)
[ https://issues.jboss.org/browse/TEIID-5133?page=com.atlassian.jira.plugin... ]
dalex dalex updated TEIID-5133:
-------------------------------
Environment: teiid-9.3.4 on WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) (was: eiid-9.3.4 on WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final))
> XmlTable path language is not always identical to XPathValue expressions
> ------------------------------------------------------------------------
>
> Key: TEIID-5133
> URL: https://issues.jboss.org/browse/TEIID-5133
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.3.4
> Environment: teiid-9.3.4 on WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final)
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Fix For: 10.0, 9.2.7, 9.3.5
>
>
> The same Path value, used in XPathValue and XmlTable->Path brings different results.
> That is for the following query:
> {code:sql}
> Select * From
> (select '<root>
> <item>
> <id>id1</id>
> <val>val1</val>
> </item>
> </root>' as resp) w,
> XMLTABLE(
> '/root' passing XMLPARSE(document w.resp) columns
> valOption2 string PATH 'item[id = "id1"]/val'
> --,valOption1 string PATH 'item[id/text() = "id1"]/val'
> ) x;;
> {code}
> returned value for "valOption2" will be changed from "val1" to "null" that is incorrect and unexpected behavior.
> Using "node/text()" in Path expressions may result in side effects.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIID-5126) Osisoft translator - SUBSTRING fails when start > string length
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5126?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5126:
---------------------------------------
We have a catch all KI on substring already as there is a lot of variations in behavior wrt negative indexes and out of range - https://teiid.gitbooks.io/documents/content/reference/String_Functions.html
> Osisoft translator - SUBSTRING fails when start > string length
> ---------------------------------------------------------------
>
> Key: TEIID-5126
> URL: https://issues.jboss.org/browse/TEIID-5126
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Driver
> Affects Versions: 8.12.x-6.4
> Reporter: Andrej Šmigala
> Assignee: Ramesh Reddy
> Priority: Minor
> Fix For: 10.1
>
>
> Calling a query such as
> {code:sql}
> SELECT cast(TIMESTAMPVALUE as string), SUBSTRING(TIMESTAMPVALUE, 22, 0) FROM BQT1.SmallA
> {code}
> fails with the following (the length of timestampvalue converted to string is 20):
> {noformat}
> Connector worker process failed for atomic-request=HOiQATHW3fPH.12.0.9: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [SQL: SELECT TOP 100 cast(g_0.TimestampValue AS String) AS c_0, SUBSTR(cast(g_0.TimestampValue AS String), 22, 0) AS c_1 FROM dvqe..SmallA AS g_0]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:363)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_141]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_141]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_141]
> at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_141]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
> at com.sun.proxy.$Proxy79.execute(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_141]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:280)
> 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:1149) [rt.jar:1.8.0_141]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_141]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_141]
> Caused by: java.sql.SQLException: [PIOLEDBENT] Arguments are invalid.
> at com.osisoft.jdbc.StatementImpl.executeQuery(StatementImpl.java:360)
> at org.jboss.jca.adapters.jdbc.WrappedStatement.executeQuery(WrappedStatement.java:344)
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:119) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4]
> ... 18 more
> Caused by: com.osisoft.rdsa.RdsaException: [PIOLEDBENT] Arguments are invalid.
> at com.osisoft.rdsa.Command.ExecuteReader(Native Method)
> at com.osisoft.rdsa.Command.executeReader(Command.java:79)
> at com.osisoft.jdbc.StatementImpl.executeQuery(StatementImpl.java:356)
> ... 20 more
> {noformat}
> This appears to be an issue with the SUBSTR implementation on the PI server, we are ok with either a workaround or documenting as KI.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIID-5134) Build Changes
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-5134:
-------------------------------------
Summary: Build Changes
Key: TEIID-5134
URL: https://issues.jboss.org/browse/TEIID-5134
Project: Teiid
Issue Type: Task
Components: Build/Kits
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 10.1
For 10.1 and later I propose that we convert to an 8-10 week cycle - with no pre-releases - so that we can drop the usage of the Alpha, Beta, etc. designations. We'll encourage people to follow the weekly snapshot builds instead.
We will have to better manage when changes are pulled in, such as how we waited for the WildFly 11 Final.
Another goal is to have the build fully automated with website updates TEIID-5015
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIID-5126) Osisoft translator - SUBSTRING fails when start > string length
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-5126?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-5126:
-------------------------------------
Thanks.
I think we can post the question to their development team and see if we can get into their queue on any of these driver issues. We can KI on our side.
> Osisoft translator - SUBSTRING fails when start > string length
> ---------------------------------------------------------------
>
> Key: TEIID-5126
> URL: https://issues.jboss.org/browse/TEIID-5126
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Driver
> Affects Versions: 8.12.x-6.4
> Reporter: Andrej Šmigala
> Assignee: Ramesh Reddy
> Priority: Minor
> Fix For: 10.1
>
>
> Calling a query such as
> {code:sql}
> SELECT cast(TIMESTAMPVALUE as string), SUBSTRING(TIMESTAMPVALUE, 22, 0) FROM BQT1.SmallA
> {code}
> fails with the following (the length of timestampvalue converted to string is 20):
> {noformat}
> Connector worker process failed for atomic-request=HOiQATHW3fPH.12.0.9: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [SQL: SELECT TOP 100 cast(g_0.TimestampValue AS String) AS c_0, SUBSTR(cast(g_0.TimestampValue AS String), 22, 0) AS c_1 FROM dvqe..SmallA AS g_0]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:363)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_141]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_141]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_141]
> at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_141]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
> at com.sun.proxy.$Proxy79.execute(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_141]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:280)
> 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:1149) [rt.jar:1.8.0_141]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_141]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_141]
> Caused by: java.sql.SQLException: [PIOLEDBENT] Arguments are invalid.
> at com.osisoft.jdbc.StatementImpl.executeQuery(StatementImpl.java:360)
> at org.jboss.jca.adapters.jdbc.WrappedStatement.executeQuery(WrappedStatement.java:344)
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:119) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4]
> ... 18 more
> Caused by: com.osisoft.rdsa.RdsaException: [PIOLEDBENT] Arguments are invalid.
> at com.osisoft.rdsa.Command.ExecuteReader(Native Method)
> at com.osisoft.rdsa.Command.executeReader(Command.java:79)
> at com.osisoft.jdbc.StatementImpl.executeQuery(StatementImpl.java:356)
> ... 20 more
> {noformat}
> This appears to be an issue with the SUBSTR implementation on the PI server, we are ok with either a workaround or documenting as KI.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIID-5133) XmlTable path language is not always identical to XPathValue expressions
by dalex dalex (JIRA)
[ https://issues.jboss.org/browse/TEIID-5133?page=com.atlassian.jira.plugin... ]
dalex dalex commented on TEIID-5133:
------------------------------------
[~shawkins] thx a lot for the quick fix.
> XmlTable path language is not always identical to XPathValue expressions
> ------------------------------------------------------------------------
>
> Key: TEIID-5133
> URL: https://issues.jboss.org/browse/TEIID-5133
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.3.4
> Environment: eiid-9.3.4 on WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final)
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Fix For: 10.0, 9.2.7, 9.3.5
>
>
> The same Path value, used in XPathValue and XmlTable->Path brings different results.
> That is for the following query:
> {code:sql}
> Select * From
> (select '<root>
> <item>
> <id>id1</id>
> <val>val1</val>
> </item>
> </root>' as resp) w,
> XMLTABLE(
> '/root' passing XMLPARSE(document w.resp) columns
> valOption2 string PATH 'item[id = "id1"]/val'
> --,valOption1 string PATH 'item[id/text() = "id1"]/val'
> ) x;;
> {code}
> returned value for "valOption2" will be changed from "val1" to "null" that is incorrect and unexpected behavior.
> Using "node/text()" in Path expressions may result in side effects.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIID-5126) Osisoft translator - SUBSTRING fails when start > string length
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIID-5126?page=com.atlassian.jira.plugin... ]
Andrej Šmigala commented on TEIID-5126:
---------------------------------------
[~rareddy] tried with Postgre which returns empty string, and Oracle which returns NULL.
> Osisoft translator - SUBSTRING fails when start > string length
> ---------------------------------------------------------------
>
> Key: TEIID-5126
> URL: https://issues.jboss.org/browse/TEIID-5126
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Driver
> Affects Versions: 8.12.x-6.4
> Reporter: Andrej Šmigala
> Assignee: Ramesh Reddy
> Priority: Minor
> Fix For: 10.1
>
>
> Calling a query such as
> {code:sql}
> SELECT cast(TIMESTAMPVALUE as string), SUBSTRING(TIMESTAMPVALUE, 22, 0) FROM BQT1.SmallA
> {code}
> fails with the following (the length of timestampvalue converted to string is 20):
> {noformat}
> Connector worker process failed for atomic-request=HOiQATHW3fPH.12.0.9: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [SQL: SELECT TOP 100 cast(g_0.TimestampValue AS String) AS c_0, SUBSTR(cast(g_0.TimestampValue AS String), 22, 0) AS c_1 FROM dvqe..SmallA AS g_0]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:363)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_141]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_141]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_141]
> at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_141]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
> at com.sun.proxy.$Proxy79.execute(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_141]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:280)
> 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:1149) [rt.jar:1.8.0_141]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_141]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_141]
> Caused by: java.sql.SQLException: [PIOLEDBENT] Arguments are invalid.
> at com.osisoft.jdbc.StatementImpl.executeQuery(StatementImpl.java:360)
> at org.jboss.jca.adapters.jdbc.WrappedStatement.executeQuery(WrappedStatement.java:344)
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:119) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4]
> ... 18 more
> Caused by: com.osisoft.rdsa.RdsaException: [PIOLEDBENT] Arguments are invalid.
> at com.osisoft.rdsa.Command.ExecuteReader(Native Method)
> at com.osisoft.rdsa.Command.executeReader(Command.java:79)
> at com.osisoft.jdbc.StatementImpl.executeQuery(StatementImpl.java:356)
> ... 20 more
> {noformat}
> This appears to be an issue with the SUBSTR implementation on the PI server, we are ok with either a workaround or documenting as KI.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (TEIID-5133) XmlTable path language is not always identical to XPathValue expressions
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5133?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5133.
-----------------------------------
Fix Version/s: 10.0
9.2.7
9.3.5
Resolution: Done
We need to check for the special case of an atomized value with no additional arcs. This seems to only happen with an element reference in a node test.
> XmlTable path language is not always identical to XPathValue expressions
> ------------------------------------------------------------------------
>
> Key: TEIID-5133
> URL: https://issues.jboss.org/browse/TEIID-5133
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.3.4
> Environment: eiid-9.3.4 on WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final)
> Reporter: dalex dalex
> Assignee: Steven Hawkins
> Fix For: 10.0, 9.2.7, 9.3.5
>
>
> The same Path value, used in XPathValue and XmlTable->Path brings different results.
> That is for the following query:
> {code:sql}
> Select * From
> (select '<root>
> <item>
> <id>id1</id>
> <val>val1</val>
> </item>
> </root>' as resp) w,
> XMLTABLE(
> '/root' passing XMLPARSE(document w.resp) columns
> valOption2 string PATH 'item[id = "id1"]/val'
> --,valOption1 string PATH 'item[id/text() = "id1"]/val'
> ) x;;
> {code}
> returned value for "valOption2" will be changed from "val1" to "null" that is incorrect and unexpected behavior.
> Using "node/text()" in Path expressions may result in side effects.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months