[jira] [Commented] (CASSANDRA-3507) Proposal: separate cqlsh from CQL drivers

["Sylvain Lebresne (Commented) (JIRA)" <ji...@apache.org>]

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

Sylvain Lebresne commented on CASSANDRA-3507:
---------------------------------------------

So, apparently this is now a blocker because Paul told me that the debian package is broken following the commit of CASSANDRA-3458.

I see two possibility:
# we revert CASSANDRA-3458 so that we can do a release.
# we fix this.

My preference goes to reverting CASSANDRA-3458, because I don't really like that we add something we're only mildly getting consensus on to a 1.0 release.

As a side note, I would have wished  we didn't end up in that state of not being able to release because of some debian problem. Please be as careful with change to the debian packaging in stable release as you are with the rest of the code since it's part of the tree.
                
> 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