[jira] Commented: (LUCENE-500) Lucene 2.0 requirements - Remove all deprecated code

[ http://issues.apache.org/jira/browse/LUCENE-500?page=comments#action_12371389 ] paul.elschot commented on LUCENE-500: - Here, at revision 387786, the target common.compile-test fails because a few previously deprecated methods are still being used in t

[jira] Commented: (LUCENE-500) Lucene 2.0 requirements - Remove all deprecated code

[ http://issues.apache.org/jira/browse/LUCENE-500?page=comments#action_12371392 ] paul.elschot commented on LUCENE-500: - Oops, I checked svn status for the test code, and the two tests that cause these compiler errors never made it into the trunk, so pl

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

TermInfosReader and other + instance ThreadLocal => transient/odd memory leaks => OutOfMemoryException Key: LUCENE-529 URL: http://issues.apache.org/jira/browse/LUCENE-529

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

There is only a single TermInfoReader per index. In order to share this instance with multiple threads, and avoid the overhead of creating new enumerators for each request, the enumerator for the thread is stored in a thread local. Normally, in a server application, threads are pooled, so new t

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

There was a small mistake - there is a single TermInfoReader per segment. -Original Message- From: Robert Engels [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 22, 2006 11:37 AM To: java-dev@lucene.apache.org Subject: RE: [jira] Created: (LUCENE-529) TermInfosReader and other + instance

query parsing

Using lucene 1.4.3, if I use the query +cat AND -dog it parses to +cat -dog and works correctly. If I use (+cat) AND (-dog) it parses to +(+cat) +(-dog) and returns no results. Is this a known issue?

[jira] Created: (LUCENE-530) Extend NumberTools to support int/long/float/double to string

Extend NumberTools to support int/long/float/double to string -- Key: LUCENE-530 URL: http://issues.apache.org/jira/browse/LUCENE-530 Project: Lucene - Java Type: Improvement Components: Analysis Ve

[jira] Commented: (LUCENE-530) Extend NumberTools to support int/long/float/double to string

[ http://issues.apache.org/jira/browse/LUCENE-530?page=comments#action_12371446 ] Yonik Seeley commented on LUCENE-530: - Here is how Solr did it: http://svn.apache.org/viewcvs.cgi/incubator/solr/trunk/src/java/org/apache/solr/util/NumberUtils.java?rev=38

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

For every IndexReader that is opened - there is one SegmentReader for every segment in the index - with its thread local - for each of these there is a TermInfosReader + its thread local. So I get 2 * (no of index segments) thread locals. I am creating index readers for a main index and t

Re: query parsing

On Mittwoch 22 März 2006 18:49, Robert Engels wrote: > If I use > > (+cat) AND (-dog) > > it parses to > > +(+cat) +(-dog) > > and returns no results. > > Is this a known issue? Basically yes. QueryParser is known to exhibit strange behavior when combining +/- and AND/OR/NOT. Regards Daniel -

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

Creating and destroying threads is one of the worst performing operations, and should be avoided at ALMOST all costs. I do not see this problem in my server impl of Lucene, internally multithreaded, and accessed via multiple threads from a Tomcat server. I have to assume many (most?) users of Luce

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

[ http://issues.apache.org/jira/browse/LUCENE-529?page=comments#action_12371463 ] Otis Gospodnetic commented on LUCENE-529: - This sounds like something that should be reproducable when written as a JUnit test. Could you write one and attach it to t

RE: query parsing

Any suggestions on what to do then, as the following query exhibits the same behavior (+cat) (-dog) Due to the implied AND. Removing the parenthesis allows it to work. It doesn't seem that adding parenthesis in this case should cause the query to fail??? Doesn't it suggest that there is a bug