Closed leandromoreira closed 7 years ago
Hi,
Glad to hear! The API for the single module is pretty much the same, but the usage of the clustering module differs a bit more, especially with the necessity to store the cluster instance as a local upvalue. Everything is documented online:
https://thibaultcha.github.io/lua-cassandra/
Depending on your cluster, you might want to look at the different load balancing policies and the desired level of consistency too.
Thank you @thibaultcha, I'll be posting here any issues or advice for anyone in the same situation.
FYI, these days work is being done on the refactor/perf+style
branch and will likely result in a more friendly cluster interface (I'd like to avoid the need for users to cache the instance themselves in an upvalue). But this is not before a while.
Let's now close this, if you have further questions, feel free to open another issue.
We postpone but we'll do it this quarter! I'll keep this up to date, thanks.
Hi @thibaultcha, just a sanity check related to this migration, there isn't setkeepalive function for cluster module, can I assume that the coordinator does that by default?
@rafatio Yes indeed!
@thibaultcha nice :)
Testing the cluster driver we are having some could not refresh cluster: no host details for
and no host details for
. Is those errors usual or there is something wrong?
Since the cassandra driver is not in active development we're planning to move on to this 🥇 awesome project.
I would like to know how different the API is from
cassandra
? socket options and client