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 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 <[email protected] > <javascript:>>: > > 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(); > > graphDB.schema().awaitIndexOnline(definition, XXX, TimeUnit.MILLISECONDS); > > // [...] > > } > > > > No matter how high I set XXX, an IllegalStateException will always be thrown. > > Is this specific to the impermanent graph database? > > > Thanks a lot for your help! > > Florent > > > -- > You received this message because you are subscribed to the Google Groups > "Neo4j" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > For more options, visit https://groups.google.com/d/optout. > > > -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
