cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vivek Mishra (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-2124) JDBC driver for CQL
Date Fri, 11 Feb 2011 01:56:02 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993297#comment-12993297
] 

Vivek Mishra commented on CASSANDRA-2124:
-----------------------------------------

Thanks Eric.

it is just to startwith. need to put in a lot of things.

What I had planned to do for the generic driver (o.a.c.cql.driver.Connection), was to introduce
the notion of a pluggable result decoder. The default decoder would introspect the schema
(comparators and/or validators) to configure itself for the right types. I'm not sure how
something like that could be applied to a JDBC driver though.

I think what we are talking here is something like resultSetMetadata/metadata for decode.
Yes that is next on list. 

Suggest if creating subtask for these would be a good idea, as there is lot of things needs
to be put in going ahead.

> 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
>
>
> 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

        

Mime
View raw message