[jira] Commented: (LUCENE-821) single norm file still uses up descriptors

[ https://issues.apache.org/jira/browse/LUCENE-821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477759 ] Michael McCandless commented on LUCENE-821: --- The reason is predictability... since you don't know what

[jira] Commented: (LUCENE-821) single norm file still uses up descriptors

[ https://issues.apache.org/jira/browse/LUCENE-821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477761 ] Doron Cohen commented on LUCENE-821: wow.. I totally missed this point in 756. Fix here seems perfect to me

[jira] Resolved: (LUCENE-820) SegmentReader.setNorm can fail to remove separate norms file, on Windows

[ https://issues.apache.org/jira/browse/LUCENE-820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-820. --- Resolution: Fixed This root cause of this bug was already fixed by LUCENE-821

[jira] Updated: (LUCENE-823) Lucene fails to close file handles under certain situations

[ https://issues.apache.org/jira/browse/LUCENE-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-823: -- Attachment: LUCENE-823.patch Lucene fails to close file handles under certain

[jira] Created: (LUCENE-823) Lucene fails to close file handles under certain situations

Lucene fails to close file handles under certain situations --- Key: LUCENE-823 URL: https://issues.apache.org/jira/browse/LUCENE-823 Project: Lucene - Java Issue Type: Bug

[jira] Updated: (LUCENE-818) IndexWriter should detect when it's used after being closed

[ https://issues.apache.org/jira/browse/LUCENE-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-818: -- Attachment: LUCENE-818.take3.patch Attached take3, which just removes ensureOpen()

Could you make lucene classes reusable?

Hi, I'm doing some development using lucene and I've found that some classes that I could reuse (e.g. TopDocs, Hits) have package level constractor. Is it really necessary? I'm forced to repeat their functionality but I don't want to. -- Dmitri. -- View this message in context:

[jira] Commented: (LUCENE-778) Allow overriding a Document

[ https://issues.apache.org/jira/browse/LUCENE-778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_1243 ] Nicolas Lalevée commented on LUCENE-778: Marker interface is a nice idea, but I think this will make

[jira] Commented: (LUCENE-662) Extendable writer and reader of field data

[ https://issues.apache.org/jira/browse/LUCENE-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_1244 ] Nicolas Lalevée commented on LUCENE-662: Thanks Michael ! I will appreciate a review and feedbacks, as it

Re: Could you make lucene classes reusable?

4 mar 2007 kl. 11.40 skrev dmitri: I'm doing some development using lucene and I've found that some classes that I could reuse (e.g. TopDocs, Hits) have package level constractor. Is it really necessary? I'm forced to repeat their functionality but I don't want to. What do you mean by

[jira] Commented: (LUCENE-823) Lucene fails to close file handles under certain situations

[ https://issues.apache.org/jira/browse/LUCENE-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477791 ] Yonik Seeley commented on LUCENE-823: - TermInfosReader.close() was setting its ThreadLocal enumerators to

Re: [jira] Question about hits scores

1) questions about using Lucene are best sent to the java-user list ... it is for people asking questions about using the java lucene library (java-dev is for quesions about developing the java lucene library) ... you are more likley to get answers to questions faster on the java-user list. 2)

[jira] Commented: (LUCENE-823) Lucene fails to close file handles under certain situations

[ https://issues.apache.org/jira/browse/LUCENE-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477852 ] Michael McCandless commented on LUCENE-823: --- Ahh, tricky! You are right, this is not a real leak, since

[jira] Commented: (LUCENE-823) Lucene fails to close file handles under certain situations

[ https://issues.apache.org/jira/browse/LUCENE-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477855 ] Yonik Seeley commented on LUCENE-823: - guess I'll leave the close in there Since it's a thread-local, that

[jira] Commented: (LUCENE-823) Lucene fails to close file handles under certain situations

[ https://issues.apache.org/jira/browse/LUCENE-823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477861 ] Michael McCandless commented on LUCENE-823: --- Since it's a thread-local, that only closes (maybe) for a

[jira] Updated: (LUCENE-823) Lucene fails to close file handles under certain situations

[ https://issues.apache.org/jira/browse/LUCENE-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-823: -- Attachment: LUCENE-823.take2.patch Fixed patch based on Yonik's comments (thanks for

[jira] Commented: (LUCENE-818) IndexWriter should detect when it's used after being closed

[ https://issues.apache.org/jira/browse/LUCENE-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477875 ] Hoss Man commented on LUCENE-818: - I havne't been following this issue that closely, and i haven't read any of the

[jira] Commented: (LUCENE-814) javacc on Win32 (cygwin) creates wrong line endings - fix them with 'ant replace'

[ https://issues.apache.org/jira/browse/LUCENE-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477876 ] Hoss Man commented on LUCENE-814: - Doron: if you are seeing problems with the modified selector, it may be because

[jira] Commented: (LUCENE-778) Allow overriding a Document

[ https://issues.apache.org/jira/browse/LUCENE-778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477880 ] Hoss Man commented on LUCENE-778: - 1) from a design standpoint, as long as IndexReader/IndexSearcher deal with

Build failed in Hudson: Lucene-Nightly #13

See http://lucene.zones.apache.org:8080/hudson/job/Lucene-Nightly/13/ -- [...truncated 192 lines...] A contrib/gdata-server/src/gom/src/test/org/apache/lucene/gdata/gom/core/GOMDocumentImplTest.java A

Re: commited docs vs wiki -- was: Re: [jira] Commented: (LUCENE-805) New Lucene Demo

Anyone know how we change this so that change notifications go to the commits list? Perhaps whomever is responsible for the wiki??? could update the committers section of the wiki with information about who is responsible for the wiki and what that means? :-) FYI: I haven't heard much

Patch Check List

Hey Committers (and contributors), I started http://wiki.apache.org/jakarta-lucene/PatchCheckList under the Committer Resources with a number of tips, etc. related to applying patches. Please edit as appropriate. This is just a little bit of a brain dump as I work on a patch. Thought it

[jira] Commented: (LUCENE-814) javacc on Win32 (cygwin) creates wrong line endings - fix them with 'ant replace'

[ https://issues.apache.org/jira/browse/LUCENE-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477919 ] Doron Cohen commented on LUCENE-814: The modified selector worked ok with the default cache file, so I thught