Mondrian not returning the correct row values for the "ROW" dimention
---------------------------------------------------------------------
Key: TEIID-1628
URL: https://issues.jboss.org/browse/TEIID-1628
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 7.4
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 7.4.1
Currently for the ROW dimension the returned data is a label not the data underneath it. COLUMNS are fine.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Order by may be applied incorrectly with pushed aggregate
---------------------------------------------------------
Key: TEIID-1678
URL: https://issues.jboss.org/browse/TEIID-1678
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.1
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 7.4.1, 7.5
If a decomposed grouping is not pushed below the accessnode, then the merge join ordering may be pushed below it - which will destroy the ordering. The order by should be above the grouping and then should be combined with the grouping during plan sorts.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
ruleimplementjoin strategy may generate an order by that does not use a relevant index
--------------------------------------------------------------------------------------
Key: TEIID-1528
URL: https://issues.jboss.org/browse/TEIID-1528
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
If a table is given additional join criteria not covered by an index or if a composite key is being used ruleimplementjoinstrategy may - either add an item not covered by the index to the order by or not use the proper order of the index columns.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
XMLTABLE processing should support streaming when possible
----------------------------------------------------------
Key: TEIID-1448
URL: https://issues.jboss.org/browse/TEIID-1448
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.1
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Just like the old xml/relational processing if the xpaths/xquery used is sufficiently restrictive the xml can be processed in a streaming fashion - where independent siblings are processed independently without loading the rest of the document.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Cache invalidation
------------------
Key: TEIID-1507
URL: https://issues.jboss.org/browse/TEIID-1507
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.4
Reporter: Steven Hawkins
Assignee: Steven Hawkins
We should provide an interface and internally react to events of updates to vdbname/version/table/row and purge resultset cache and possibly materialization.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Index metadata issues
---------------------
Key: TEIID-1597
URL: https://issues.jboss.org/browse/TEIID-1597
Project: Teiid
Issue Type: Bug
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Using index metadata will cause multisource usage of procedures to always fail and not allow xml staging tables to be referenced by user queries.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Increase audit information
--------------------------
Key: TEIID-1586
URL: https://issues.jboss.org/browse/TEIID-1586
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Affects Versions: 8.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
AuditMessages should include the Session object and the request id, so that custom logging can access additional information. login events should also capture more detail including IP (and possibly MAC), etc.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Exists subqueries will unnest by default
----------------------------------------
Key: TEIID-1677
URL: https://issues.jboss.org/browse/TEIID-1677
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.4
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Exists subqueries should respect the default unnest property, rather than always unnesting.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Unable to build on a file system that isn't formatted to support case-sensitivity
---------------------------------------------------------------------------------
Key: TEIID-1639
URL: https://issues.jboss.org/browse/TEIID-1639
Project: Teiid
Issue Type: Bug
Components: Build/Kits
Affects Versions: 7.4, 7.4.1
Reporter: Van Halbert
Assignee: Van Halbert
Priority: Critical
Trying to build the 7.4.1 branch and trunk, but unable to due to the metadata project contains 2 vdb files; Test.vdb and test.vdb in the the src/test/resources directory. Each are for different tests. This problem is due to a filesystem hasn't been formatted to support case-sensititivity.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Provide something like an ECHO statement in the procedure language that can assist a user in debugging their procedure logic
-----------------------------------------------------------------------------------------------------------------------------
Key: TEIID-1632
URL: https://issues.jboss.org/browse/TEIID-1632
Project: Teiid
Issue Type: Feature Request
Components: Server
Affects Versions: 7.4
Reporter: Van Halbert
Assignee: Steven Hawkins
Provide something like an ECHO statement in the procedure language that can assist a user in debugging their procedure logic
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira