[
https://issues.apache.org/jira/browse/CASSANDRA-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993253#comment-12993253
]
Eric Evans commented on CASSANDRA-2124:
---------------------------------------
Obviously there is a lot more that can be done here, but this is a great start,
so I went ahead and committed your latest. Thanks for the contribution!
{quote}
>> Additionally, it looks like CassandraResultSet creates String instances for
>> column names and values,
>> which is really going to limit the utility. Do you have plans to change that?
>>
> Changes made. Thought to add generics with in place of Object, but seems
> overhead.
{quote}
Using Object for {{valueMap}} here isn't going to change much since {{next()}}
still marshals the returned values to String.
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.
> 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
