[
https://issues.apache.org/jira/browse/CASSANDRA-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031817#comment-13031817
]
Tony Bringardner commented on CASSANDRA-2124:
---------------------------------------------
I did not see this issue earlier (my bad) and I have been working on a JDBC
driver using Cassandra 0.7.4. It originally used Hector to access Cassandra
but now uses Cassandra.client.
It’s not complete by any means but it is fairly functional. It has support for
an expanded set of types using a column family to store type info. It also
supports Metadata (Database and ResultSet) .
My objective was to introduce Cassandra into our datacenter but have developers
write code using standard Spring JDBC template.
Is there any interest?
> 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
> Fix For: 0.8 beta 1
>
> 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,
> v3-0001-first-pass-at-column-decoding.txt,
> v3-0002-clean-up-JdbcDriverTest.txt,
> v3-0003-implements-getXXX-methods-to-return-values-of-the-corr.txt,
> v3-0004-more-comments-in-ColumnDecoder.txt,
> v3-0005-move-all-java-cql-into-jdbc-package-and-only-expose-.patch
>
>
> 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
