Re: [Neo4j] Schema#awaitIndexOnline forever?

2015-05-11 Thread Mattias Persson
Yes, Michael is correct, you must await the index to be ONLINE in a separate transaction because the index starts to populate first when closing the transactions. On Monday, May 11, 2015 at 2:35:58 AM UTC+2, Michael Hunger wrote: Florent, can you best raise that as an GitHub issue? How much

Re: [Neo4j] Schema#awaitIndexOnline forever?

2015-05-10 Thread Michael Hunger
Florent, can you best raise that as an GitHub issue? How much data is in your test-database? What happens if you run the await in a separate tx ? Michael Am 10.05.2015 um 14:49 schrieb Florent Biville florent.bivi...@gmail.com: Hi, I'm trying to run the following snippet (with Neo4j

[Neo4j] Schema#awaitIndexOnline forever?

2015-05-10 Thread Florent Biville
Hi, I'm trying to run the following snippet (with Neo4j v2.2.1 / impermanent graph database): try (Transaction tx = graphDB.beginTx()) { IndexDefinition definition = graphDB.schema() .indexFor(Labels.ARTIST) .on(name) .create();