[ https://issues.apache.org/jira/browse/CASSANDRA-18438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738098#comment-17738098 ]
Stefan Miklosovic commented on CASSANDRA-18438: ----------------------------------------------- [~maxwellguo], you still have a possibility to create your own snitch, put it into a JAR file and place that JAR on the classpath so Cassandra will find it and you can reference it in cassandra.yaml file. Nothing prevents you from implementing your own snitch right now if you have something custom which is not there yet. It is just comfortable to have it shipped in Cassandra so you do not need to take care of your custom JAR but that is just that ... comfortable. Not necessary. > Refactor the code for public cloud platform snitch to be configurable > --------------------------------------------------------------------- > > Key: CASSANDRA-18438 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18438 > Project: Cassandra > Issue Type: Improvement > Components: Local/Other > Reporter: Maxwell Guo > Assignee: Maxwell Guo > Priority: Normal > Fix For: 5.x > > > Nowadays we have got about four public cloud platform snitchs : EC2 snitch > for aws, google cloud snitch for google cloud, alibaba cloud snitch for > alibaba cloud and multi region snitch for ec2. And the common place for the > first three is that we just need to query the zone center to get the ec2 / > ecs id , so I think we can refactor the code , and if some new public cloud > platform want to add one more snitch for himself, there is no need to pull a > pr for him and configure some options in yaml is enough . > Besides it would be even better that we may reuse the multic region snitch > for ec2 for other public cloud platform. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org