[
https://issues.apache.org/jira/browse/CASSANDRA-10221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14720006#comment-14720006
]
Sylvain Lebresne commented on CASSANDRA-10221:
----------------------------------------------
Ok, so do we agree that by "arbitrary", you just mean any predicate as
supported by the existing syntax. Or to put it another way, am I right in
saying that what you're asking is that C* would accept any
non-completely-illogical query assuming you provide {{ALLOW FILTERING}}? If so,
then that's kind of what CASSANDRA-6377 is intended to (at least that was I
plan on doing for that ticket).
> arbitrary predicate pushdown on CL=ONE
> --------------------------------------
>
> Key: CASSANDRA-10221
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10221
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jon Haddad
>
> For analytics workloads (in particular I'm thinking spark) it would be nice
> if we could add any predicate to the WHERE clause. I added the CL=ONE
> requirement since it seems like this may be insane to do with any other level
> of consistency.
> Currently in the spark connector if you want to filter on an arbitrary column
> of a table, you have to pull the entire table in memory via what is
> effectively a distributed SELECT * with token ranges and CL=ONE (typically).
> It would be much nicer to avoid pulling the extra data into memory and just
> noop on the row if it doesn't satisfy the predicates.
> I think for sanity this should require the ALLOW FILTERING clause.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
