[
https://issues.apache.org/jira/browse/CASSANDRA-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175278#comment-13175278
]
paul cannon commented on CASSANDRA-3507:
----------------------------------------
Is it possible for the ASF contributors to vote on code that isn't in the
official tree, like, say, a particular tag of the python CQL driver at Apache
Extras? If we can distribute the drivers in the same official repository, most
of these problems go away.
----
If not, here are the alternatives as I see them:
1. Bundle python-cql with cqlsh deb, rpm, and tarball (whether cqlsh is in the
same artifact with C* or not). This makes, by far, the most sense to me, since
it's the same approach taken for nearly everything else in C*. I don't buy the
"everyone expects Java stuff to be bundled, and not Python stuff" argument,
because no one should be expecting any bundling, java or not, in actual OS
packages. Also, the user shouldn't need to care what languages our tools are
written in, so per-language expectations around bundling and packaging need not
apply.
2. Add steps to the install instructions, or modify the instructions, so that
users get C*/cqlsh/python-cql packages from a third party repo (like
Datastax's).
3. Allow normal install of C* packages without any bundled python-cql, but have
the cqlsh executable give instructions on how to download python-cql with the
least amount of fuss for the local platform, when it is run.
4. Allow normal install of C* packages without any bundled python-cql, and have
the cqlsh executable perform installation of python-cql automatically (giving
the user a chance to cancel first). It could use a dot-directory under $HOME,
and could be as simple as {{wget \-O -
"http://pypi.python.org/packages/source/c/cql/cql-$CQL_VERSION.tar.gz"; | tar
xz}} , so it wouldn't need administrator privileges.
5. (Don't even want to bring this up, but) Put python-cql back in the C* tree,
so it can be voted on by the ASF people and put up in the same official C*
repositories (and bundled, in the tarball case).
6. Get python-cql into the official OS repositories for all supported platforms
(hint: probably not possible within the next, say, 3 years).
> 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: Minor
> Labels: cql, cqlsh
> Fix For: 1.1
>
>
> 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
