[jira] Resolved: (LUCENE-871) ISOLatin1AccentFilter a bit slow

[ https://issues.apache.org/jira/browse/LUCENE-871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-871. --- Resolution: Duplicate Fix Version/s: 2.3 Lucene Fields: [New, Patch Availab

[jira] Commented: (LUCENE-845) If you "flush by RAM usage" then IndexWriter may over-merge

[ https://issues.apache.org/jira/browse/LUCENE-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520181 ] Michael McCandless commented on LUCENE-845: --- > This increases file descriptor usage in some cases, right?

[jira] Created: (LUCENE-982) Create new method optimize(int maxNumSegments) in IndexWriter

Create new method optimize(int maxNumSegments) in IndexWriter - Key: LUCENE-982 URL: https://issues.apache.org/jira/browse/LUCENE-982 Project: Lucene - Java Issue Type: Improvement

[jira] Commented: (LUCENE-871) ISOLatin1AccentFilter a bit slow

[ https://issues.apache.org/jira/browse/LUCENE-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520234 ] Mark Miller commented on LUCENE-871: Pretty sure you still want this guys patch. It avoids a slow StringBuffer an

[jira] Commented: (LUCENE-847) Factor merge policy out of IndexWriter

[ https://issues.apache.org/jira/browse/LUCENE-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520260 ] Michael McCandless commented on LUCENE-847: --- One new small item: you've added a "public void merge()" to In

[jira] Commented: (LUCENE-871) ISOLatin1AccentFilter a bit slow

[ https://issues.apache.org/jira/browse/LUCENE-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520262 ] Michael McCandless commented on LUCENE-871: --- Ahh, OK, thanks. I will re-open and merge in the fail-fast pa

[jira] Reopened: (LUCENE-871) ISOLatin1AccentFilter a bit slow

[ https://issues.apache.org/jira/browse/LUCENE-871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless reopened LUCENE-871: --- Assignee: Michael McCandless Lucene Fields: [New, Patch Available] (was: [Pa

[jira] Updated: (LUCENE-978) GC resources in TermInfosReader when exception occurs in its constructor

[ https://issues.apache.org/jira/browse/LUCENE-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ning Li updated LUCENE-978: --- Lucene Fields: [Patch Available] (was: [New]) > GC resources in TermInfosReader when exception occurs in its

[jira] Commented: (LUCENE-845) If you "flush by RAM usage" then IndexWriter may over-merge

[ https://issues.apache.org/jira/browse/LUCENE-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520268 ] Steven Parkes commented on LUCENE-845: -- I understand the merge problem but I'm still concerned about the increas

[jira] Commented: (LUCENE-978) GC resources in TermInfosReader when exception occurs in its constructor

[ https://issues.apache.org/jira/browse/LUCENE-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520269 ] Yonik Seeley commented on LUCENE-978: - Nice catch! fix looks good to me. > GC resources in TermInfosReader whe

[jira] Commented: (LUCENE-845) If you "flush by RAM usage" then IndexWriter may over-merge

[ https://issues.apache.org/jira/browse/LUCENE-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520271 ] Yonik Seeley commented on LUCENE-845: - Is there a change in filedescriptor use if you don't use setRamBufferSizeM

[jira] Commented: (LUCENE-978) GC resources in TermInfosReader when exception occurs in its constructor

[ https://issues.apache.org/jira/browse/LUCENE-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520273 ] Michael McCandless commented on LUCENE-978: --- Agreed. Actually, it also looks like we need to do something

[jira] Commented: (LUCENE-982) Create new method optimize(int maxNumSegments) in IndexWriter

[ https://issues.apache.org/jira/browse/LUCENE-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520280 ] Yonik Seeley commented on LUCENE-982: - +1 sounds like a great idea. > Create new method optimize(int maxNumSegm

[jira] Commented: (LUCENE-978) GC resources in TermInfosReader when exception occurs in its constructor

[ https://issues.apache.org/jira/browse/LUCENE-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520286 ] Ning Li commented on LUCENE-978: > Agreed. Actually, it also looks like we need to do something similar for > Fields

[jira] Commented: (LUCENE-847) Factor merge policy out of IndexWriter

[ https://issues.apache.org/jira/browse/LUCENE-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520293 ] Steven Parkes commented on LUCENE-847: -- One new small item: you've added a "public void merge()" to

[jira] Commented: (LUCENE-845) If you "flush by RAM usage" then IndexWriter may over-merge

[ https://issues.apache.org/jira/browse/LUCENE-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520328 ] Michael McCandless commented on LUCENE-845: --- > Is there a change in filedescriptor use if you don't use se

[jira] Updated: (LUCENE-978) GC resources in TermInfosReader when exception occurs in its constructor

[ https://issues.apache.org/jira/browse/LUCENE-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ning Li updated LUCENE-978: --- Attachment: Readers.patch Similar fixes are added for FieldsReader and TermVectorsReader as well. > GC resou

[jira] Commented: (LUCENE-845) If you "flush by RAM usage" then IndexWriter may over-merge

[ https://issues.apache.org/jira/browse/LUCENE-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520334 ] Yonik Seeley commented on LUCENE-845: - You may avoid the cost of a bunch of small merges, but then you pay the pr

[jira] Commented: (LUCENE-845) If you "flush by RAM usage" then IndexWriter may over-merge

[ https://issues.apache.org/jira/browse/LUCENE-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520336 ] Steven Parkes commented on LUCENE-845: -- Here's an idea: maybe we can accept the O(N^2) merge cost, when

[jira] Commented: (LUCENE-845) If you "flush by RAM usage" then IndexWriter may over-merge

[ https://issues.apache.org/jira/browse/LUCENE-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520344 ] Michael McCandless commented on LUCENE-845: --- > > Here's an idea: maybe we can accept the O(N^2) merge cost,

[jira] Commented: (LUCENE-845) If you "flush by RAM usage" then IndexWriter may over-merge

[ https://issues.apache.org/jira/browse/LUCENE-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520343 ] Michael McCandless commented on LUCENE-845: --- > You may avoid the cost of a bunch of small merges, but then

[jira] Commented: (LUCENE-845) If you "flush by RAM usage" then IndexWriter may over-merge

[ https://issues.apache.org/jira/browse/LUCENE-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520351 ] Michael McCandless commented on LUCENE-845: --- > Or here's another random idea: maybe IndexReaders should loa

[jira] Commented: (LUCENE-845) If you "flush by RAM usage" then IndexWriter may over-merge

[ https://issues.apache.org/jira/browse/LUCENE-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520360 ] Steven Parkes commented on LUCENE-845: -- I think the combination of these two changes should give a net/n

[jira] Commented: (LUCENE-847) Factor merge policy out of IndexWriter

[ https://issues.apache.org/jira/browse/LUCENE-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520374 ] Michael McCandless commented on LUCENE-847: --- > Note that merge() was added not for users (which I have no s

[jira] Commented: (LUCENE-845) If you "flush by RAM usage" then IndexWriter may over-merge

[ https://issues.apache.org/jira/browse/LUCENE-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520378 ] Michael McCandless commented on LUCENE-845: --- > I think this would be great. It's always been a pet peeve of

[jira] Created: (LUCENE-983) Enable IndexReader to merge tail segments on demand, in RAM, when opening

Enable IndexReader to merge tail segments on demand, in RAM, when opening - Key: LUCENE-983 URL: https://issues.apache.org/jira/browse/LUCENE-983 Project: Lucene - Java

[jira] Updated: (LUCENE-871) ISOLatin1AccentFilter a bit slow

[ https://issues.apache.org/jira/browse/LUCENE-871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-871: -- Attachment: LUCENE-871.take4.patch OK I merged the original patch with my commit from L

[jira] Commented: (LUCENE-847) Factor merge policy out of IndexWriter

[ https://issues.apache.org/jira/browse/LUCENE-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520408 ] Steven Parkes commented on LUCENE-847: -- I don't think so: I think if someone changes the merge policy to

[jira] Updated: (LUCENE-626) Extended spell checker with phrase support and adaptive user session analysis.

[ https://issues.apache.org/jira/browse/LUCENE-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wettin updated LUCENE-626: --- Attachment: LUCENE-626_20070817.patch As the phrase-suggestion layer on top of contrib/spell in this

TermVectorsWriter and DocumentsWriter

I am trying to understand the new DocumentsWriter a bit... I am wondering if TermVectorsWriter is still used? It doesn't seem to be, at least not any of its methods (some of the constants still are, either that or my IDE is not properly finding method calls or I am too bleary-eyed at the m

[jira] Commented: (LUCENE-626) Extended spell checker with phrase support and adaptive user session analysis.

[ https://issues.apache.org/jira/browse/LUCENE-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520435 ] Karl Wettin commented on LUCENE-626: RAMDirectory vs. InstantiatedIndex as apriori index: the latter is 5 to 25

Re: variuos IndexReader methods -- was: Re: [jira] Updated: (LUCENE-832) NPE when calling isCurrent() on a ParallellReader

Chris Hostetter wrote: > > isn't segmentInfos the kind of thing that should be refactored into the > subclasses? there might be a little duplication, but it shouldn't be > significant (and it helps eliminate the odds of other problems like this > in the future as more features/methods get added).