[jira] [Commented] (CASSANDRA-11295) Make custom filtering more extensible via custom classes

["Sylvain Lebresne (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-11295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226240#comment-15226240 ] 

Sylvain Lebresne commented on CASSANDRA-11295:
----------------------------------------------

Lgtm, +1.

Nit: the patch removes the {{final}} from {{class CustomExpression}}. It's really not a big deal but I guess that's not necessary anymore.


> Make custom filtering more extensible via custom classes 
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-11295
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11295
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Local Write-Read Paths
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>            Priority: Minor
>             Fix For: 3.x
>
>
> At the moment, the implementation of {{RowFilter.CustomExpression}} is tightly bound to the syntax designed to support non-CQL search syntax for custom 2i implementations. It might be interesting to decouple the two things by making the custom expression implementation and serialization a bit more pluggable. This would allow users to add their own custom expression implementations to experiment with custom filtering strategies without having to patch the C* source. As a minimally invasive first step, custom expressions could be added programmatically via {{QueryHandler}}. Further down the line, if this proves useful and we can figure out some reasonable syntax we could think about adding the capability in CQL in a separate ticket. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)