[jira] Commented: (LUCENE-504) FuzzyQuery produces a java.lang.NegativeArraySizeException in PriorityQueue.initialize if I use Integer.MAX_VALUE as BooleanQuery.MaxClauseCount

2006-06-29 Thread Nadav Har'El (JIRA)
[ http://issues.apache.org/jira/browse/LUCENE-504?page=comments#action_12418446 ] Nadav Har'El commented on LUCENE-504: - Hi Otis, you did not comment on my patch (fuzzyquery.patch), which I think solves your objections to Doron's previous patch. Do you

Limit of QueryParser ?

2006-06-29 Thread Rakesh Prajapati
HI, What is the maximum number of words allowed by the QueryParser. Thanks Regards, Sr. Software Engineer I- Link Infosoft (G) Pvt . Ltd. [EMAIL PROTECTED]

Re: Limit of QueryParser ?

2006-06-29 Thread Nadav Har'El
On Thu, Jun 29, 2006, Rakesh Prajapati wrote about Limit of QueryParser ?: What is the maximum number of words allowed by the QueryParser. QueryParser generates a BooleanQuery, so this class's MaxClauseCount limits the number of words (each becoming a clause in this BooleanQuery) you can have

[jira] Commented: (LUCENE-305) [PATCH] Lock Framework - allows custom lock mechanism

2006-06-29 Thread Michael McCandless (JIRA)
[ http://issues.apache.org/jira/browse/LUCENE-305?page=comments#action_12418493 ] Michael McCandless commented on LUCENE-305: --- I'm working towards a patch for this. I changed the name of the issue to better reflect the goal. I started with the

Re: [jira] Commented: (LUCENE-305) [PATCH] Lock Framework - allows custom lock mechanism

2006-06-29 Thread Chris Hostetter
: I'd like to sanity check the approach to get any feedback: I don't really know/understand a lot about the current internals of Lucene Locking ... but based on the writeup you've added to Jira, your plan of attack seems like a sound refactoring approach. Your choice to use explicit setters

Re: [jira] Commented: (LUCENE-305) [PATCH] Lock Framework - allows custom lock mechanism

2006-06-29 Thread Michael McCandless
I don't really know/understand a lot about the current internals of Lucene Locking ... but based on the writeup you've added to Jira, your plan of attack seems like a sound refactoring approach. Your choice to use explicit setters instead of a system properties seems to make sense given some

Flexible index format / Payloads Cont'd

2006-06-29 Thread Michael Busch
Hi everyone, I'm working for IBM and started recently looking into Lucene. I am very interested in the topic flexible indexing / payloads, that was discussed a couple of times in the last two months. I did some investigation in the mailing lists, and found several threads about this topic. Those

IndexWriter WRITE_LOCK_TIMEOUT

2006-06-29 Thread Mukul Joshi
Hi, We have written a multi-threaded indexing framework that uses Lucene. To avoid contention on a single IndexWriter, we are using multiple writers. We have enountered a situation where we need to check if a writer object exists for a particular index directory and create it if it doesn't.