[
https://issues.apache.org/jira/browse/CASSANDRA-11295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15231089#comment-15231089
]
Henry Manasseh commented on CASSANDRA-11295:
--------------------------------------------
This looks useful for a query I am implementing. I looked at the code for
TestQueryHandler and have some questions.
1. How do you access the RowFilter from within the QueryHandler so that I could
call rowFilter.addUserExpression(UserExpression e) to register my custom
UserExpression?
2. Is a custom payload the only way to pass inputs to the user expression at
the moment (until there is a CQL syntax)?
If you have a sample you used for development/testing... would it be possible
to post to either Jira, github or via email? Thank you for any tips.
> 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.6
>
>
> 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)
