Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 5 Apr 2016 20:28:25 +0000 (UTC)
From: "Brandon Williams (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12956274.1459887553000.142656.1459888105440@Atlassian.JIRA>
In-Reply-To: <JIRA.12956274.1459887553000@Atlassian.JIRA>
References: <JIRA.12956274.1459887553000@Atlassian.JIRA>
 <JIRA.12956274.1459887553161@arcas>
Subject: [jira] [Commented] (CASSANDRA-11509) Consider deprecating the
 property file snitch
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-11509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15227080#comment-15227080 ] 

Brandon Williams commented on CASSANDRA-11509:
----------------------------------------------

The nice thing about this is even with PFS removed, GPFS can remain true to its name.

> Consider deprecating the property file snitch
> ---------------------------------------------
>
>                 Key: CASSANDRA-11509
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11509
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Brandon Williams
>
> It is at least clear to me that GPFS is one of the most dominate snitches in installations I see, with there being no good reason to continue using PFS any longer.  Since GPFS has a direct migration path from PFS, we can deprecate it in a major release and remove it (and the backward compatibility cruft in GPFS) in a later one.  This will prevent the sort of problem that caused me to file CASSANDRA-11508.
> We could also just remove the migration path, if someone really, really wants to use PFS for the rest of time.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)