[
https://issues.apache.org/jira/browse/CASSANDRASC-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17090850#comment-17090850
]
Yifan Cai commented on CASSANDRASC-17:
--------------------------------------
It is fair to not support batch requests, as it adds bunch of complexity.
Regarding versioning, should the version be the root segment of the URL schema?
For example
{{/api/:version/nodes/:node_id/sstables/:path_to_file}}
Something out of the scope of the ticket. It could be very helpful to define a
set of web APIs in advance and provide the handler impls later, instead of "I
am adding a new API because I need XYZ feature". It helps to organize the APIs,
and keep the style consistent. As of now, there is no such ticket in sidecar
project to address it.
> Ensure sidecar can control multiple Cassandra instances
> -------------------------------------------------------
>
> Key: CASSANDRASC-17
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-17
> Project: Sidecar for Apache Cassandra
> Issue Type: Improvement
> Components: Configuration
> Reporter: Jon Haddad
> Priority: Normal
>
> Since we can run multiple hosts per node, we should allow a single sidecar
> process to control multiple Cassandra nodes.
> I am not sure if we should encode the id of the node in the URL or as a
> parameter that would have to be present in every request if using > 1 node.
> I lean towards the latter - meaning it’s a slight inconvenience for a very
> small group, rather than messing with the URL scheme for everyone else. I
> don’t hold this opinion very strongly though. I’d like to discuss before
> doing any work here.
> Thoughts?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
