[teiid-issues] [JBoss JIRA] (TEIID-2724) Suggestion for Cassandra: implement fallback plan if push-down CQL fails

[Steven Hawkins (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins updated TEIID-2724:
----------------------------------

    Issue Type: Enhancement  (was: Bug)
      Priority: Minor  (was: Major)


Defaulting to no filtering seems dangerous.  It would be best to attempt to capture under what scenarios push down is appropriate.  If this proves too difficult (for instance introducing too much extension metadata/capabilities) then we could add an option for this.
                
> Suggestion for Cassandra:  implement fallback plan if push-down CQL fails
> -------------------------------------------------------------------------
>
>                 Key: TEIID-2724
>                 URL: https://issues.jboss.org/browse/TEIID-2724
>             Project: Teiid
>          Issue Type: Enhancement
>          Components: Query Engine
>    Affects Versions: 8.6
>         Environment: Teiid 8.6 with Cassandra
>            Reporter: Ivan Chan
>            Assignee: Steven Hawkins
>            Priority: Minor
>              Labels: teiid
>
> Sometimes push down sql doesn't work in Cassandra database because most of the time filtering only works on petition key or index column.   For example, it won't be possible to apply "IN" clause on non-petition key column.  Therefore, I suggest if push down sql fails to execute, I would like to see Teiid to the filtering using Teiid in-memory engine.  Thanks.

--
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