Re: Titan to JanusGraph migration Elasticsearc| "janusgraph" index is created and used , not titan

Jason Plurad <plu...@...>

Hi Akshya,

Thanks for the info, and unfortunately it looks like some scenarios were missed. Note that if you created the Titan graph originally with the `` property set, it would work without additional configuration in JanusGraph.

In your scenario, when opening the graph in JanusGraph with  ``, this warning is shown:

WARN  org.janusgraph.graphdb.configuration.GraphDatabaseConfiguration  - Local setting (Type: GLOBAL_OFFLINE) is overridden by globally managed value (janusgraph).  Use the ManagementSystem interface instead of the local configuration to control this setting.

The additional work you need to do is:

mgmt = graph.openManagement()
.set('', 'titan')
// at this point the graph is closed, so reopen it with the same properties

On Tuesday, April 25, 2017 at 11:18:11 AM UTC-4, Akshaya Rawat wrote:
Refer for other related issue with migration. 
It seems the default name of elastic search index is also changed from 'titan' to  'janusgraph'. 
"" property name option should help. 
However I am afraid its not working. I am using BerkeleyDB+Embedded ES option.  
1.  I created the DB with Titan. 
2. At this point titan index is created. http://localhost:9200/titan returns index definition.  http://localhost:9200/janusgraph/ returns IndexMissingException. 
3. Data is created in titan index. 
4. Now I migrate the code to Janus. I thought index-name should work and added - 
5. Now when I start , storage backend works seamlessly. I can query nodes added with Titan. And new nodes are added. 
6. The index backend does not work well. "janusgraph" index is created ( even when index-name is titan). The new nodes never go to "titan" , they are created in "janusgraph" index. 


Join { to automatically receive all group messages.