Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 5 Jan 2012 17:28:41 +0000 (UTC)
From: "paul cannon (Commented) (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <1453216624.10224.1325784521243.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <481742360.44766.1321646331619.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CASSANDRA-3507) Proposal: separate cqlsh from
 CQL drivers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

paul cannon commented on CASSANDRA-3507:
----------------------------------------

Here is what might be a helpful thought experiment: _how would this have been solved, if cqlsh had been written in Java, using cassandra-jdbc?_ My estimation was, based on the past, that a cassandra-jdbc jar would probably just be bundled in with C* along with all the others. If that's true, the arguments against bundling cassandra-dbapi2 are not very convincing.
                
> Proposal: separate cqlsh from CQL drivers
> -----------------------------------------
>
>                 Key: CASSANDRA-3507
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3507
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Packaging, Tools
>    Affects Versions: 1.0.3
>         Environment: Debian-based systems
>            Reporter: paul cannon
>            Assignee: paul cannon
>            Priority: Blocker
>              Labels: cql, cqlsh
>             Fix For: 1.0.7
>
>
> Whereas:
> * It has been shown to be very desirable to decouple the release cycles of Cassandra from the various client CQL drivers, and
> * It is also desirable to include a good interactive CQL client with releases of Cassandra, and
> * It is not desirable for Cassandra releases to depend on 3rd-party software which is neither bundled with Cassandra nor readily available for every target platform, but
> * Any good interactive CQL client will require a CQL driver;
> Therefore, be it resolved that:
> * cqlsh will not use an official or supported CQL driver, but will include its own private CQL driver, not intended for use by anything else, and
> * the Cassandra project will still recommend installing and using a proper CQL driver for client software.
> To ease maintenance, the private CQL driver included with cqlsh may very well be created by "copying the python CQL driver from one directory into another", but the user shouldn't rely on this. Maybe we even ought to take some minor steps to discourage its use for other purposes.
> Thoughts?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira