[
https://issues.apache.org/jira/browse/CASSANDRA-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Mishra updated CASSANDRA-2124:
------------------------------------
Attachment: cassandra_generic_decoder_v1.1.patch
@Gary:
<I think that calling describe_keyspace() for every statement is going to
impact performance very negatively. At the very least, there should be some
caching going on there.>
i am moving it to CassandraConnection. Do we still need to put caching there?
Introducing connection pooling should take care of this. Getting a new
connection instance should make call to "describe_key_space".
< relying on a regex to figure out the keyspace is brittle>
This is for extracting column family from cql query.
> 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_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
>
>
> 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
