[
https://issues.apache.org/jira/browse/CASSANDRA-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13179713#comment-13179713
]
Sylvain Lebresne commented on CASSANDRA-3507:
---------------------------------------------
bq. If we don't mind releasing a C* version for which the existing drivers
don't work right, then it probably doesn't matter whether the drivers are
available from the cassandra deb repo or not.
It matters because if the driver don't work, cqlsh don't work and thus we would
be shipping a release with a regression. If Cassandra don't ship with cqlsh, we
don't have this problem. Let's be clear that the choice is between having cqlsh
in-tree or not having it, because that's what imply the dependency on the
driver. Again, the initial goal was to have C* not depend on any of the driver,
based on the idea that drivers may be maintained by other people than us having
different schedule than us. Having cqlsh in-tree does create a dependency on
the python driver. And while we obviously will want to work with driver
maintainers to be sure that when we release incompatible changes, there is
preferably at least a few driver supporting it, it's is not the same to say
that we will have to wait on the *python* driver before being *able to* release.
Again, I'm just saying that the dependency on the python driver will exist if
cqlsh is in tree. Do we think having cqlsh in-tree is worth it? Maybe, but I've
seen at least Jonathan and Eric state above that they wouldn't necessarily mind
having cqlsh separate, and I've missed the part where they said "ok, I'm
convinced, it's worth having cqlsh in-tree". I guess I just want to be sure we
have consensus on the choice we make (I'm personally not sure where I stand on
this). Maybe I've just missed the part where we did all clearly agree, in which
case I apologize for having missing it.
> 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
