Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Sat, 13 Sep 2014 00:32:34 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12741213.1410568323000.24784.1410568354235@Atlassian.JIRA>
In-Reply-To: <JIRA.12741213.1410568323000@Atlassian.JIRA>
References: <JIRA.12741213.1410568323000@Atlassian.JIRA>
 <JIRA.12741213.1410568323464@arcas>
Subject: [jira] [Created] (CASSANDRA-7920) Remove cassandra-cli in Cassandra
 3.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Aleksey Yeschenko created CASSANDRA-7920:
--------------------------------------------

             Summary: Remove cassandra-cli in Cassandra 3.0
                 Key: CASSANDRA-7920
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7920
             Project: Cassandra
          Issue Type: Improvement
            Reporter: Aleksey Yeschenko
            Assignee: Aleksey Yeschenko
             Fix For: 3.0


At this point, cassandra-cli has been deprecated for longer than a year (since 1.2) with a warning that it would be removed in 3.0.

There are several tricky bugs and unsupported table options in it, so it's out of date as well.

Even before that, we've been urging people to use cqlsh for a while.

There are several tickets in 3.0 that would require modifying (deprecated) cli - e.g. #6717 - so to not do that redundant work, I suggest we kill it early.


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