Re: [VOTE] Accept java-driver

[Michael Shuler]

+1

(late to the vote, but wanted to publicly note my support)

Kind regards,
Michael

On 10/2/23 23:52, Mick Semb Wever wrote:

The donation of the java-driver is ready for its IP Clearance vote.
https://incubator.apache.org/ip-clearance/cassandra-java-driver.html 



The SGA has been sent to the ASF.  This does not require acknowledgement 
before the vote.


Once the vote passes, and the SGA has been filed by the ASF Secretary, 
we will request ASF Infra to move the datastax/java-driver as-is to 
apache/java-driver


This means all branches and tags, with all their history, will be kept.  
A cleaning effort has already cleaned up anything deemed not needed.


Background for the donation is found in CEP-8: 
https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-8%3A+DataStax+Drivers+Donation 


PMC members, please take note of (and check) the IP Clearance 
requirements when voting.


The vote will be open for 72 hours (or longer). Votes by PMC members are 
considered binding. A vote passes if there are at least three binding 
+1s and no -1's.


regards,
Mick

java driver with cassandra proxies (option: -Dcassandra.join_ring=false)

[Regis Le Bretonnic]

Hi,

We use datastax cassandra java driver v4.15.0 and we want to limit
connexion only to Cassandra proxy nodes (Nodes with no data started
with option: -Dcassandra.join_ring=false).
For that:
 - we configured the driver to have only proxy hosts in the
contact-points (datastax-java-driver.basic.contact-points).
 - we added a custom configuration containing "whitelisted host" (same
list as contact-points)
 - we implemented a custom NodeFilter Class to limit allowed nodes to
whitelisted one

If we look at opened TCP connexions between client and Cassandra
cluster we see only 2:
 - one to one of the proxy listed in the contact-points (coordinator connexion)
 - another one the the same proxy (query connexion)

We expected to have an opened connexion to each proxy listed in
contact-points / whitelisted hosts.
We found that it is not the case because during cluster discovery the
driver execute a query in table "system.peers" or "system.peers_v2"
(made in DefaultTopologyMonitor class) and proxy nodes are not in this
table.

Is it possible to add these nodes in table "peers" ?
Is there a way to implement a custom version of TopologyMonitor
interface to bypass this mechanism ?
Is there another way to do this ?

Thanks in advance
Regards