If you are looking for another example along the same principals,
(but considerably less sophisticated :) ), see
https://source.sakaiproject.org/svn//search/trunk/search-impl/
This manages a queue of change events on items to be indexed, that
queue is processed by a cluster of search indexer
[
https://issues.apache.org/jira/browse/LUCENE-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520499
]
Ian Boston commented on LUCENE-871:
---
My pleasure, for once to give something back to Lucene :)
FYI, this is used
Done,
https://issues.apache.org/jira/browse/LUCENE-871
Ian
Yonik Seeley wrote:
Thanks Ian, nice improvement!
Could you open a lucene JIRA issue and provide a patch?
(that helps with other things such as IP tracking)
-Yonik
On 4/29/07, Ian Boston <[EMAIL PROTECTED]> wrote:
Hi,
We&#
[
https://issues.apache.org/jira/browse/LUCENE-871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ian Boston updated LUCENE-871:
--
Attachment: ISOLatin1AccentFilter.java.patch
Patch to improve performance,
This was re-created form
, 1.9, 2.0.1, 2.2
Reporter: Ian Boston
The ISOLatin1AccentFilter is a bit slow giving 300+ ms responses when used in a
highligher for output responses.
Patch to follow
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
Hi,
We've been using this filter in a project and found it a bit slow, so
we've re-written it. In tests we did on a 5M string with no accents, we
found the version in trunk to take ~200ms, this version takes about
~12ms. If there are accents, then its not quite as good at about 60ms.
(MacBook
Simon,
Im picking this thread up from the web archive, but I there was some
talk of replication of indexes. This message may not be threaded
correctly. I've just completed a custom FSDirectory implementation that
is designed to work in a cluster with replication.
The anatomy of this cluster i
[
http://issues.apache.org/jira/browse/LUCENE-576?page=comments#action_12413039 ]
Ian Boston commented on LUCENE-576:
---
Found the problem,
This is *NOT* a bug,
I am an Idiot!
I had a stale IndexWriter in the stack, which had old Segment Inforamation
[
http://issues.apache.org/jira/browse/LUCENE-576?page=comments#action_12413035 ]
Ian Boston commented on LUCENE-576:
---
Setting
indexWriter.setMaxMergeDocs(50);
indexWriter.setMergeFactor(50);
Makes the
Environment: 1.9.1, OSX, JDK 1.4.2
Reporter: Ian Boston
IndexWriter.magbeMergeSergments appears to be attempting to merge the same
segments twice in a row which causes a FileNotFoundException in the fnm file
for the segment deep inside FiledInfos.
In the IndexWriter.maybeMergeSegments below
10 matches
Mail list logo
