cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "paul cannon (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3507) Proposal: separate cqlsh from CQL drivers
Date Mon, 21 Nov 2011 19:30:52 GMT

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

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

bq. Should we just spin cqlsh out to a separate project?

I expect that if cqlsh is in a different project, but cassandra-cli is distributed with c*
proper, cassandra-cli will remain the de facto standard interactive interface, even if cqlsh
is quite simple to install alongside. I've heard from several people that we want to transition
to cqlsh over time, so that would make this an important issue.

But if we don't mind sticking with cassandra-cli (I don't really know), then it makes sense
to split cqlsh into a different project.
                
> 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: Minor
>              Labels: cql, cqlsh
>             Fix For: 1.0.4
>
>
> 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

        

Mime
View raw message