November 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2020) Running Sybase procedure with jconnect driver in Teiid fails

by Anonymous (JIRA)

[ https://issues.jboss.org/browse/TEIID-2020?page=com.atlassian.jira.plugin... ] Anonymous commented on TEIID-2020: ---------------------------------- Vivienne Westwood vivenne westwood http://www.cellact.co.uk/uk/vwbag.html > Running Sybase procedure with jconnect driver in Teiid fails > ------------------------------------------------------------ > > Key: TEIID-2020 > URL: https://issues.jboss.org/browse/TEIID-2020 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.4.1 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 7.4.1, 7.7.1, 8.0 > > Attachments: Sybase_test.vdb > > > run the following against the Sybase_test.vdb > exec sp_rows_between(1,6,'SmallA') > You'll receive the below error: > [TranslatorException] ZZZZZ: Error Code:ZZZZZ Message:'{ ?= call sp_rows_between(?,?,?)}' error executing statement(s): {1} > 1 [SybSQLException]Execute cursor 'jconnect_implicit_3' is declared on a procedure which contains a non-SELECT or a SELECT with a COMPUTE clause. For the declaration of this cursor to be legal it should have a single SELECT statement without a COMPUTE clause. > at org.teiid.translator.jdbc.JDBCProcedureExecution.execute(JDBCProcedureExecution.java:70) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:264) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:338) > at org.teiid.dqp.internal.process.DataTierTupleSource.access$000(DataTierTupleSource.java:80) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:138) > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:135) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:121) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:230) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:118) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:288) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Caused by: com.sybase.jdbc3.jdbc.SybSQLException: Execute cursor 'jconnect_implicit_3' is declared on a procedure which contains a non-SELECT or a SELECT with a COMPUTE clause. For the declaration of this cursor to be legal it should have a single SELECT statement without a COMPUTE clause. > at com.sybase.jdbc3.tds.Tds.a(Unknown Source) > I can use DBVisualizer and the same jConnect driver and run the exact same procedure with correct results. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3206) EAP 6.3 - JDBC Datasources Test Connection

by Tom Arnold (JIRA)

[ https://issues.jboss.org/browse/TEIID-3206?page=com.atlassian.jira.plugin... ] Tom Arnold edited comment on TEIID-3206 at 11/11/14 8:51 PM: ------------------------------------------------------------- The work to get it in the install script is 90% done. This script needs to be run once to create a replacement module for IronJacamar. The version can be changed, but I settled on 1.0.26.Final as it seemed to be the earliest that fixed the issue (counter to the version indicated by JBJCA-1151). It uses the existing module XML with the versions updated, and gets the new JARs from JBoss repos. I took this approach because I couldn't find any IronJacamar releases published as JBoss modules. I assume the resulting ZIP can be hosted on Teiid SourceForge or somewhere similar. https://gist.github.com/Tom9729/fe28e904f9ce4048382e This is a patch file for the install script that updates the IronJacamar module. The SHA1 and URL parts need to be filled in once the module has been made and it has been uploaded somewhere. https://gist.github.com/Tom9729/a158354a3468dda731d6 was (Author: tom9729): The work to get it in the install script is 90% done. This script needs to be run once to create a replacement module for IronJacamar. The version can be changed, but I settled on 1.0.26.Final as it seemed to be the earliest that fixed the issue (counter to the version indicated by JBJCA-1151). It uses the existing module XML with the versions updated, and gets the new JARs from JBoss repos. I took this approach because I couldn't find any IronJacamar releases published as JBoss modules. I assume the resulting ZIP can be hosted on Teiid SourceForge or somewhere similar. https://gist.github.com/Tom9729/fe28e904f9ce4048382e This is a patch file for the install script that updated the IronJacamar module. The SHA1 and URL parts need to be filled in once the module has been made and it has been uploaded somewhere. https://gist.github.com/Tom9729/a158354a3468dda731d6 > EAP 6.3 - JDBC Datasources Test Connection > ------------------------------------------ > > Key: TEIID-3206 > URL: https://issues.jboss.org/browse/TEIID-3206 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 8.9, 8.10 > Reporter: Tom Arnold > Assignee: Steven Hawkins > > Using `Test Connection` for JDBC Datasources seems to be broken in the standalone server built from 8.9.x and master. This is an issue with EAP 6.3 Alpha1. > This is reproducible with the built-in ExampleDS H2 database. Run the `install.sh`, unzip, add a management user (bin/add-user.sh), start the server, and then login to the admin console (localhost:9990). Then go to Profile -> Connector -> Data Sources -> ExampleDS -> Connection -> Test Connection. It will fail with this error: "JBAS010440: failed to invoke operation: JBAS010447: Connection is not valid. This also happens with Oracle and PostgreSQL datasources. > The datasources seem to work despite this, but it would be good to understand the root cause and get it fixed if possible. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3206) EAP 6.3 - JDBC Datasources Test Connection

by Tom Arnold (JIRA)

[ https://issues.jboss.org/browse/TEIID-3206?page=com.atlassian.jira.plugin... ] Tom Arnold commented on TEIID-3206: ----------------------------------- The work to get it in the install script is 90% done. This script needs to be run once to create a replacement module for IronJacamar. The version can be changed, but I settled on 1.0.26.Final as it seemed to be the earliest that fixed the issue (counter to the version indicated by JBJCA-1151). It uses the existing module XML with the versions updated, and gets the new JARs from JBoss repos. I took this approach because I couldn't find any IronJacamar releases published as JBoss modules. I assume the resulting ZIP can be hosted on Teiid SourceForge or somewhere similar. https://gist.github.com/Tom9729/fe28e904f9ce4048382e This is a patch file for the install script that updated the IronJacamar module. The SHA1 and URL parts need to be filled in once the module has been made and it has been uploaded somewhere. https://gist.github.com/Tom9729/a158354a3468dda731d6 > EAP 6.3 - JDBC Datasources Test Connection > ------------------------------------------ > > Key: TEIID-3206 > URL: https://issues.jboss.org/browse/TEIID-3206 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 8.9, 8.10 > Reporter: Tom Arnold > Assignee: Steven Hawkins > > Using `Test Connection` for JDBC Datasources seems to be broken in the standalone server built from 8.9.x and master. This is an issue with EAP 6.3 Alpha1. > This is reproducible with the built-in ExampleDS H2 database. Run the `install.sh`, unzip, add a management user (bin/add-user.sh), start the server, and then login to the admin console (localhost:9990). Then go to Profile -> Connector -> Data Sources -> ExampleDS -> Connection -> Test Connection. It will fail with this error: "JBAS010440: failed to invoke operation: JBAS010447: Connection is not valid. This also happens with Oracle and PostgreSQL datasources. > The datasources seem to work despite this, but it would be good to understand the root cause and get it fixed if possible. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3046) Add support for recursive common table expressions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3046?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3046. ----------------------------------- Resolution: Done No checking the session variable teiid.maxRecursion to control how many recursions/iterations processing can make prior to throwing an exception. This will default to 10000. Ideally we'd allow the common table to be incrementally used so that it doesn't need to be fully processed all of the time, but currently we lack a good infrastructure to do that (we now use actual temp tables rather than just a linear tuple buffer as in the old days such that we can just append have the logic block appropriately). > Add support for recursive common table expressions > -------------------------------------------------- > > Key: TEIID-3046 > URL: https://issues.jboss.org/browse/TEIID-3046 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.10 > > > We should add support for recursive CTE. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3211) Add ui support for whole texttable no trim

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3211: ------------------------------------- Summary: Add ui support for whole texttable no trim Key: TEIID-3211 URL: https://issues.jboss.org/browse/TEIID-3211 Project: Teiid Issue Type: Enhancement Components: Query Engine Environment: Teiid 8.8.0 Final Reporter: Shiveeta Mattoo Assignee: Steven Hawkins Fix For: 8.10 In case of Delimited text files, currently, we always TRIM the input data. The enhancement request is to make this behaviour configurable, and let user determine, whether the leading or trailing spaces for the column text should be trimmed or not. Refer thread https://developer.jboss.org/message/905658?et=watches.email.thread#905658 for complete background discussion. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3167) Enhance TEXTTABLE to support TRIM as a configurable option for Delimited Text Files

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3167?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3167. ----------------------------------- Resolution: Done Added a general NO TRIM option for the entire text table and updated the reference. > Enhance TEXTTABLE to support TRIM as a configurable option for Delimited Text Files > ----------------------------------------------------------------------------------- > > Key: TEIID-3167 > URL: https://issues.jboss.org/browse/TEIID-3167 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Environment: Teiid 8.8.0 Final > Reporter: Shiveeta Mattoo > Assignee: Steven Hawkins > Labels: File-connector, TEXTTABLE, TRIM > Fix For: 8.10 > > > In case of Delimited text files, currently, we always TRIM the input data. > The enhancement request is to make this behaviour configurable, and let user determine, whether the leading or trailing spaces for the column text should be trimmed or not. > Refer thread https://developer.jboss.org/message/905658?et=watches.email.thread#905658 for complete background discussion. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3210) Refine ordered comparison pushdown support

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3210?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3210. ----------------------------------- Resolution: Done Added supportsCompareCriteriaOrderedExclusive, which defaults to supportsCompareCriteriaOrdered Updated temp table support as well. > Refine ordered comparison pushdown support > ------------------------------------------ > > Key: TEIID-3210 > URL: https://issues.jboss.org/browse/TEIID-3210 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.10 > > > The support for <, > and <=.>= was split a between comparison ordered and negated support (the logic being that not >= is the same as < and with or support <> is implied). However it's more natural that all inclusive/exclusive comparisons are supported. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3169) Update infinispan-cache translator to use DSLQuery in library mode

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3169?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3169: ------------------------------------ With the changes that were committed for TEIID-3137, it also includes the changes to support DSL querying in library mode. > Update infinispan-cache translator to use DSLQuery in library mode > ------------------------------------------------------------------ > > Key: TEIID-3169 > URL: https://issues.jboss.org/browse/TEIID-3169 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Van Halbert > > The curent lucene query logic needs to be upgraded to use the DSL query logic to perform searches on the cache when in library mode. This logic is currently being used in the infinispan-cache-dsl translator. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2052) Add Problem/Resolution to query problem using the query plan

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2052?page=com.atlassian.jira.plugin... ] Work on TEIID-2052 started by Van Halbert. ------------------------------------------ > Add Problem/Resolution to query problem using the query plan > ------------------------------------------------------------ > > Key: TEIID-2052 > URL: https://issues.jboss.org/browse/TEIID-2052 > Project: Teiid > Issue Type: Enhancement > Components: Documentation > Affects Versions: 7.7.1 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Optional > Attachments: INClauseNotPushedDown.odt > > > Adding content that could be used for query problem resolution. The initial attachment does the following: > - states the query problem (i.e., not pushing down the "IN" clause) > - provides the query plan (and debug log) for the query being submitted > - provides recommendations for resolving the problem > - then indicates how this problem was resolved and what the resulting query plan / debug log > The idea here is to continue to add other problem scenarios so that this information is really useful for resolving issues. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2052) Add Problem/Resolution to query problem using the query plan

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2052?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2052: ------------------------------------ The process has started to help explain the query plan. > Add Problem/Resolution to query problem using the query plan > ------------------------------------------------------------ > > Key: TEIID-2052 > URL: https://issues.jboss.org/browse/TEIID-2052 > Project: Teiid > Issue Type: Enhancement > Components: Documentation > Affects Versions: 7.7.1 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Optional > Attachments: INClauseNotPushedDown.odt > > > Adding content that could be used for query problem resolution. The initial attachment does the following: > - states the query problem (i.e., not pushing down the "IN" clause) > - provides the query plan (and debug log) for the query being submitted > - provides recommendations for resolving the problem > - then indicates how this problem was resolved and what the resulting query plan / debug log > The idea here is to continue to add other problem scenarios so that this information is really useful for resolving issues. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2014