[JBoss JIRA] Created: (TEIID-1498) Incorrect rewrite of not disjunctive criteria
by Steven Hawkins (JIRA)
Incorrect rewrite of not disjunctive criteria
----------------------------------------------
Key: TEIID-1498
URL: https://issues.jboss.org/browse/TEIID-1498
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Critical
Fix For: 7.4
The rewrite of a condition such as "not((a or b) AND c)" with a,b,c predicates where c a is predicate that is negatable, such as col1 = 1. The result should have the negated form of col1 <> 1, but instead has col1 = 1. This is because the col1 = 1 predicate is repeated in the result, but not cloned and the rewriter modifies the same instance.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] Created: (TEIID-1489) Teiid assumes fqns in transformations, but they are no longer required to be there
by Steven Hawkins (JIRA)
Teiid assumes fqns in transformations, but they are no longer required to be there
----------------------------------------------------------------------------------
Key: TEIID-1489
URL: https://issues.jboss.org/browse/TEIID-1489
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.1
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Critical
Fix For: 7.4
It looks like with the uuid refactoring we no long maintain that the designer indexed transformations will contain only fully qualified group names.
This will cause a good deal of problems at runtime as partially qualified names are subject to visibility rules and can conflict with session level tables.
I would prefer to address this on the teiid though better metadata logic, rather than requiring fqns in transformation queries.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] Created: (TEIID-1492) StackOverflowError in DefaultCache
by Mark Addleman (JIRA)
StackOverflowError in DefaultCache
----------------------------------
Key: TEIID-1492
URL: https://issues.jboss.org/browse/TEIID-1492
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.2
Environment: Windows & Linux
Reporter: Mark Addleman
Assignee: Steven Hawkins
Intermittently, we get the stack overflow error. It doesn't seem to be related to the query.
java.lang.StackOverflowError
at org.teiid.cache.DefaultCache.remove(DefaultCache.java:164)
at org.teiid.cache.DefaultCache.validate(DefaultCache.java:119)
at org.teiid.cache.DefaultCache.access$000(DefaultCache.java:36)
at org.teiid.cache.DefaultCache$1.removeEldestEntry(DefaultCache.java:86)
at java.util.LinkedHashMap.putImpl(LinkedHashMap.java:411)
at java.util.LinkedHashMap.put(LinkedHashMap.java:370)
at org.teiid.cache.DefaultCache.remove(DefaultCache.java:164)
at org.teiid.cache.DefaultCache.validate(DefaultCache.java:119)
at org.teiid.cache.DefaultCache.access$000(DefaultCache.java:36)
at org.teiid.cache.DefaultCache$1.removeEldestEntry(DefaultCache.java:86)
at java.util.LinkedHashMap.putImpl(LinkedHashMap.java:411)
at java.util.LinkedHashMap.put(LinkedHashMap.java:370)
at org.teiid.cache.DefaultCache.remove(DefaultCache.java:164)
at org.teiid.cache.DefaultCache.validate(DefaultCache.java:119)
at org.teiid.cache.DefaultCache.access$000(DefaultCache.java:36)
at org.teiid.cache.DefaultCache$1.removeEldestEntry(DefaultCache.java:86)
at java.util.LinkedHashMap.putImpl(LinkedHashMap.java:411)
at java.util.LinkedHashMap.put(LinkedHashMap.java:370)
at org.teiid.cache.DefaultCache.remove(DefaultCache.java:164)
at org.teiid.cache.DefaultCache.validate(DefaultCache.java:119)
at org.teiid.cache.DefaultCache.access$000(DefaultCache.java:36)
at org.teiid.cache.DefaultCache$1.removeEldestEntry(DefaultCache.java:86)
at java.util.LinkedHashMap.putImpl(LinkedHashMap.java:411)
at java.util.LinkedHashMap.put(LinkedHashMap.java:370)
at org.teiid.cache.DefaultCache.remove(DefaultCache.java:164)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] Created: (TEIID-1473) Don't batch more rows than is needed when query contains limit but translator does not support limit
by Howard Abrams (JIRA)
Don't batch more rows than is needed when query contains limit but translator does not support limit
----------------------------------------------------------------------------------------------------
Key: TEIID-1473
URL: https://issues.jboss.org/browse/TEIID-1473
Project: Teiid
Issue Type: Enhancement
Reporter: Howard Abrams
Assignee: Steven Hawkins
Priority: Minor
Teiid shouldn't try to batch more rows than is needed when query contains limit and translator does not support limit.
For example, say there is a translator that exposes a table "A", but does not support limit.
select * from A limit 2
will currently select an entire batch of rows (1024?) from A, instead of just stopping after 2 rows.
Likewise, if the translator supports neither offset nor limit, and the query contains both, Teiid should not try to batch more that (offset + limit) rows.
This is marked as "Minor" because the workaround of naively supporting limit and offset within a translator is not too hard.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months