Non-Titan data in Cassandra backed Titan architecture

[Guy Ellis]

Are there any issues or special considerations to be taken into account when storing non-Titan data in a Cassandra cluster that is being used at the store for Titan?

e.g. If a Cassandra cluster already exists in an enterprise for storing arbitrary data and Titan is introduced and configured to use that cluster what do I need to know?

[Stephen Mallette]

Titan will run in its own keyspace so it should be able to coexist with other keyspaces. I guess the question is whether or not titan will compete with your other applications that are storing the non-Titan data. That's the main thing that jumps out in my mind.

On Wed, Aug 17, 2016 at 12:12 PM, Guy Ellis <wildf...@gmail.com> wrote:

Are there any issues or special considerations to be taken into account when storing non-Titan data in a Cassandra cluster that is being used at the store for Titan?

e.g. If a Cassandra cluster already exists in an enterprise for storing arbitrary data and Titan is introduced and configured to use that cluster what do I need to know?

--
You received this message because you are subscribed to the Google Groups "Aurelius" group.
To unsubscribe from this group and stop receiving emails from it, send an email to aureliusgraphs+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/aureliusgraphs/92d2eb63-8792-425f-91de-4c06aff0d8d8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.