[Neo4j] Behaviour of LuceneIndex vs. BatchInserterIndex for multiple adds

Hi all, as far as i know, the Batch Inserter Index has a slightly different behaviour than the default LuceneIndex: 1. It supports the addition of multiple Key/Value pairs at once and 2. Multiple calls to add() will result in multiple Index entries The default Lucene Index implementation does n

Re: [Neo4j] Test and try/catch block

TemporaryFolder is a Junit-Rule coming with JUnit 4.7 "The TemporaryFolder Rule allows creation of files and folders that are guaranteed to be deleted when the test method finishes (whether it passes or fails)" http://kentbeck.github.com/junit/javadoc/latest/org/junit/rules/TemporaryFolder.html

Re: [Neo4j] BatchInserterIndex and ValueContext[]

> great, will merge it in as soon as you send in the CLA, see > http://wiki.neo4j.org/content/About_Contributor_License_Agreement pull request and CLA are crawling through the sea cables to sweden right now. > For testing, we normally use the ImpermanentGraphDatabase which does exactly > this. I

Re: [Neo4j] BatchInserterIndex and ValueContext[]

Hi Peter, > Could you provide a test and maybe fix it (fork on > GIThub)? Would be awesome! No problem, I'll send you a pull request tonight. I still have one question that already had come to my mind while testing my own app: Have you ever thought of implementing a GraphDatabaseService back

[Neo4j] BatchInserterIndex and ValueContext[]

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. T