Fix bug pangloss/pacer#51, so now even after the usage of a BatchInserter or a GraphML Import, whenever we create a key index this is properly fix.
I've read, and test, some other strategies like passing some variables to the Neo4j constructor on runtime, but never success with anyone of that, so I think to flush the index content just in case of a neo4j graph is a proper solution to that. However I'm open to suggestions ;-)
fix the pacer bug #51, neo4j auto index failing to create autoindex a…
…fter a batch import
I'm wondering if this fix should be submitted directly to the Blueprints Neo4j project. What do you think?
I'm not sure about it, as far as we're speaking about a Neo4j problem (see neo4j/neo4j#173) first of all we should understand or ask if the blueprints project make you create the key index before or after the GraphML import. I was unable to see any bug report regarding that, so I understand the current blueprint behaviour is to create the key index before the graphml import in the case of neo4j, but I'm not sure.