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

[ https://issues.apache.org/jira/browse/LUCENE-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12773402#action_12773402 ] Nadav Har'El commented on LUCENE-504: - Hi Uwe, I think that even though PriorityQueue

[jira] Commented: (LUCENE-1899) Inefficient growth of OpenBitSet

[ https://issues.apache.org/jira/browse/LUCENE-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12752931#action_12752931 ] Nadav Har'El commented on LUCENE-1899: -- Hi Shai, I guess you're right that if there's

[jira] Commented: (LUCENE-1899) Inefficient growth of OpenBitSet

[ https://issues.apache.org/jira/browse/LUCENE-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12753019#action_12753019 ] Nadav Har'El commented on LUCENE-1899: -- Yes, you're right, 12.5%. Or actually,

[jira] Created: (LUCENE-1899) Inefficient growth of OpenBitSet

Inefficient growth of OpenBitSet Key: LUCENE-1899 URL: https://issues.apache.org/jira/browse/LUCENE-1899 Project: Lucene - Java Issue Type: Bug Components: Store Affects Versions: 2.9

[jira] Commented: (LUCENE-1470) Add TrieRangeQuery to contrib

[ https://issues.apache.org/jira/browse/LUCENE-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12652002#action_12652002 ] Nadav Har'El commented on LUCENE-1470: -- Hi, I just wanted to comment that a similar

[jira] Commented: (LUCENE-1382) Allow storing user data when IndexWriter.commit() is called

[ https://issues.apache.org/jira/browse/LUCENE-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12630561#action_12630561 ] Nadav Har'El commented on LUCENE-1382: -- Hi Mike, If you add this feature, I suggest

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

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

[jira] Commented: (LUCENE-954) Toggle score normalization in Hits

[ https://issues.apache.org/jira/browse/LUCENE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12579258#action_12579258 ] Nadav Har'El commented on LUCENE-954: - I hate to rain on the parade, but maybe instead

[jira] Commented: (LUCENE-997) Add search timeout support to Lucene

[ https://issues.apache.org/jira/browse/LUCENE-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552174 ] Nadav Har'El commented on LUCENE-997: - I'd like to add my 2 cents on this issue. The more I use Lucene in

[jira] Commented: (LUCENE-1088) PriorityQueue 'wouldBeInserted' method

[ https://issues.apache.org/jira/browse/LUCENE-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550964 ] Nadav Har'El commented on LUCENE-1088: -- Michael, I agree - the most important fix was to make heap protected

[jira] Commented: (LUCENE-695) Improve BufferedIndexInput.readBytes() performance

[ http://issues.apache.org/jira/browse/LUCENE-695?page=comments#action_12444903 ] Nadav Har'El commented on LUCENE-695: - If given a null array? Is this ever done in Lucene? Which should be fixed, the testcase or the code? I don't know -

[jira] Created: (LUCENE-695) Improve BufferedIndexInput.readBytes() performance

Improve BufferedIndexInput.readBytes() performance -- Key: LUCENE-695 URL: http://issues.apache.org/jira/browse/LUCENE-695 Project: Lucene - Java Issue Type: Improvement Components:

[jira] Updated: (LUCENE-695) Improve BufferedIndexInput.readBytes() performance

[ http://issues.apache.org/jira/browse/LUCENE-695?page=all ] Nadav Har'El updated LUCENE-695: Attachment: readbytes.patch The patch, which includes the change to BufferedIndexInput.readBytes(), and a new unit test for that class. Improve

[jira] Commented: (LUCENE-695) Improve BufferedIndexInput.readBytes() performance

[ http://issues.apache.org/jira/browse/LUCENE-695?page=comments#action_12444322 ] Nadav Har'El commented on LUCENE-695: - Sorry, I didn't notice that my fix broke this unit test. Thanks for catching that. What is happening is interesting:

[jira] Updated: (LUCENE-623) RAMDirectory.close() should have a comment about not releasing any resources

[ http://issues.apache.org/jira/browse/LUCENE-623?page=all ] Nadav Har'El updated LUCENE-623: Attachment: ramdirectory.diff I propose a trivial patch, which does two very simple things: 1. RAMDirectory.close(), instead of being a no-op, sets

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

[ 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

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

[ http://issues.apache.org/jira/browse/LUCENE-504?page=all ] Nadav Har'El updated LUCENE-504: Attachment: fuzzyquery.patch This is my proposed patch described above. FuzzyQuery produces a java.lang.NegativeArraySizeException in

[jira] Commented: (LUCENE-554) Possible index corruption if crashing while replacing segments file

[ http://issues.apache.org/jira/browse/LUCENE-554?page=comments#action_12378295 ] Nadav Har'El commented on LUCENE-554: - Hi Otis, sorry about lingering with this patch (I've been very busy, not to mention a daughter two weeks ago :-) I still want to

[jira] Created: (LUCENE-554) Possible index corruption if crashing while replacing segments file

Possible index corruption if crashing while replacing segments file --- Key: LUCENE-554 URL: http://issues.apache.org/jira/browse/LUCENE-554 Project: Lucene - Java Type: Bug Components: Index

[jira] Commented: (LUCENE-130) org.apache.lucene.search.Query.toString(String field) ignores it's only parameter

[ http://issues.apache.org/jira/browse/LUCENE-130?page=comments#action_12373847 ] Nadav Har'El commented on LUCENE-130: - toString(field) works very well, if you understand what it does. Perhaps the javadoc isn't explicit enough on what it does and need

[jira] Commented: (LUCENE-322) [PATCH] Add IndexSearcher.numDocs() method

[ http://issues.apache.org/jira/browse/LUCENE-322?page=comments#action_12373849 ] Nadav Har'El commented on LUCENE-322: - I wonder, is this change at all necessary? After all, we have the IndexSearcher().getIndexReader() function, which returns the