You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "M Chen (JIRA)" <ji...@apache.org> on 2011/09/22 05:33:26 UTC

[jira] [Created] (CASSANDRA-3240) CQL JDBC can only specify one host, thus doesn't support failover

CQL JDBC can only specify one host, thus doesn't support failover
-----------------------------------------------------------------

                 Key: CASSANDRA-3240
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3240
             Project: Cassandra
          Issue Type: Bug
          Components: API
    Affects Versions: 0.8.6
            Reporter: M Chen


The CQL JDBC driver takes a connection string of the form

jdbc:cassandra:user/pass@thrifthost:thriftport

but 

1. only one value for thrifthost is supported, 
2. CQL JDBC does not appear to allow access to the ring members 
(e.g. so that as long as the specified host was alive long enough to get the ring, 
from then on some other logic can try different host:port values if needed). 




--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (CASSANDRA-3240) CQL JDBC can only specify one host, thus doesn't support failover

Posted by "M Chen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112321#comment-13112321 ] 

M Chen commented on CASSANDRA-3240:
-----------------------------------

an old article on Hector where they provide multiple thrift host:port values
http://prettyprint.me/2010/03/03/load-balancing-and-improved-failover-in-hector/

Pelops appears to do something similar.

I've seen a few connection pool items, although pool wrappers for JDBC already exist
(if CQL JDBC is compliant enough for them)
but none that help with failover

> CQL JDBC can only specify one host, thus doesn't support failover
> -----------------------------------------------------------------
>
>                 Key: CASSANDRA-3240
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3240
>             Project: Cassandra
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 0.8.6
>            Reporter: M Chen
>
> The CQL JDBC driver takes a connection string of the form
> jdbc:cassandra:user/pass@thrifthost:thriftport
> but 
> 1. only one value for thrifthost is supported, 
> 2. CQL JDBC does not appear to allow access to the ring members 
> (e.g. so that as long as the specified host was alive long enough to get the ring, 
> from then on some other logic can try different host:port values if needed). 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (CASSANDRA-3240) CQL JDBC can only specify one host, thus doesn't support failover

Posted by "Rick Shaw (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112758#comment-13112758 ] 

Rick Shaw commented on CASSANDRA-3240:
--------------------------------------

+1. Good addition to the "nice to have" list for next release. (after release coinsiding with 1.0.0 of server)

> CQL JDBC can only specify one host, thus doesn't support failover
> -----------------------------------------------------------------
>
>                 Key: CASSANDRA-3240
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3240
>             Project: Cassandra
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 0.8.6
>            Reporter: M Chen
>
> The CQL JDBC driver takes a connection string of the form
> jdbc:cassandra:user/pass@thrifthost:thriftport
> but 
> 1. only one value for thrifthost is supported, 
> 2. CQL JDBC does not appear to allow access to the ring members 
> (e.g. so that as long as the specified host was alive long enough to get the ring, 
> from then on some other logic can try different host:port values if needed). 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira