11:13 a.m.
Partial Pushdown of WHERE clause columns
----------------------------------------
Key: TEIID-1568
URL: https://issues.jboss.org/browse/TEIID-1568
Project: Teiid
Issue Type: Feature Request
Reporter: Mark Addleman
Assignee: Steven Hawkins
We have some exotic data sources that can efficiently support WHERE clause filtering on
particular columns + operators combinations but are no better than Teiid for other
operation. In particular, suppose I have a data source that supplies columns A and B.
The data source can efficiently support A='some value' but may not support
A>'value' or A!='value' and does not support efficient processing of
column B at all. We would like an enhance supports* protocol to describe the particulars
of a data source's capabilities with finer detail.
Even partially solving this problem without operator support would be helpful
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:13 a.m.
New subject: [JBoss JIRA] Updated: (TEIID-1568) Partial Pushdown of WHERE clause columns
[
https://issues.jboss.org/browse/TEIID-1568?page=com.atlassian.jira.plugin...
]
Mark Addleman updated TEIID-1568:
---------------------------------
Priority: Minor (was: Major)
Partial Pushdown of WHERE clause columns
----------------------------------------
Key: TEIID-1568
URL: https://issues.jboss.org/browse/TEIID-1568
Project: Teiid
Issue Type: Feature Request
Reporter: Mark Addleman
Assignee: Steven Hawkins
Priority: Minor
We have some exotic data sources that can efficiently support WHERE clause filtering on
particular columns + operators combinations but are no better than Teiid for other
operation. In particular, suppose I have a data source that supplies columns A and B.
The data source can efficiently support A='some value' but may not support
A>'value' or A!='value' and does not support efficient processing of
column B at all. We would like an enhance supports* protocol to describe the particulars
of a data source's capabilities with finer detail.
Even partially solving this problem without operator support would be helpful
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:41 a.m.
New subject: [JBoss JIRA] Commented: (TEIID-1568) Partial Pushdown of WHERE clause columns
[
https://issues.jboss.org/browse/TEIID-1568?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1568:
---------------------------------------
The first cut at this behavior currently would be to set the searchability on B to
unsearchable. As long as the runtime type is comparable then all teiid predicate
operations will work as expected.
For the remaining columns, you can differentiate between supporting equality and greater
than, but not at a column level. It gets complicated quickly to have ongoing
conversations with the translator about what is supported, because the context of the
operation can matter as well. Having better support at least to a column level should be
easily addressed in 8.x.
Partial Pushdown of WHERE clause columns
----------------------------------------
Key: TEIID-1568
URL: https://issues.jboss.org/browse/TEIID-1568
Project: Teiid
Issue Type: Feature Request
Reporter: Mark Addleman
Assignee: Steven Hawkins
Priority: Minor
We have some exotic data sources that can efficiently support WHERE clause filtering on
particular columns + operators combinations but are no better than Teiid for other
operation. In particular, suppose I have a data source that supplies columns A and B.
The data source can efficiently support A='some value' but may not support
A>'value' or A!='value' and does not support efficient processing of
column B at all. We would like an enhance supports* protocol to describe the particulars
of a data source's capabilities with finer detail.
Even partially solving this problem without operator support would be helpful
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4989
days inactive
4989
days old
2 comments
2 participants
participants (2)
-
Mark Addleman (JIRA) -
Steven Hawkins (JIRA)