cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-11295) Make custom filtering more extensible via custom classes
Date Thu, 03 Mar 2016 15:56:18 GMT


Sam Tunnicliffe commented on CASSANDRA-11295:

Force-pushed an update which adds a new expression type, {{UserExpression}}, to preserve {{CustomExpression}}
for it's original intended use and avoid overloading it. {{UserExpression}} is declared abstract
and concrete implementations must be registered before they're used to ensure that they can
be correctly deserialized. In general, I think this is a cleaner and more robust solution,
though use of such expressions during upgrades will still require some finesse. 

> Make custom filtering more extensible via custom classes 
> ---------------------------------------------------------
>                 Key: CASSANDRA-11295
>                 URL:
>             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

View raw message