Hi,
More Lucene index errors this week...
We started using below utility to check the index right after the LOAD CSV operation completes.
java -cp
/home/neo4j-community-2.3.1/lib/lucene-core-3.6.2.jar -ea:org.apache.lucene...
org.apache.lucene.index.CheckIndex
We receive several error messages like the below...
--------------------------------------------------
An error has occurred on index at folder /home/neo4jsupp/neo4j-community-2.3.1/data/INM_06282016/schema/index/lucene/5, please check http://hln2080p:7474/browser.Opening index @ /home/neo4jsupp/neo4j-community-2.3.1/data/INM_06282016/schema/index/lucene/5Segments file=segments_9 numSegments=2 version=3.6.2 format=FORMAT_3_1 [Lucene 3.1+] userData={status=online} 1 of 2: name=_0 docCount=28809 compound=true hasProx=false numFiles=1 size (MB)=1.061 diagnostics = {os=Linux, java.vendor=Oracle Corporation, java.version=1.8.0_71, lucene.version=3.6.2 1423725 - rmuir - 2012-12-18 19:45:40, os.arch=amd64, source=flush, os.version=3.10.0-327.13.1.el7.x86_64} no deletions test: open reader.........OK test: fields..............OK [2 fields] test: field norms.........OK [0 fields] test: terms, freq, prox...OK [57618 terms; 57618 terms/docs pairs; 57618 tokens] test: stored fields.......OK [28809 total field count; avg 1 fields per doc] test: term vectors........OK [0 total vector count; avg 0 term/freq vector fields per doc] 2 of 2: name=_1h docCount=27 compound=true hasProx=false numFiles=1FAILED WARNING: fixIndex() would remove reference to this segment; full exception:java.io.FileNotFoundException: _1h.cfs at org.apache.lucene.store.FSDirectory.fileLength(FSDirectory.java:284) at org.apache.lucene.index.SegmentInfo.sizeInBytes(SegmentInfo.java:303) at org.apache.lucene.index.CheckIndex.checkIndex(CheckIndex.java:494) at org.apache.lucene.index.CheckIndex.main(CheckIndex.java:1064)WARNING: 1 broken segments (containing 27 documents) detectedWARNING: would write new segments file, and 27 documents would be lost, if -fix were specified --------------------------------------------------
Q1) Is this a Neo4j implementation of Lucene index issue or an issue with Lucene3.6.2 version itself?
Q2) We notice Neo4j 3.0.3 Community uses Lucene 5.5.0. Will moving to Neo4j 3.0 avoid these kind of errors?
Sample syntax for LOAD CSV is below...
./bin/neo4j-shell -host <HOSTNAME> -port
<PORTNUM> -c "USING PERIODIC COMMIT LOAD CSV FROM
'file:////home//tmp//<FILENAME>.csv' AS line MATCH (v1:VSID
{code:line[0]}) match (v2:VSID {code:line[4]}) merge (v1) -[r:CONNECT]->(v2)
ON CREATE SET r.transit_time = toFloat(line[3]) ON MATCH SET r.transit_time =
toFloat(line[3]);"
Thanks in advance.