SegmentReader with custom setting of deletedDocs, single reusable FieldsReader

One of the bottlenecks I have noticed testing Ocean realtime search is the delete process which involves writing several files for each possibly single delete of a document in SegmentReader. The best way to handle the deletes is too simply keep them in memory without flushing them to disk, saving

[jira] Commented: (LUCENE-1314) IndexReader.reopen(boolean force)

[ https://issues.apache.org/jira/browse/LUCENE-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607609#action_12607609 ] Jason Rutherglen commented on LUCENE-1314: -- A package protected field "boolean op

[jira] Updated: (LUCENE-1314) IndexReader.reopen(boolean force)

[ https://issues.apache.org/jira/browse/LUCENE-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Rutherglen updated LUCENE-1314: - Attachment: lucene-1314.patch lucene-1314.patch Included the changes mentioned to allow

[jira] Resolved: (LUCENE-1311) Add ability to open prior commits to IndexReader

[ https://issues.apache.org/jira/browse/LUCENE-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-1311. Resolution: Fixed > Add ability to open prior commits to IndexReader > ---

[jira] Updated: (LUCENE-1314) IndexReader.reopen(boolean force)

[ https://issues.apache.org/jira/browse/LUCENE-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Rutherglen updated LUCENE-1314: - Attachment: lucene-1314.patch lucene-1314.patch Added SegmentReader protected BitVector

[jira] Commented: (LUCENE-1312) InstantiatedIndexReader does not implement getFieldNames properly

[ https://issues.apache.org/jira/browse/LUCENE-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607683#action_12607683 ] Karl Wettin commented on LUCENE-1312: - bq. Will be interesting to try out your new pat

[jira] Commented: (LUCENE-1312) InstantiatedIndexReader does not implement getFieldNames properly

[ https://issues.apache.org/jira/browse/LUCENE-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607686#action_12607686 ] Jason Rutherglen commented on LUCENE-1312: -- The error I was seeing in SegmenMerge

Potential bug in SloppyPhraseScorer

Hi list (and hopefully Doron), Don't know if Doron saw this Jira issue: https://issues.apache.org/jira/browse/LUCENE-1310 Given that this bug only surfaces with repeating terms in the target phrase, I wonder if it's related to the changes made to fix Lucene-736? We've looked at the code, an

per-field similarity

Something to consider for Lucene 3 is to have something to retrieve Similarity per-field rather than passing the field name into some functions... benefits: - Would allow customizing most Similarity functions per-field - Performance: Similarity for a field could be looked up once at the beginning

[jira] Updated: (LUCENE-1313) Ocean Realtime Search

[ https://issues.apache.org/jira/browse/LUCENE-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Rutherglen updated LUCENE-1313: - Attachment: lucene-1313.patch lucene-1313.patch Depends on LUCENE-1312 and LUCENE-1314.

How to do a query using less than or greater than

Hi all, I've been looking at the lucene documentation and the source code and I can't seem to find a greater than or less than operator in the default query syntax for lucene. Does anyone one know if they exists and how to use them? For a concrete example I'm looking to do a query on a date fie

[jira] Commented: (LUCENE-1312) InstantiatedIndexReader does not implement getFieldNames properly

[ https://issues.apache.org/jira/browse/LUCENE-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607813#action_12607813 ] Karl Wettin commented on LUCENE-1312: - bq. The error I was seeing in SegmenMerger was

[jira] Commented: (LUCENE-1312) InstantiatedIndexReader does not implement getFieldNames properly

[ https://issues.apache.org/jira/browse/LUCENE-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607828#action_12607828 ] Jason Rutherglen commented on LUCENE-1312: -- I have an exception but it's differen

[jira] Commented: (LUCENE-1312) InstantiatedIndexReader does not implement getFieldNames properly

[ https://issues.apache.org/jira/browse/LUCENE-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607833#action_12607833 ] Jason Rutherglen commented on LUCENE-1312: -- In order to simulate a different Inde

[jira] Commented: (LUCENE-1312) InstantiatedIndexReader does not implement getFieldNames properly

[ https://issues.apache.org/jira/browse/LUCENE-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607838#action_12607838 ] Jason Rutherglen commented on LUCENE-1312: -- Because the patch looks like a mess w

Re: How to do a query using less than or greater than

I do not believe that the operators "<" and ">" are supported by Lucene, but you can use RANGE SEARCH to do achieve what you want. Just put an unreachable upper boundary for "greater than" or lower boundary for "less than". J.D. On Tue, Jun 24, 2008 at 3:31 PM, Kyle Miller <[EMAIL PROTECTED]> wrot

[jira] Commented: (LUCENE-1314) IndexReader.reopen(boolean force)

[ https://issues.apache.org/jira/browse/LUCENE-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607857#action_12607857 ] Nadav Har'El commented on LUCENE-1314: -- At first glance, my opinion was that adding t

Fwd: changing index format

Hi guys: Perhaps I should have posted this to this list in the first place. I am trying to work on a patch to for each term, expose minDoc and maxDoc. This value can be retrieve while constructing the TermInfo. Knowing these two values can be very helpful in caching DocIdSet for a giv