cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Wunderlich (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2263) cql driver jar
Date Sun, 29 May 2011 18:57:47 GMT


Lars Wunderlich commented on CASSANDRA-2263:

Connection problem could be solved by passing parameter -Dcassandra.config=cassandra.yaml
when starting test case and adding cassandra.yaml file as copy to classpath. However, cql
driver couldn't be started out of the box and I haven't found documentation including code
examples how to successfully setup a working JDBC connection as of now.  

> cql driver jar
> --------------
>                 Key: CASSANDRA-2263
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 0.8 beta 1
>            Reporter: Eric Evans
>            Priority: Minor
>              Labels: cql
>             Fix For: 1.0
>   Original Estimate: 0h
>  Remaining Estimate: 0h
> Work was done in CASSANDRA-1848  to create a jar for the CQL Java driver.  The generated
Thrfit code was broken out into it's own jar as well, since that is a dependency for both
servers and clients. However, based on the work currently happening in CASSANDRA-2262 and
CASSANDRA-2124, it seems that additional dependencies will exist, and new jar(s) will need
to be created.
> The easiest way to fix this will probably be to put copies of all of {{o.a.c.db.marshal}}
and {{o.a.c.utils}}, and a copy of {{o.a.c.config.ConfigurationException}} into the CQL driver
jar (a split along those lines to create another jar doesn't make sense IMO).

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message