[
https://issues.apache.org/jira/browse/CASSANDRA-10745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15061178#comment-15061178
]
Paulo Motta commented on CASSANDRA-10745:
-----------------------------------------
Thanks for the input [~sdurity]. We could probably make the
{{PropertyFileSnitch}} use the {{GossipingPropertyFileSnitch}} internally,
fetching only the local node's information from
{{cassandra-topology.properties}} file while ignoring other node's info from
this file (which will be propagated by gossip as in GPFS).
Alternatively we could still deprecate {{PropertyFileSnitch}} while making
{{GossipingPropertyFileSnitch}} support the {{cassandra-topology.properties}}
file to allow having a single global topology file.
> Deprecate PropertyFileSnitch
> ----------------------------
>
> Key: CASSANDRA-10745
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10745
> Project: Cassandra
> Issue Type: Improvement
> Components: Coordination, Distributed Metadata
> Reporter: Paulo Motta
> Priority: Minor
>
> Opening this ticket to discuss deprecating PropertyFileSnitch, since it's
> error-prone and more snitch code to maintain (See CASSANDRA-10243). Migration
> from existing cluster with PropertyFileSnitch to GossipingPropertyFileSnitch
> is straightforward.
> Is there any useful use case that can be achieved only with
> PropertyFileSnitch?
> If not objections, we would add deprecation warnings in 2.2.x, 3.0.x, 3.2 and
> deprecate in 3.4 or 3.6.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
