June 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2433) cannot specify both auto increment and primary key via ddl

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2433?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2433. --------------------------------- > cannot specify both auto increment and primary key via ddl > ---------------------------------------------------------- > > Key: TEIID-2433 > URL: https://issues.jboss.org/browse/TEIID-2433 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4 > > > the grammar does not accept auto increment and primary key -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2510) time-slice-in-millseconds setting typo

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2510?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2510. --------------------------------- > time-slice-in-millseconds setting typo > -------------------------------------- > > Key: TEIID-2510 > URL: https://issues.jboss.org/browse/TEIID-2510 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.4 > Environment: Running Teiid 8.4 Beta > Reporter: B Long > Assignee: Steven Hawkins > Priority: Trivial > Fix For: 8.4 > > > I assume "time-slice-in-millseconds" is missing an 'i'. Should be "time-slice-in-milliseconds". > May affect multiple versions. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2457) Assertion error with INTERSECT

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2457?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2457. --------------------------------- > Assertion error with INTERSECT > ------------------------------ > > Key: TEIID-2457 > URL: https://issues.jboss.org/browse/TEIID-2457 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.3, 7.7.6 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.4 > > > A sample query which produced the error is: SELECT IntKey FROM BQT1.SmallA INTERSECT SELECT IntNum FROM BQT1.SmallB ORDER BY INTKEY > How to reproduce: Run the query using a client such as Squirrel multiple times. The results varies from returning an Assertion to returning actual results. In my test I ran the query five times and it returned actual results twice and the Assertion 3 times. The Assertion can be seen below. > 2013-04-03 16:00:42,190 ERROR [org.teiid.PROCESSOR] (Worker4_QueryProcessorQueue146) Unexpected exception for request JyDs6MZ6d9zG.24 > java.lang.AssertionError: ASSERTION FAILED: expected reference to be not null > at org.teiid.core.util.Assertion.failed(Assertion.java:73) > at org.teiid.core.util.Assertion.isNotNull(Assertion.java:100) > at org.teiid.core.util.Assertion.isNotNull(Assertion.java:92) > at org.teiid.common.buffer.TupleBuffer.getBatch(TupleBuffer.java:217) > at org.teiid.common.buffer.TupleBuffer$1.getBatch(TupleBuffer.java:331) > at org.teiid.common.buffer.AbstractTupleSource.getCurrentTuple(AbstractTupleSource.java:61) > at org.teiid.common.buffer.AbstractTupleSource.hasNext(AbstractTupleSource.java:91) > at org.teiid.query.processor.relational.MergeJoinStrategy.process(MergeJoinStrategy.java:163) > at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:212) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:280) > at org.teiid.query.processor.BatchIterator.finalRow(BatchIterator.java:70) > at org.teiid.common.buffer.AbstractTupleSource.getCurrentTuple(AbstractTupleSource.java:69) > at org.teiid.query.processor.BatchIterator.getCurrentTuple(BatchIterator.java:85) > at org.teiid.common.buffer.AbstractTupleSource.nextTuple(AbstractTupleSource.java:48) > at org.teiid.query.processor.relational.SortUtility.initialSort(SortUtility.java:248) > at org.teiid.query.processor.relational.SortUtility.sort(SortUtility.java:185) > at org.teiid.query.processor.relational.SortNode.sortPhase(SortNode.java:99) > at org.teiid.query.processor.relational.SortNode.nextBatchDirect(SortNode.java:88) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:280) > at org.teiid.query.processor.relational.LimitNode.nextBatchDirect(LimitNode.java:100) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:280) > at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:176) > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:139) > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:105) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:147) > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:375) > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:288) > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49) > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:216) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:244) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:122) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:292) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2452) Oracle pushdown of like_regex is incorrect

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2452?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2452. --------------------------------- > Oracle pushdown of like_regex is incorrect > ------------------------------------------ > > Key: TEIID-2452 > URL: https://issues.jboss.org/browse/TEIID-2452 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 7.5 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4 > > > The pushdown for oracle needs to use function notation, rather than an infix operator. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2063) NPE with proc relational query

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2063?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2063. --------------------------------- > NPE with proc relational query > ------------------------------ > > Key: TEIID-2063 > URL: https://issues.jboss.org/browse/TEIID-2063 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.4, 7.7.3 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.1 > > > A proc relational query using a table function or other source without an access node will fail with an NPE, for example: > select param1, param2, e1, e2 from pm1.vsp26 as x, texttable('abc' columns a string) as y where param1=1 and param2='a' -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2332) Better handling for pg transport rewrite

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2332?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2332. --------------------------------- > Better handling for pg transport rewrite > ---------------------------------------- > > Key: TEIID-2332 > URL: https://issues.jboss.org/browse/TEIID-2332 > Project: Teiid > Issue Type: Quality Risk > Components: ODBC > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.3 > > > The regexes used for handling several pg constructs are not generally safe and need to be aware of sql structure. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2353) Resolving order is not respected by the metadatavalidator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2353?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2353. --------------------------------- > Resolving order is not respected by the metadatavalidator > --------------------------------------------------------- > > Key: TEIID-2353 > URL: https://issues.jboss.org/browse/TEIID-2353 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.3 > > > When resolving a DDL based schema that uses view definitions that omit columns, the statement order of the schema matters to ensure that the views are properly resolved. Currently we'll resolve based upon name order, which can lead to erroneous validation exceptions. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2380) Planning failure with update subquery compensation with agg comparision

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2380?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2380. --------------------------------- > Planning failure with update subquery compensation with agg comparision > ----------------------------------------------------------------------- > > Key: TEIID-2380 > URL: https://issues.jboss.org/browse/TEIID-2380 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.3 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.3 > > > An update of the form: > delete from pm3.g1 where e1 = (SELECT MAX(e1) FROM pm3.g1 as z where e2 = pm3.g1.e2) > Such that the subquery cannot be pushed will result in the unaliased max being known by two different names which results in an AssertionError in the SortNode initialization. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2351) Inherent update compensating procedures are cached inappropriately

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2351?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2351. --------------------------------- > Inherent update compensating procedures are cached inappropriately > ------------------------------------------------------------------ > > Key: TEIID-2351 > URL: https://issues.jboss.org/browse/TEIID-2351 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.2 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 8.3 > > > TEIID-2226 introduced a regression where the initial compensation procedure plan will be reused for each update regardless of whether it is valid for other updates. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2479) Selecting from SYS model throws exception

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2479?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2479. --------------------------------- > Selecting from SYS model throws exception > ----------------------------------------- > > Key: TEIID-2479 > URL: https://issues.jboss.org/browse/TEIID-2479 > Project: Teiid > Issue Type: Bug > Affects Versions: 7.4 > Environment: Teiid 8.3 running in JBoss EAP 6.0 RPM install > java version "1.7.0_09-icedtea" > OpenJDK Runtime Environment (rhel-2.3.8.0.el6_4-x86_64) > OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode) > Reporter: Graeme Gillies > Assignee: Steven Hawkins > Fix For: 8.4 > > > We have a dynamic vdb deployed into our Teiid 8.3 environment, but whenever we connect to the vdb via the pgsql emulation socket using the standard postgresql tools, and attempt to select any value from any tables in the SYS scheama, we are given an error > {noformat} > TestVDB=> select * from sys.keys; > ERROR: Group specified is ambiguous, resubmit the query by fully qualifying the group name: pg_attribute > DETAIL: org.teiid.jdbc.TeiidSQLException: Group specified is ambiguous, resubmit the query by fully qualifying the group name: pg_attribute > TestVDB=> select * from sys.columns; > ERROR: Group specified is ambiguous, resubmit the query by fully qualifying the group name: pg_attribute > DETAIL: org.teiid.jdbc.TeiidSQLException: Group specified is ambiguous, resubmit the query by fully qualifying the group name: pg_attribute > TestVDB=> select * from sys.tables; > ERROR: Group specified is ambiguous, resubmit the query by fully qualifying the group name: pg_attribute > DETAIL: org.teiid.jdbc.TeiidSQLException: Group specified is ambiguous, resubmit the query by fully qualifying the group name: pg_attribute > TestVDB=> > {noformat} > It looks like the teiid parser is getting confused somehow with multiple pg_attribute fields on those tables or something. -- 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

12 years, 9 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 June 2013