[
https://issues.apache.org/jira/browse/CASSANDRA-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Dusbabek updated CASSANDRA-1710:
-------------------------------------
Attachment: jdbc-ish.diff
This may not be useful or productive, but I had to put the code somewhere.
This patch (applies on top) and makes the API JDBC-ish, which may be
undesirable). However, it does push the pool abstraction down so that client
code would think about pools and could treat all Connection objects the same
way: get connection, execute query, close.
I haven't given too much thought as to how this would work out in other
languages, but it is idiomatic for java. :)
> Java driver for CQL
> -------------------
>
> Key: CASSANDRA-1710
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1710
> Project: Cassandra
> Issue Type: Sub-task
> Components: API
> Affects Versions: 0.8
> Reporter: Eric Evans
> Priority: Minor
> Fix For: 0.8
>
> Attachments: jdbc-ish.diff,
> v3-0001-CASSANDRA-1710-basic-connection-pooling-for-java-drive.txt,
> v3-0002-compile-driver-source.txt
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> In-tree CQL drivers should be reasonably consistent with one another
> (wherever possible/practical), and implement a minimum of:
> * Query compression
> * Keyspace assignment on connection
> * Connection pooling / load-balancing
> The goal is not to supplant the idiomatic libraries, but to provide a
> consistent, stable base for them to build upon.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
