[
https://issues.apache.org/jira/browse/CASSANDRA-11295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15175368#comment-15175368
]
Sam Tunnicliffe commented on CASSANDRA-11295:
---------------------------------------------
Pushed a branch with fairly trivial changes to allow the serializer for custom
expressions to be plugged in via a system property. In the usual case,
behaviour remains identical with before, so it's very low impact. The first new
commit exposes a bit more of a statement's restrictions to the {{QueryHandler}}.
||branch||testall||dtest||
|[11295-trunk|https://github.com/beobal/cassandra/tree/11295-trunk]|[testall|http://cassci.datastax.com/view/Dev/view/beobal/job/beobal-11295-trunk-testall]|[dtest|http://cassci.datastax.com/view/Dev/view/beobal/job/beobal-11295-trunk-dtest]|
> 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)
