[
https://issues.apache.org/jira/browse/CASSANDRA-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13180063#comment-13180063
]
Eric Evans commented on CASSANDRA-3507:
---------------------------------------
bq. To sum up, my personal ideal solution would be to take cqlsh out of tree,
along with cassandra-cli (and, actually, all the other bundled dependencies)
and use package relationships to manage all that complexity (and just give
tarball users a nice long installation readme).
+1
We could probably do better than a "nice long installation readme" though.
Once, for a brief time, we were free of embedded dependencies. Tarball users
would fetch them with Ivy (that was before we were all mavened up). Something
like that could be done again for people who want to go about things the Hard
Way.
bq. But if we want something built in to the main official C* tarball to allow
talking to C* once it's running, I think we have to include cqlsh — based on
the premise that the project wants cql to be the preferred mode of interface.
If we include cassandra-cli but not cqlsh, cql will remain second-class. If we
don't care about that, then yay, definitely we should leave cqlsh out.
I feel like I missed something important. The description called for bundling
a private copy of the driver. This seems to be identical to how we currently
handle all of our other external dependencies. Is that off the table now?
> 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
