Cassandra keyspace (storage.cassandra.keyspace) and (titan and titan-version) about janusgraph HOT 7 CLOSED

Thanks for the report and sorry for the trouble! That looks like a bug in JanusGraph.

As part of the migration from the name Titan to JanusGraph, we replaced all code and constances from titan-* to janusgraph-* but we did not set compatible versions, so we need to update GraphDatabaseConfiguration.java as well as JanusGraphConstants.java to do the following:

• allow titan-version as a valid configuration key for backwards-compatibility with Titan
• allow janusgraph-version as a valid config key for folks who start with JanusGraph
• set up compatible versions both for Titan 1.0 as well as JanusGraph 0.1.0-SNAPSHOT

If you're up for making these changes, we'd love to accept your contribution! Otherwise, we'll need someone to pick this up to fix this issue.

from janusgraph.

Sure, I'll pick it up tomorrow and send a fix

from janusgraph.

@rafatuita — thanks!

Please note that we'll need you (or an authorized officer of your company) to sign either the ICLA or CCLA, as appropriate, before we can accept any contributions.

from janusgraph.

got the fix ready, the approach I took was to go first on JanusGraph version, try/catch for the exception and look or a compatibility with titan and their versions, so it always tries janus first, if fails, go compatible check.

janusgraph.compatible.versions are stored on main pom.xmlfile, so I just added titan.backward.compatible.versions with those IDs 1.0.0,1.1.0-SNAPSHOT.

Since this is just a compatibility issue, didn't see a reason to work on this https://github.com/JanusGraph/janusgraph/blob/ec441ac6d87f3359c9740075786ec6de3651745e/janusgraph-dist/src/release/release.sh

let me know your thoughts.

from janusgraph.

@rafatuita good work on this one, can we close it out at this point?

from janusgraph.

@twilmes sure, you can close it by now.

from janusgraph.

Thanks @rafatuita. Closing as fixed by #80.

from janusgraph.