[
https://issues.apache.org/jira/browse/CASSANDRA-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13179001#comment-13179001
]
Sylvain Lebresne commented on CASSANDRA-3507:
---------------------------------------------
bq. That's a little harsh- the debian package and the packaging aren't
technically broken, they just require users to add a 3rd-party apt source or
install a python-cql deb locally. But yeah, I doubt users really appreciate
that distinction much.
I stand corrected. But in a minor release, anything that require more than
'apt-get update' from the user is a regression from his point of view.
bq. Do you mean we don't have strong consensus on including cqlsh in the
official C* debs?
I don't know. I mean that there has been a number of comments on that issue,
and some doubt on what we can and cannot do (it would be counter-productive to
start doing this some way to change it in two release, so we'd better make sure
we're covered on that -- though I'm not saying you're reading of apache rules
was non exhaustive in any way) and that right now this is holding the release
of 1.0.7. It's kind of annoying given that I don't feel that cqlsh is something
current user of 1.0 are really waiting on (and they can get it if they want
anyway) -- without making any judgement on the quality of cqlsh btw.
> 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
