[
https://issues.jboss.org/browse/TEIID-1993?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-1993:
----------------------------------
Fix Version/s: 8.1
Priority: Minor (was: Major)
For non-union views (which will require inline view support) you can workaround by marking
the translator as supporting GROUP BY, but no aggregate functions nor the having clause.
However the translator will still be responsible for ensuring that if GROUP BY is used
instead of distinct, that the selected columns match the grouping columns or that an
appropriate subset of the distinct is projected.
For the case at hand, we need to detect the equvalence with distinct prior to view
removal, then the union will be appropriately changed from a UNION ALL to a UNION to
account for the DISTINCT operation.
Pushdown GROUP BY as DISTINCT when data source does not support
inline views
----------------------------------------------------------------------------
Key: TEIID-1993
URL:
https://issues.jboss.org/browse/TEIID-1993
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.7
Reporter: Mark Addleman
Assignee: Steven Hawkins
Priority: Minor
Fix For: 8.1
Attachments: pushdown-example.txt
The datasource does not support inline views but does support distinct.
See attached plan and
https://community.jboss.org/message/728556
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira