[
https://issues.jboss.org/browse/TEIID-4717?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-4717:
-------------------------------------
From the blog you shared about ALLOW FILTERING, essentially Teiid will
do the same when column is set to not searchable. It will get all the table contents and
then filter out not non matching criteria. So, I am no seeing any downside to use ALLOW
FILTERING. The question is do you want to do this on all the columns of table or just some
specific ones? IMO doing on all of them is fine as that would be default behavior anyway
if you not defined the property ALLOW FILTERING. Then question becomes, why not do this
by default on all tables? i.e. always tack on ALLOW FILTERING to query?
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)