[jira] Commented: (LUCENE-436) [PATCH] TermInfosReader, SegmentTermEnum Out Of Memory Exception

[ http://issues.apache.org/jira/browse/LUCENE-436?page=comments#action_12377764 ] Andy Hind commented on LUCENE-436: -- I agree this is not strictly an issue with lucenebut . Lucene has an unusual use pattern for thread locals (instance vs static

Statistaical evaluation of modifications to a Lucene query based on search logs

Hi! I'm developing a new type of Query, called a SubPhraseQuery. I have sent a message to the list regarding this and Doug was kind enough to put me on the right track. The query is simply a PhraseQuery where all terms are search, but, if any of the subphrases are found, it boosts the

[jira] Commented: (LUCENE-436) [PATCH] TermInfosReader, SegmentTermEnum Out Of Memory Exception

[ http://issues.apache.org/jira/browse/LUCENE-436?page=comments#action_12377815 ] robert engels commented on LUCENE-436: -- To restate: It is NOT a bug. It is a design decision in the JDK between performance and memory use. This decisions changed a bit

[jira] Commented: (LUCENE-436) [PATCH] TermInfosReader, SegmentTermEnum Out Of Memory Exception

[ http://issues.apache.org/jira/browse/LUCENE-436?page=comments#action_12377826 ] robert engels commented on LUCENE-436: -- Oops. Last comment was not quite correct. The reason the finalize() methods are worthless for clearing the ThreadLocal entries,

[jira] Commented: (LUCENE-436) [PATCH] TermInfosReader, SegmentTermEnum Out Of Memory Exception

[ http://issues.apache.org/jira/browse/LUCENE-436?page=comments#action_12377850 ] Nicholaus Shupe commented on LUCENE-436: However, this problem is classified is eventually irrelevant to me. Bug in the JDK, bug in Lucene, not a bug, it's all the

[jira] Commented: (LUCENE-436) [PATCH] TermInfosReader, SegmentTermEnum Out Of Memory Exception

[ http://issues.apache.org/jira/browse/LUCENE-436?page=comments#action_12377855 ] robert engels commented on LUCENE-436: -- Are you always loading your indexes using RAMDirectories? I use multi-hundred megabytes indexes, with 196 max heap, and it runs

[jira] Updated: (LUCENE-436) [PATCH] TermInfosReader, SegmentTermEnum Out Of Memory Exception

[ http://issues.apache.org/jira/browse/LUCENE-436?page=all ] robert engels updated LUCENE-436: - Attachment: TermInfosReader.java better version of TermInfos reader that avoid multiple ThreadLocal.get() calls [PATCH] TermInfosReader, SegmentTermEnum

[jira] Resolved: (LUCENE-529) TermInfosReader and other + instance ThreadLocal = transient/odd memory leaks = OutOfMemoryException

[ http://issues.apache.org/jira/browse/LUCENE-529?page=all ] Otis Gospodnetic resolved LUCENE-529: - Resolution: Duplicate Duplicate of LUCENE-436 TermInfosReader and other + instance ThreadLocal = transient/odd memory leaks =

[jira] Commented: (LUCENE-436) [PATCH] TermInfosReader, SegmentTermEnum Out Of Memory Exception

[ http://issues.apache.org/jira/browse/LUCENE-436?page=comments#action_12377863 ] Nicholaus Shupe commented on LUCENE-436: I am not using a RAMDirectory. I never indicated as such. Here's the the way I load my index: reader =

Re: Statistaical evaluation of modifications to a Lucene query based on search logs

On Thu, May 04, 2006 at 10:52:46AM -0400, Daniel Shane wrote: I'm developing a new type of Query, called a SubPhraseQuery. I have sent a message to the list regarding this and Doug was kind enough to put me on the right track. The query is simply a PhraseQuery where all terms are search,

Re: Statistaical evaluation of modifications to a Lucene query based on search logs

: It's got one difference from yours, in that the terms are allowed to : occur in any order in the sub-phrases (so phrase C B from your : original example is scored like B C). there's a much bigger differnece, in that your technique won't reqard documents where B and C are near eachother, but A

[jira] Commented: (LUCENE-436) [PATCH] TermInfosReader, SegmentTermEnum Out Of Memory Exception

[ http://issues.apache.org/jira/browse/LUCENE-436?page=comments#action_12377905 ] kieran commented on LUCENE-436: --- Robert Engels description of the ThreadLocal issue in JDK 1.4.2 provides a very plausible explanation for why this is not a bug, either in

[jira] Commented: (LUCENE-436) [PATCH] TermInfosReader, SegmentTermEnum Out Of Memory Exception

[ http://issues.apache.org/jira/browse/LUCENE-436?page=comments#action_12377933 ] Erik Hatcher commented on LUCENE-436: - Please, everyone, let's keep this discussion technical and factual and avoid making degrading statements to one another. It