DataStax DevCenter compatibility

[darren.landoll@gmail.com]

Has anyone tried using DevCenter to execute queries, etc. against a scylla cluster? I am able to connect and view keyspaces/tables. When I try to run queries (insert, select) DevCenter says the script failed to execute... but I can capture the network traffic with Wireshark and see that the scylla server returns a response containing the data I'd expect to see. Maybe there is a field set incorrectly in the response or DevCenter is expecting something non-standard back?

[Glauber Costa]

We have seen similar problems in the past with cqlsh, that expected
specific version strings.
But you're the first - to the best of my knowledge - to be testing
DevCenter. At least in terms of reporting to the mailing list.

If this is something easy for you to do, would you mind sending us the
connection data for Scylla, and a similar trace for Cassandra?


> --
> You received this message because you are subscribed to the Google Groups
> "ScyllaDB users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to scylladb-user...@googlegroups.com.
> To post to this group, send email to scyllad...@googlegroups.com.
> Visit this group at https://groups.google.com/group/scylladb-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/scylladb-users/65de35b6-5d08-4c1e-ac39-c26b68d654d4%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Dor Laor]

@amnon tested OpsCenter with Scylla and few basic paths worked.

In general it's a dead end with OpsCenter since Datastax closed the door and it

won't work with Apache Cassandra. 

Regarding Glauber's comment, we expect 2.1.x CQL compatibility and it could be that

Devcenter expects something else. It could be a minor bug in Scylla too. 

Can you share the tcpdump data? 

In general we plan on releasing our own Opscenter-like app, later this year.

Until that happens we have scyllatop and a set of graphite docker images.

To view this discussion on the web visit https://groups.google.com/d/msgid/scylladb-users/CAD-J%3DzZJtUbUW%3Dac5S%2Boryq3h0sNa4%3Dm5D0cGehQKvndEMwjeQ%40mail.gmail.com.

[Darren Landoll]

We have seen similar problems in the past with cqlsh, that expected
specific version strings.
But you're the first - to the best of my knowledge - to be testing
DevCenter. At least in terms of reporting to the mailing list.

If this is something easy for you to do, would you mind sending us the
connection data for Scylla, and a similar trace for Cassandra?

 

The only thing I had to do to get the initial connection working was create an empty "OpsCenter" keyspace in my cluster as DevCenter was throwing exceptions and expecting it to be there.

Attached are a couple Wireshark captures for the latest 2 versions of DevCenter. Looks like DevCenter is expecting 3.0 versions so that may have something to do with it. The actual query that gives me the error in DevCenter is at the end of each trace.

[Darren Landoll]

 

The only thing I had to do to get the initial connection working was create an empty "OpsCenter" keyspace in my cluster as DevCenter was throwing exceptions and expecting it to be there.

Attached are a couple Wireshark captures for the latest 2 versions of DevCenter. Looks like DevCenter is expecting 3.0 versions so that may have something to do with it. The actual query that gives me the error in DevCenter is at the end of each trace.

I compared my Wireshark captures with version 3 of the CQL protocol and couldn't find any issues with that implementation. I started to wonder if it might have something to do with the Query Trace feature in DevCenter and after looking through their documentation I found a way to disable it (see link below). After disabling Query Trace, I was able to execute and display results for the simple query I've been testing in DevCenter. Not sure if any more advanced queries or capabilities will also cause trouble, but I'll continue testing as I move forward.

http://docs.datastax.com/en/developer/devcenter/doc/devcenter/dcQueryTrace.html?scroll=dc-query-trace__disable-enable-query-trace-section

[Avi Kivity]

Cool.  We'll be working to implement Query Trace, as it is a useful feature on its own.