[
https://issues.jboss.org/browse/TEIID-4717?page=com.atlassian.jira.plugin...
]
Vijay K commented on TEIID-4717:
--------------------------------
IMHO, appending ALLOW FILTERING to all the tables of the model by default may lead to
unintended consequences in-terms of performance, I think that is the reason why Cassandra
is warning. It should be left to discreation of the developer, so that he/she understands
the consequences and OK with that.
Moreover some may not be interested in applying ALLOW FILTERING hint on all the tables,
they may need the flexibility to allow at table level (as in my case)
Add Support for 'ALLOW FILTERING' in Teiid Cassandra
Translator
---------------------------------------------------------------
Key: TEIID-4717
URL:
https://issues.jboss.org/browse/TEIID-4717
Project: Teiid
Issue Type: Enhancement
Components: Misc. Connectors
Reporter: Vijay K
Labels: cassandra
Fix For: 9.3
At certain times it is unavoidable to use few columns in the where clause which are not
part of the index, in that case Cassandra driver throws error
{color:red}Bad Request: Cannot execute this query as it might involve data filtering and
thus may have unpredictable performance. If you want to execute this query despite the
performance unpredictability, use ALLOW FILTERING{color}
As a user I should be able to configure the Cassandra translator to append *ALLOW
FILTERING* to the generated query (CQL)
References:
https://www.datastax.com/dev/blog/allow-filtering-explained-2
https://developer.jboss.org/thread/239011
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)