Skip to content
This repository has been archived by the owner on Apr 4, 2023. It is now read-only.

composeaddresstranslator no longer works with recent versions of gocql #3

Open
homme opened this issue Dec 6, 2017 · 2 comments
Open

Comments

@homme
Copy link

homme commented Dec 6, 2017

We're using this package to connect to our Compose.io instances but have noticed that it doesn't work with more recent versions of gocql. The gocql commit that introduces the problem is 01f586cc26f23b994055dcca2052ce26f87e27c8.

By doesn't work I mean that the very latest gocql versions don't even connect, returning the error: no connections were made when creating the session. Earlier versions do connect and seem to run ok, except that they hang on session.Close waiting for a mutex to unlock.

@nkev
Copy link

nkev commented Aug 24, 2018

I just created a trial compose account to evaluate their hosted ScyllaDB and I too cannot connect. I'm getting unable to create session: unable to discover protocol version. Does anyone know how to get past this?

@nkev
Copy link

nkev commented Aug 24, 2018

We can connect to Compose ScyllaDB with DBeaver Enterprise without issue. It's Gocql that has yet to for us.

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

No branches or pull requests

2 participants