[
https://issues.apache.org/jira/browse/CASSANDRA-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997544#comment-12997544
]
Eric Evans commented on CASSANDRA-2124:
---------------------------------------
I didn't spend a great deal of time looking at this since you've indicated that
it's a work in-progress, but one thing worth mentioning is that I think the
decoder should exist as a part of the vanilla driver, where it can be used by
the JDBC one (much the way {{o.a.c.cql.driver.Connection}} is).
Also, I'm not sure what your comfort level is with reading Python, but I
committed a result decoder to the Python driver recently. I'm not married to
anything that was done there (in fact, I feel certain it could use some
improvement), but I mention it because it would be nice to sync the two up as
much as possible.
> 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-0.7.1-2124_v2.0,
> cassandra-0.7.1-2124_v2.1, cassandra_generic_decoder.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
