1] There is a note in documentation, that you cannot change keyspace after it is defined and used. And you said that when you change the keyspace in the configuration, titan will silently create new keyspace in cassandra on background. So there is no real way how to change the keyspace in configuration, right? Is it meant that you cannot change it from cassandra CLI? But even though you change it in CLI it would be a new keyspace I think...
2] Are the titan standard indices (maybe they are called native?) stored in backend storage as well (in my case cassandra)?
3] When using elasticsearch, there is an default index of name "search" in example configuration files. However, when I look into ES, there is an index called "titan" and not "search". Does this mean that the "search" is just only for an identification used by titan and the index in ES is called "titan"?
4] When I create a second graph by introducing a new keyspace in configuration, is there a possibility to have separate indices for each of the graphs when using elasticsearch? Or is it complicated and it was never meant to have multiple graphs in one storage backend (cassandra) with different external indices (in my case ES) for each of the graphs, and you have to use only single ES index called "titan" (which is created silently by Titan) within one Titan instance for all graphs stored in the storage backend?
5] Is it better to have two different cassandra instances when I want one graph for development and one graph for unit tests? Or can I just use single cassandra instance with multiple graphs in it?
This is the full list of configuration options for Elasticsearch. Note, that each of these options needs to be prefixed with
[INDEX-NAME]stands for the name of the index backend. For instance, if the index backend is named search then these configuration options need to be prefixed with
two disconnected graphs in the same Titan instance.