cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vivek Mishra (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-2124) JDBC driver for CQL
Date Thu, 03 Mar 2011 09:36:36 GMT


Vivek Mishra commented on CASSANDRA-2124:

Hi Gary,
Should we hold a decoder instance with Connection  or it should be a static call? 
Passing Decoder instance to CassandraResultSet is required, why?

Planning for ResultSetMetadata API? CassandraResultSet does not need column name decoding(only
value decoding), i think.

> JDBC driver for CQL
> -------------------
>                 Key: CASSANDRA-2124
>                 URL:
>             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,
> 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:


View raw message