[
https://issues.apache.org/jira/browse/CASSANDRA-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977793#action_12977793
]
Gary Dusbabek commented on CASSANDRA-1710:
------------------------------------------
Changes look good.
One more thing I realized: careless uses could close() a Connection before
returning it to the pool, which if not full, would add a closed connection.
Depending on how much you want to guard the API you could check connection
status before returning it to the queue or emit derived Connections that have
their close() methods overwritten to be no-ops (or log a WARN), so that only
the pool could call the real close().
> 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
> Assignee: Eric Evans
> Priority: Minor
> Fix For: 0.8
>
> Attachments:
> v1-0001-CASSANDRA-1710-basic-connection-pooling-for-java-drive.txt,
> v1-0002-compile-driver-source.txt,
> v2-0001-CASSANDRA-1710-basic-connection-pooling-for-java-drive.txt,
> v2-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.
