Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some issues for cassandra protocol #69

Open
kination opened this issue Sep 18, 2018 · 3 comments
Open

Some issues for cassandra protocol #69

kination opened this issue Sep 18, 2018 · 3 comments

Comments

@kination
Copy link
Contributor

Hello.
I'm trying to update protocol to support Cassandra DB. While working on, I have question for this.

from cassandra.cluster import Cluster

cluster = Cluster(['127.0.0.1'])
session = cluster.connect('testks')

Cassandra requires List of IPs of cluster which compose database, and currently Duct receives string value for host. Which will be the good way to adapt this?

Thanks.

@naoyak
Copy link
Collaborator

naoyak commented Sep 19, 2018

@djKooks it still seems an open question (#63 (comment) #59 #19) how we would implement support for NoSQL DBs - if you want to come up with an implementation it would be great, as it would help us think through whether to standardize the API across different NoSQL backends.

@matthewwardrop
Copy link
Collaborator

@djKooks Actually, omniduct does support a list of host names, but what happens at runtime is that one host of these is randomly selected for use, based upon availability. I'll look into this a bit more for you, and add a new class of Ducts for NoSQL databases.

@kination
Copy link
Contributor Author

@matthewwardrop @naoyak thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants