[
https://issues.apache.org/jira/browse/CASSANDRA-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13179647#comment-13179647
]
paul cannon commented on CASSANDRA-3507:
----------------------------------------
bq. I don't think that's the case actually.
Oh, you're right. My mistake, sorry.
bq. Namely, if we do a change in cassandra that require a driver change
(granted we don't want to do that too often but that has happen and will
undoubtedly happen again), we have to wait on the driver to catch up to release.
This doesn't seem to follow to me. 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. And if we
want to be sure the drivers are up-to-date for new C* features before we
release a C* version, then we probably want that whether the drivers are
available from the cassandra deb repo or not.
> 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
