Re: [Neo4j] Lucene index provider not found in certain cases

(As I answered in another thread) This is a bug in the LuceneIndexBatchInserterIndexProvider class where it doesn't automatically fill in the provider parameter. It has been fixed now, so until M03 send that in yourself... just like the tests do. I'm not sure this is connected to the python

[Neo4j] Lucene index provider not found in certain cases

Hi all, there are two cases (from python and Paddys code below) where a created index is not found. I have been trying to track it down, but cannot reproduce it using the code at