[
https://issues.apache.org/jira/browse/CASSANDRA-17059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433688#comment-17433688
]
Benedict Elliott Smith commented on CASSANDRA-17059:
----------------------------------------------------
I look forward to seeing a patch, as it seems like it may harm the clarity of
the codebase by forcing a migration away from {{Enum}} for {{Verb}}.
It would help to provide some concrete examples of the need for this feature,
as this does not appear to enable improved testing or any specific feature for
the project. If this is for an external use case, I think the ticket would
benefit from a fuller description of the use case.
> Support adding custom verbs at runtime
> --------------------------------------
>
> Key: CASSANDRA-17059
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17059
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Matt Fleming
> Priority: Normal
>
> Cassandra already has support for registering custom verbs at build time, but
> there's value in allowing verbs to be added at runtime since that enables new
> use cases where it's inconvenient or impossible to modify the Cassandra
> source.
> Additionally, apps that went to register new verbs benefit from running
> custom code after the default verb handlers execute. This can be achieved
> with straightforward modifications to the Sink interface (e.g. adding a
> PostSink class).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
