April 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2930) SCROLL keyword for DECLARE CURSOR not being parsed correctly

by Johnathon Lee (JIRA)

Johnathon Lee created TEIID-2930: ------------------------------------ Summary: SCROLL keyword for DECLARE CURSOR not being parsed correctly Key: TEIID-2930 URL: https://issues.jboss.org/browse/TEIID-2930 Project: Teiid Issue Type: Bug Components: ODBC Affects Versions: 7.7.8 Reporter: Johnathon Lee Assignee: Steven Hawkins The DECLARE cursor is defined as [1]. However, in [2] line #155, the SCROLL keyword is not being matched. Correction would be to match the pattern fully as defined in [1] [1] http://www.postgresql.org/docs/8.4/static/sql-declare.html [2] https://github.com/teiid/teiid/blob/master/runtime/src/main/java/org/teii... Example of error: TRACE [org.teiid.ODBC] (New I/O server worker #3-1) invoking server method: executeQuery [BEGIN;declare "SQL_CUR0x11ad4120" scroll cursor for <SQL QUERY>;fetch 100 in "SQL_CUR0x11ad4120"] DEBUG [org.teiid.ODBC] (New I/O server worker #3-1) Modified Query: START TRANSACTION FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing: requestID -1 commands: [START TRANSACTION] expecting: EITHER FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing as transaction statement TRACE [org.teiid.ODBC] (New I/O server worker #3-1) invoking client method: sendUpdateCount [BEGIN, 0] FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing: requestID -1 commands: [show client_encoding] expecting: RESULTSET FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing as show statement FINER [org.teiid.jdbc] (New I/O server worker #3-1) Creating ResultSet requestID: -1 beginRow: 1 resultsColumns: 1 parameters: 0 TRACE [org.teiid.ODBC] (New I/O server worker #3-1) invoking client method: setEncoding [UTF-8] FINE [org.teiid.jdbc] (New I/O server worker #3-1) Statement closed successfully. DEBUG [org.teiid.ODBC] (New I/O server worker #3-1) Modified Query: declare "SQL_CUR0x11ad4120" scroll cursor for <SQL QUERY> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2929) Provide ability define "execution properties" as VDB properties

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2929?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2929: ---------------------------------- Forum Reference: https://community.jboss.org/thread/239728 The forum post where this comes from involves setting partialResultsMode. So the approach here would be either * have the vdb properties simply be default values for the session/execution properties. I think this makes sense for well known properties at least. * allow there to be a server side initialization string on the vdb, such that any set of statements can be run. > Provide ability define "execution properties" as VDB properties > --------------------------------------------------------------- > > Key: TEIID-2929 > URL: https://issues.jboss.org/browse/TEIID-2929 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > > Currently if user needs to set any execution properties on their connection, with JDBC they can define on the URL or use "SET " statement to issue a query. In ODBC can also use "SET " method. > However, when working with packaged applications and ODBC or in some situations it may be better to configure these properties VDB wide so that all the connections are using same execution properties. > This JIRA proposes ability to add execution properties as vdb properties in vdb.xml file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2928) Allow for backwards compatibility with multiple security domains per transport

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2928?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2928. ----------------------------------- Resolution: Done Consolidated logic as best as possible to the sessionserviceimpl so that multiple domains per transport is still a supported setting. But this will likely be removed from Teiid 9. > Allow for backwards compatibility with multiple security domains per transport > ------------------------------------------------------------------------------ > > Key: TEIID-2928 > URL: https://issues.jboss.org/browse/TEIID-2928 > Project: Teiid > Issue Type: Quality Risk > Components: Server > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.8 > > > With TEIID-2863 the ability to assign multiple security domains per transport was removed in favor of a per vdb scheme. However we still need to have it in place for backwards compatibility. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2801) HIVE2: HAVING specified without GROUP BY

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2801?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2801. --------------------------------- > HIVE2: HAVING specified without GROUP BY > ----------------------------------------- > > Key: TEIID-2801 > URL: https://issues.jboss.org/browse/TEIID-2801 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.6 > Environment: Teiid with HIVE1 and HIVE2 > Reporter: Ivan Chan > Assignee: Steven Hawkins > Labels: teiid > Fix For: 8.7 > > > If SQL contains HAVING, with group by. > HIVE2 will throw the following exception: > HAVING specified without GROUP BY, errorCode:40000, SQLState:42000) > at org.apache.hadoop.hive.service.ThriftHive$execute_result$execute_resultStandardScheme.read(ThriftHive.java:1494) > at org.apache.hadoop.hive.service.ThriftHive$execute_result$execute_resultStandardScheme.read(ThriftHive.java:1480) > at org.apache.hadoop.hive.service.ThriftHive$execute_result.read(ThriftHive.java:1430) > at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78) > at org.apache.hadoop.hive.service.ThriftHive$Client.recv_execute(ThriftHive.java:116) > at org.apache.hadoop.hive.service.ThriftHive$Client.execute(ThriftHive.java:103) > at org.apache.hadoop.hive.jdbc.HivePreparedStatement.executeImmediate(HivePreparedStatement.java:175) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2897) texttable performance enhancements

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2897?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2897. --------------------------------- > texttable performance enhancements > ---------------------------------- > > Key: TEIID-2897 > URL: https://issues.jboss.org/browse/TEIID-2897 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7 > > > texttable processing should be enhanced to be multi-threaded and should be able to determine if a limit is in effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2890) IndexOutOfBoundsException when using GROUP BY

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2890?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2890. --------------------------------- > IndexOutOfBoundsException when using GROUP BY > --------------------------------------------- > > Key: TEIID-2890 > URL: https://issues.jboss.org/browse/TEIID-2890 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Reporter: Tom Arnold > Assignee: Steven Hawkins > Labels: 8.7, grouping, translator > Fix For: 8.7 > > > I have a translator that does not support aggregates or grouping. I am using a view to try to normalize data from several sources. I am duplicating some of the fields as an approximation. I have existing software that is querying with GROUP BY, and sometimes this happens. > This query works fine in 8.6: > {code:sql} > select identifier > from foo.items > group by identifier, identifier; > {code} > In 8.7 this happens: > {code} > 10:15:24,280 ERROR [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue39) njknuxobPkVY TEIID30019 Unexpected exception for request njknuxobPkVY.3: java.lang.IndexOutOfBoundsException: Index: 1, Size: 1 > at java.util.ArrayList.rangeCheck(ArrayList.java:604) [rt.jar:1.7.0_02] > at java.util.ArrayList.get(ArrayList.java:382) [rt.jar:1.7.0_02] > at org.teiid.query.processor.relational.MergeJoinStrategy.compareTuples(MergeJoinStrategy.java:313) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.relational.GroupingNode.sameGroup(GroupingNode.java:488) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.relational.GroupingNode.groupPhase(GroupingNode.java:414) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.relational.GroupingNode.nextBatchDirect(GroupingNode.java:336) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:136) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:159) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:141) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:435) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:320) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:248) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:273) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.7.0.Beta2-SNAPSHOT.jar:8.7.0.Beta2-SNAPSHOT] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_02] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_02] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_02] > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2826) Change build to use zip translator packaging when building jboss kit

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2826?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2826. --------------------------------- > Change build to use zip translator packaging when building jboss kit > -------------------------------------------------------------------- > > Key: TEIID-2826 > URL: https://issues.jboss.org/browse/TEIID-2826 > Project: Teiid > Issue Type: Sub-task > Components: Build/Kits > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Labels: Beta2 > Fix For: 8.7 > > > Change build to use zip translator packaging when building jboss kit -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2758) add org.teiid.disableResultSetFetchSize property to ignore client set fetch size on resultset

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2758?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2758. --------------------------------- > add org.teiid.disableResultSetFetchSize property to ignore client set fetch size on resultset > ----------------------------------------------------------------------------------------------- > > Key: TEIID-2758 > URL: https://issues.jboss.org/browse/TEIID-2758 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Connector > Affects Versions: 7.7.8 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 8.7 > > > add org.teiid.disableResultSetFetchSize property to ignore client set fetch size on resultset. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2853) Aggregation fails with select all

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2853?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2853. --------------------------------- > Aggregation fails with select all > --------------------------------- > > Key: TEIID-2853 > URL: https://issues.jboss.org/browse/TEIID-2853 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.1 > Reporter: Alex K. > Assignee: Steven Hawkins > Fix For: 8.7 > > > This query fails for me on Teiid 8.1 and 8.6 > {code:sql} > WITH qry_0 as > (SELECT > floor(t.f) AS a1, floor(t2.f) as b1 > FROM > mysql.test_e AS t, oracle.test_e as t2 WHERE (t.f=t2.f) > GROUP BY > t.f, t2.f) > SELECT * from qry_0 GROUP BY a1, b1; > {code} > This is the exception > {code} > 01:18:03,883 ERROR [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue16) qioVIE+5j6a2 TEIID30019 Unexpected exception forrequest qioVIE+5j6a2.9: java.lang.NullPointerException > at org.teiid.query.processor.relational.GroupingNode.initialize(GroupingNode.java:192) [teiid-engine-8.6.0.Final.jar:8.6.0.Final] > at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:94) [teiid-engine-8.6.0.Final.jar:8.6.0.Final] > at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:100) [teiid-engine-8.6.0.Final.jar:8.6.0.Final] > at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:100) [teiid-engine-8.6.0.Final.jar:8.6.0.Final] > at org.teiid.query.processor.relational.RelationalPlan.initialize(RelationalPlan.java:89) [teiid-engine-8.6.0.Final.jar:8.6.0.Final] > at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:226) [teiid-engine-8.6.0.Final.jar:8.6.0.Final] > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:138) [teiid-engine-8.6.0.Final.jar:8.6.0.Final] > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) [teiid-engine-8.6.0.Final.jar:8.6.0.Final] > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:159) [teiid-engine-8.6.0.Final.jar:8.6.0.Final] > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:141) [teiid-engine-8.6.0.Final.jar:8.6.0.Final] > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:435) [teiid-engine-8.6.0.Final.jar:8.6.0.Final] > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:320) [teiid-engine-8.6.0.Final.jar:8.6.0.Final] > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.6.0.Final.jar:8.6.0.Final] > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:248) [teiid-engine-8.6.0.Final.jar:8.6.0.Final] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:273) [teiid-engine-8.6.0.Final.jar:8.6.0.Final] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.6.0.Final.jar:8.6.0.Final] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.6.0.Final.jar:8.6.0.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > atjava.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2771) Data role checking should be enabled by default for embedded

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2771?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2771. --------------------------------- > Data role checking should be enabled by default for embedded > ------------------------------------------------------------ > > Key: TEIID-2771 > URL: https://issues.jboss.org/browse/TEIID-2771 > Project: Teiid > Issue Type: Enhancement > Components: Embedded > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.2, 8.7 > > > Data role checking currently has to be manually enabled for embedded by setting an authorizationvalidator on the embeddedconfiguration. This should instead default to the built-in data roles authorization. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 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 2014