cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3507) Proposal: separate cqlsh from CQL drivers
Date Wed, 04 Jan 2012 16:50:40 GMT

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

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

bq. But that regression already occurred, in 1.0.6

I don't think that's the case actually. I checked and the control file for 1.0.6 did not mention
cql (nor python for that matter). Which is consistent with the 'fix version' of CASSANDRA-3458
and the fact that nobody bitched about not being able to upgrade.

I've went ahead and reverted CASSANDRA-3458 (we can still recommit if everyone think I'm wrong,
but at least the branch is in a releasable state in the meantime)

bq. I haven't seen any doubt expressed since my last proposal

To be clear, I did not criticize your last proposal. I just wanted to point out that committing
CASSANDRA-3458 without committing this one at roughly the same time was imo a mistake. But
anyway, doesn't matter.

On the issue itself, I'll note that voting on the python driver and including it in the official
deb repository does create some dependency on the driver. 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.
I am still not totally at ease with that. We obviously have to make a decision at some point
on whether we want to accept that to have cqlsh in tree, but reading the comments above I
don't see that a huge consensus on that really emerge (that may must be me misreading what's
above, in why case mea culpa).
                
> 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

        

Mime
View raw message