[
https://issues.apache.org/jira/browse/CASSANDRA-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978829#action_12978829
]
Eric Evans commented on CASSANDRA-1848:
---------------------------------------
bq. cassandra-thrift -> libthrift
Yes.
bq. cassandra-cql -> (none)?
cassandra-thrift (for now).
bq. cassandra-jmx -> (none)?
Yes.
bq. cassandra-hadoop -> hadoop jars and perhaps cassandra-thrift / cassandra-cql
Not sure.
{quote}
cassandra-tools-core -> cassandra-jmx, etc
cassandra-tools-cli -> cassandra-tools-core [make this an executable jar]
cassandra-tools-nodetool -> cassandra-tools-core [make this an executable jar]
cassandra-tools-clustertool -> cassandra-tools-core [make this an executable
jar]
{quote}
This seems a little gratuitous to me, at most I could see separating the CLI,
but for the others, not only is it going to be awkward to do, it seems like a
waste of effort.
bq. cassandra-server instead of cassandra-main [make this an executable jar]
I was calling it main simply because it's the catch-all and there's bound to be
stuff bundled in that doesn't quite fit with "server", but which doesn't
warrant turning into it's own jar. I also doubt that anyone is going to use
this jar outside of our binary artifacts w/ start scripts, etc.
That said, I don't care *that* much about the name (of others think -server is
better), and it certainly won't hurt anything to make it executable.
ObBikeShed: Red
> Separate thrift and avro classes from cassandra's jar
> -----------------------------------------------------
>
> Key: CASSANDRA-1848
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1848
> Project: Cassandra
> Issue Type: Improvement
> Components: Packaging
> Affects Versions: 0.7.0 rc 2
> Reporter: Tristan Tarrant
> Assignee: Eric Evans
> Priority: Trivial
> Fix For: 0.8
>
> Attachments: CASSANDRA-1848.patch, CASSANDRA-1848_with_hadoop.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> Most client applications written in Java include the full
> apache-cassandra-x.y.z.jar in their classpath. I propose to separate the avro
> and thrift classes into separate jars.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
