[
https://issues.apache.org/jira/browse/CASSANDRA-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002896#comment-13002896
]
Eric Evans commented on CASSANDRA-2124:
---------------------------------------
It is very strange, but with these patches applied I get failures of
{{o.a.c.db.SerializationsTest}}. Is anyone else seeing that?
Would it make sense to wrap the Thrift results from
{{o.a.c.cql.driver.Connection}} in something that returned decoded results?
This is how the Python driver works FWIW.
You wouldn't need to expose the current keyspace, column family, or decoder,
and hiding the Thrift instances behind a Rows proxy like that would make it
easier later on to replace Thrift with our own protocol.
On that note, I guess you'd also need to wrap the Thrift exceptions thrown by
{{o.a.c.cql.driver.Connection.execute}} (the Python driver does that too).
> 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,
> v1-0001-first-pass-at-column-decoding.txt,
> v1-0002-clean-up-JdbcDriverTest.txt,
> v1-0003-implements-getXXX-methods-to-return-values-of-the-corr.txt,
> v1-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
