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

Gary Dusbabek commented on CASSANDRA-2124:
------------------------------------------

I took at look at Cassandra_2124_decoder.patch this morning.  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, and that relying on a regex to figure out the keyspace is brittle.  It 
would be better to make the describe_keyspace() call once in 
CassandraConnection constructor.

Other things: ColumnDecoder.describe_key_Space() needs to conform to the 
project coding conventions.  There seem to be copious amounts of 
whitespace/comment/javadoc changes.  If you're going to include them, put them 
all in a separate patch at the end.

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

        

Reply via email to