[
https://issues.apache.org/jira/browse/CASSANDRA-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830177#action_12830177
]
Gary Dusbabek commented on CASSANDRA-754:
-----------------------------------------
I think the way you're parsing and validating the API properties could be
simplified. First approach is to punt on validation until setup is called. Or
if you think validation is best performed in DD, have a static validate()
method in each impl class that is called reflectively. The upshot is that you
can get away with using a Map<String, String> and get rid of all the *Property
related methods. As it stands now, if new property types come along, DD and
IPluggableAPI will need to be modified to handle them.
> Pluggable API with a simple HTTP+JSON daemon
> --------------------------------------------
>
> Key: CASSANDRA-754
> URL: https://issues.apache.org/jira/browse/CASSANDRA-754
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Ted Zlatanov
> Priority: Minor
> Attachments: 001-CASSANDRA-754-api-reorg.patch,
> 001-CASSANDRA-754-api-reorg.patch, 002-CASSANDRA-754-thriftdaemon.patch,
> 002-CASSANDRA-754-thriftdaemon.patch, 003-CASSANDRA-754-configapi.patch,
> 003-CASSANDRA-754-configapi.patch, 004-CASSANDRA-754-onedaemon.patch,
> 005-CASSANDRA-754-avroconfig.patch, 006-CASSANDRA-754-daemonproperties.patch,
> 006-CASSANDRA-754-daemonproperties.patch
>
>
> Proposal of a simple pluggable API interface with a HTTP daemon implementation
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
