Re: Document scoring

I modify TopDocsCollector and collect some to-score value store in index to an array and then calculate them with similar score,return final score to sort the docs. -- View this message in context: http://lucene.472066.n3.nabble.com/Document-scoring-tp4018582p4018962.html Sent from the Lucene

Re: "read past EOF" when merge

Sorry,I can't reproduce in local... "If at any time you accidentally had two writers open on the same index, it could have created this corruption. " I use singleton to create/get IndexWriter ,and change LockFactory to SimpleFSLockFactory (NativeFSLockFactory before) .Maybe a long time it was run

Re: "read past EOF" when merge

oh ,thx,I don't know CheckIndex before...and I use to fix my error index,it is OK... I use NFS to share my index,and no change to the LogFactory. How could I avoid this problem,and not only fix after it was broken suddenly? -- View this message in context: http://lucene.472066.n3.nabble.com/rea

"read past EOF" when merge

The exception "read past EOF" Bothering me a long time, trace at below. Exception in thread "Lucene Merge Thread #7" org.apache.lucene.index.MergePolicy$MergeException: java.io.IOException: read past EOF at org.apache.lucene.index.ConcurrentMergeScheduler.handleMergeException(ConcurrentM

Re: Why read past EOF

Oh,I made a mistake.Our testing server's time is faster hours than it should be.I reminded workmate to modify it,and index maintain in a range size. Thank you all the same. -- View this message in context: http://lucene.472066.n3.nabble.com/Why-read-past-EOF-tp3639401p3752592.html Sent from the L

Re: Why read past EOF

My IndexWriter only create once and cached in memery. I restart tomcat this morning,and the index become 94M...But I restart yesterday serveral times ,it still too big... My deletion policy is in above reply,it only compare the timestamp,not actually deleting commits. -- View this message in cont

Re: Why read past EOF

http://lucene.472066.n3.nabble.com/file/n3746464/index.jpg The index files are same size,and the index increase to 7.5G in one day,but it should only 90-100M... -- View this message in context: http://lucene.472066.n3.nabble.com/Why-read-past-EOF-tp3639401p3746464.html Sent from the Lucene - J

Re: Why read past EOF

Thanks for your advice and patient. I modify "present",and use stress testing two day(loop search and index),the "read past EOF" didn't appeared yet. My system structure should be improved, I hope to get your proposal again in the future. -- View this message in context: http://lucene.472066.n3.n

Re: Why read past EOF

public class PostponeCommitDeletionPolicy implements IndexDeletionPolicy { private final static long deletionPostPone = 60; public void onInit(List commits) { // Note that commits.size() should normally be 1: onCommit(commits); }

Re: Why read past EOF

ok,thanks. I modify my program like you suggest.But another problem appear: java.lang.ArrayIndexOutOfBoundsException: -1 at org.apache.lucene.index.TermInfosReader.seekEnum(TermInfosReader.java:203) at org.apache.lucene.index.TermInfosReader.get(TermInfosReader.java:273) at

Re: Why read past EOF

eg,I implement IndexDeletionPolicy and the onCommit(): public void onCommit(List commits) { // Note that commits.size() should normally be 2 (if not // called by onInit above): int size = commits.size(); long present = System.

Re: Why read past EOF

Thanks,you suggest me to creat a my IndexDeletionPolicy,I check KeepOnlyLastCommitDeletionPolicy.onCommit,it invoke CommitPoint.delete(),but it only : deleted = true; commitsToDelete.add(this); ,and the delete index file operation in other place. Is it useful that I postpone invoke

Re: Why read past EOF

Does it means I only to ensure reopen readers before deleted.I use default IndexDeletionPolicy: KeepOnlyLastCommitDeletionPolicy.And another two IndexDeletionPolicy,SnapshotDeletionPolicy and PersistentSnapshotDeletionPolicy,I am watching now.Are they useful to this problem? -- View this message i

Re: Why read past EOF

yes，i use it to share index,and one server is master to writer and read;the others are slaver,read only. -- View this message in context: http://lucene.472066.n3.nabble.com/Why-read-past-EOF-tp3639401p3644074.html Sent from the Lucene - Java Users mailing list archive at Nabble.com.

Why read past EOF

Hi, I use lucene 3.4.0 in a search project,but encounter a problem and i don't know how to resolve. I index and it run well,but one week or two(it appear two times,first run one week,second two),it can't be searched,and the trace at below. Thank you! java.io.IOException: read past EOF a

Re: Why read past EOF

and my index create is: IndexWriterConfig indexWriterConfig = new IndexWriterConfig(Version.LUCENE_34, getAnalyzer()); indexWriterConfig.setOpenMode(IndexWriterConfig.OpenMode.CREATE_OR_APPEND); writer = new IndexWriter(directory, indexWriterConfig); writer.commit(); -- View this message in conte

Re: Why read past EOF

and my IndexWriter create is: IndexWriterConfig indexWriterConfig = new IndexWriterConfig(Version.LUCENE_34, getAnalyzer()); indexWriterConfig.setOpenMode(IndexWriterConfig.OpenMode.CREATE_OR_APPEND); writer = new IndexWriter(directory, indexWriterConfig); writer.commit(); -- View this message i