Data Transfer from Titan to Janusgraph


sambhajic...@...
 

I am currently using Titan 1.0.0 with Cassandra backend and Elasticsearch for indexing. Our graph has 100 million nodes and 170 million edges with a replication factor of 2 and distributed across a cluster of 3 cassandra nodes. We recently decided to switch to JanusGraph for future development. As the column family names in Titan and JanusGraph are different, What would be the best way to transfer data from Titan to JanusGraph?


Misha Brukman <mbru...@...>
 

The idea is that you shouldn't have to transfer any data, you can just configure JanusGraph flags to match the default values in Titan, such that it would just work in-place.

Since Titan/JanusGraph are themselves stateless, you should be able to just shut down Titan and bring up JanusGraph with a new configuration to match the same config and read the same data.

Here are the Cassandra-related configuration flags:

My guess is that the most important one here is the parameter "storage.cassandra.keyspace" which defaults to "titan" in Titan and "janusgraph" in JanusGraph; setting this parameter to "titan" in your config for JanusGraph should make it backwards-compatible with your data.

Are there any other issues that you see with transition from Titan to JanusGraph while using Cassandra?

On Tue, Apr 18, 2017 at 9:03 PM, <sambhajic...@...> wrote:
I am currently using Titan 1.0.0 with Cassandra backend and Elasticsearch for indexing. Our graph has 100 million nodes and 170 million edges with a replication factor of 2 and distributed across a cluster of 3 cassandra nodes. We recently decided to switch to JanusGraph for future development. As the column family names in Titan and JanusGraph are different, What would be the best way to transfer data from Titan to JanusGraph?

--
You received this message because you are subscribed to the Google Groups "JanusGraph users list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


sambhajic...@...
 

Hey,

That worked perfectly. Thanks a lot!!!!

Regards,
Neelesh


On Wednesday, April 19, 2017 at 1:14:08 PM UTC+5:30, Misha Brukman wrote:
The idea is that you shouldn't have to transfer any data, you can just configure JanusGraph flags to match the default values in Titan, such that it would just work in-place.

Since Titan/JanusGraph are themselves stateless, you should be able to just shut down Titan and bring up JanusGraph with a new configuration to match the same config and read the same data.

Here are the Cassandra-related configuration flags:

My guess is that the most important one here is the parameter "storage.cassandra.keyspace" which defaults to "titan" in Titan and "janusgraph" in JanusGraph; setting this parameter to "titan" in your config for JanusGraph should make it backwards-compatible with your data.

Are there any other issues that you see with transition from Titan to JanusGraph while using Cassandra?

On Tue, Apr 18, 2017 at 9:03 PM, <samb...@...> wrote:
I am currently using Titan 1.0.0 with Cassandra backend and Elasticsearch for indexing. Our graph has 100 million nodes and 170 million edges with a replication factor of 2 and distributed across a cluster of 3 cassandra nodes. We recently decided to switch to JanusGraph for future development. As the column family names in Titan and JanusGraph are different, What would be the best way to transfer data from Titan to JanusGraph?

--
You received this message because you are subscribed to the Google Groups "JanusGraph users list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.