[
https://issues.apache.org/jira/browse/CASSANDRA-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003396#comment-13003396
]
Gary Dusbabek commented on CASSANDRA-2124:
------------------------------------------
bq. I get failures of `o.a.c.db.SerializationsTest`.
Careless modifications to `test/conf/cassandra.yaml` did that. Fixed in v2.
bq. Would it make sense to wrap the Thrift results from
o.a.c.cql.driver.Connection in something that returned decoded results?
That's what happens in `CassandraStatement.execute()` when it returns a
`CassandraResultSet` (the magic is in `CassandraResultSet.next()`.)
bq. I guess you'd also need to wrap the Thrift exceptions thrown by
`o.a.c.cql.driver.Connection.execute()`
That is what is being done.
> JDBC driver for CQL
> -------------------
>
> Key: CASSANDRA-2124
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2124
> Project: Cassandra
> Issue Type: New Feature
> Components: API
> Reporter: Eric Evans
> Assignee: Vivek Mishra
> Priority: Minor
> Labels: cql
> Attachments: Cassandra-2124_v1.0, Cassandra_2124_decoder.patch,
> cassandra-0.7.1-2124_v2.0, cassandra-0.7.1-2124_v2.1,
> cassandra_generic_decoder.patch, cassandra_generic_decoder_v1.1.patch,
> v2-0001-first-pass-at-column-decoding.txt,
> v2-0002-clean-up-JdbcDriverTest.txt,
> v2-0003-implements-getXXX-methods-to-return-values-of-the-corr.txt,
> v2-0004-more-comments-in-ColumnDecoder.txt
>
>
> A simple connection class and corresponding pool was created for CQL as a
> part of CASSANDRA-1710, but a JDBC driver (either in addition to, or as a
> replacement for) would also be interesting.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
