Not at all, I'm glad potential issues comes out in the open immediately and
don't stay and get people frustrated. That this particular issue was
unrelated to neo4j doesn't change that. Keep all the feedback coming, it
makes neo4j improve and evolve.
Best,
Mattias
2011/6/27 Craig Taverner
Please elaborate on how you are using your index. Are you using
Index#remove(entity,key) or Index#remove(entity) followed by get/query in
the same tx? There was a recent change in transactional state
implementation, where a full representation (in-memory lucene index) was
needed for it to be able
Sorry for the lack of details. I wrote the email late at night, as I am
again.
Anyway, the relevant code in github is
OSMImporter.javahttps://github.com/neo4j/neo4j-spatial/blob/master/src/main/java/org/neo4j/gis/spatial/osm/OSMImporter.java.
When adding nodes to the graph, it also adds the
Hi again,
My apologies, but I have found the problem, and it is in the OSMImporter
itself, nothing to do with Lucene or Neo4j. Peter made a
commithttps://github.com/neo4j/neo4j-spatial/commit/b5e0f1d1a11ed9c8b2b8074f529362a1607a7643#src/main/java/org/neo4j/gis/spatial/osm/OSMImporter.javain
May
Hi,
Has anyone noticed a slowdown of imports into neo4j with recent snapshots?
Neo4j-spatial importing OSM data (which uses lucene to find matching nodes
for ways) is suddenly running much slower than usual on non-batch imports.
For most of my medium sized test cases, I normally have surprisingly
To: Neo user discussions
Subject: [Neo4j] Recent slowdown in imports with lucene
Hi,
Has anyone noticed a slowdown of imports into neo4j with recent snapshots?
Neo4j-spatial importing OSM data (which uses lucene to find matching nodes
for ways) is suddenly running much slower than usual on non-batch
6 matches
Mail list logo
