Thibault Charbonnier

@drolando Interesting, thanks for the PR! I have given it a look and will have some comments, but will need a couple days to post them. Are you already using...

@drolando Sorry for the delay! I really need some time on my hands to be able to look at this, I hope to get there soon since I finally got...

Hi @drolando, Here are the concerns that have been on my mind but that I haven't had time to put in writing until now. As far as I can tell,...

@drolando Hi; any thoughts on the above?

@drolando No worries. > True, but that's not important. Each worker has its own connection pool, so they can use the same id if they want. Indeed they do have...

We use [rpc_address](https://docs.datastax.com/en/cassandra/3.0/cassandra/configuration/configCassandra_yaml.html#configCassandra_yaml__rpc_address) which is for client connections. In comparison, [broadcast_address](https://docs.datastax.com/en/cassandra/3.0/cassandra/configuration/configCassandra_yaml.html#configCassandra_yaml__broadcast_address) is used for inter-nodes communication. This driver aims at a similar behavior as other Datastax-maintained drivers, which use `rpc_address`...

@nmeylan What is the value configured for [rpc_address](https://docs.datastax.com/en/cassandra/3.0/cassandra/configuration/configCassandra_yaml.html#configCassandra_yaml__rpc_address) in your cluster's nodes?

> The JS driver doesn't follow this behavior. How so? The JS driver uses `rpc_address` unless it is specified as the bind all address (`0.0.0.0`), in which case it will...

@viossat So, if I understand you correctly, your complaint is that the Lua driver overrides the specified `contact_point` argument with said contact point's `rpc_address`, instead of sticking to the given...

Reopening this since the discussion is active.