Ben, that is faulty behavior, since the Batchinseter should insert the same data as in normal operations. Could you provide a test and maybe fix it (fork on GIThub)? Would be awesome! Otherwise, raise an issue in https://github.com/neo4j/community so we can get to it ASAP!
Cheers, /peter neubauer GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer http://www.neo4j.org - Your high performance graph database. http://startupbootcamp.org/ - Öresund - Innovation happens HERE. http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party. On Sat, Aug 27, 2011 at 3:12 AM, Benjamin Gehrels < [email protected]> wrote: > Hi folks, > > i've just - after a lot of searching - recognized, that the > LuceneBatchInserterIndex handles ValueContext[] a little bit different > than the normal one: > > When calling add(), the LuceneIndex converts its Parameter to an > Object[], and checks for each element if it is an ValueContext. > > The BatchInserterIndex checks the input parameter for beeing a > ValueContext first, than converts it to an Object[] and indexing it > Element by element. > > This results in a ValueContext[]{numeric(123L), numeric(456L)} being > indexed as (123L,456L) when using the normal LuceneIndex, but > ("123","456") when using the BatchInserterIndex. > > Is this intended behaviour? > > Best regards, > Benjamin > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
