[opencms-dev] Lucene lock index

M Butcher mbutcher at grcomputing.net
Thu Mar 4 18:27:00 CET 2004


Ernesto,

Stephan added some methods to IndexManager to support updating the 
index. I don't think they are exposed to CronIndexManager, though.

See updateIndexForFile() and updateFile() in IndexManager.

Matt

Ernesto De Santis wrote:
> Matt
> 
> I believe that this would not happen if the module provided with an update
> function. This is not present in the present version, rigth? Because if use
> createIndex=false I do not have problems, since it does not need to erase
> the index. But indexing with the parameter it crateIndex=flase, appear
> duplicated documents. It does not update the documents, that return them to
> add.
> 
> In addition the performance would be far better, since it would only index,
> or would update the documents that they changed and the new ones.
> 
> Greetings Ernesto.
> 
> 
> ----- Original Message ----- 
> From: "M Butcher" <mbutcher at grcomputing.net>
> To: <opencms-dev at opencms.org>
> Sent: Tuesday, March 02, 2004 8:35 PM
> Subject: Re: [opencms-dev] Lucene lock index
> 
> 
> 
>>Ernesto,
>>
>>Very interesting. I wonder if locking is new in the 1.3 version of
>>Lucene. If you have time, would you mind testing? (I don't have a w2k
>>box... all Linux here).
>>
>>Again, thanks for pointing these things out.
>>
>>Thanks,
>>
>>Matt
>>
>>Ernesto De Santis wrote:
>>
>>>Hello all
>>>
>>>I am using the opencms-lucene module, and I am having a big problem with
>>>re-indexation in Windows which is not happening in Linux.
>>>
>>>The index is being locked for my IndexSearcher I believe. When I perform
>>>the re-indexation, it throws an IOException (for the index files locked
>>>in the
>>>FS)
>>>I am re-indexing with the parameter createIndex=true in the task line.
>>>The OpenCms log looks like:
>>>-------
>>>[02.03.2004 11:25:14] <opencms_cronscheduler> Error running job for
>>>com.opencms.core.CmsCronEntry{25 11 * * * Admin Administrators
>>>net.grcomputing.opencms.search.lucene.CronIndexManager
>>>createIndex=true,registry=C:\lucene-config_es_cu.xml} Error:
>>>java.io.IOException: couldn't delete _3i3.f1
>>> at org.apache.lucene.store.FSDirectory.create(FSDirectory.java:166)
>>> at
>>>org.apache.lucene.store.FSDirectory.getDirectory(FSDirectory.java:135)
>>> at
>>>org.apache.lucene.store.FSDirectory.getDirectory(FSDirectory.java:113)
>>> at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:151)
>>> at net.grcomputing.opencms.search.lucene.IndexManager.doIndex(Unknown
>>>Source)
>>> at
>>>net.grcomputing.opencms.search.lucene.CronIndexManager.launch(Unknown
>>>Source)
>>> at com.opencms.core.CmsCronScheduleJob.run(CmsCronScheduleJob.java:68)
>>>-------
>>>
>>>My system is
>>>OpenCms 5.0.0
>>>Lucene 1.3
>>>opencms-lucene 1.5
>>>Windows 2000
>>>
>>>Under Linux, it works fine! Can you help me?
>>>
>>>Regards
>>>Ernesto.
>>>
>>>_______________________________________________
>>>This mail is send to you from the opencms-dev mailing list
>>>To change your list options, or to unsubscribe from the list, please
> 
> visit
> 
>>>http://mail.opencms.org/mailman/listinfo/opencms-dev
>>
>>_______________________________________________
>>This mail is send to you from the opencms-dev mailing list
>>To change your list options, or to unsubscribe from the list, please visit
>>http://mail.opencms.org/mailman/listinfo/opencms-dev
>>
>>
> 
> 
> _______________________________________________
> This mail is send to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://mail.opencms.org/mailman/listinfo/opencms-dev




More information about the opencms-dev mailing list