Re: Titan to JanusGraph migration Elasticsearc| "janusgraph" index is created and used , not titan
Akshaya Rawat <akshay...@...>
toggle quoted message Show quoted text
This solutions worked for me. Commit had to be done after the force closure.
The graph has to be initialized all over again after this since its closed after this.
This looks to be disruptive solution though the graph is closed and has to be initialized all over again. However this only has to be done once. Once this configuration is forced, it persists. So this could be done as one time migration may be using a script and then it works then on.
Thanks for the solution.
On Wednesday, 26 April 2017 02:36:48 UTC-7, Jason Plurad wrote: