cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1848) Separate thrift and avro classes from cassandra's jar
Date Mon, 13 Dec 2010 19:27:02 GMT

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

Eric Evans commented on CASSANDRA-1848:
---------------------------------------

{quote}
cassandra-all-___.jar (the current jar)
cassandra-thrift-___.jar (the thrift client)
cassandra-avro-___.jar (the avro client)
cassandra-hadoop-___.jar (the hadoop support classes)
cassandra-server-jar (the remainder of cassandra-all after removing the above three)
{quote}

Why the -all jar?  That seems redundant to me.

bq. Could we get that in the 0.7.0 time frame (so I can get the maven publishing of at least
the thrift and avro client jars in the 0.7.0 timeframe)

No, we're too close to the release to be making changes with the potential for disruption
this has.

{quote}
I am less concerned with the thrift & avro jars containing more than they should, as the
key here is to trim the dependencies down to those that are available in central... as cassandra
is modifying avro, and avro is an apache project, it is no big deal to publish the cassandra
avro special build under the org.apache.cassandra gId, the same goes for libthrift.
{quote}

I think it's worth the (minor) effort to get those packages pared down to just client code.
 And, fwiw there are classes in there with dependencies outside Thrift/Avro.

> 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
>            Priority: Trivial
>         Attachments: CASSANDRA-1848.patch, CASSANDRA-1848_with_hadoop.patch
>
>
> 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.


Mime
View raw message