Re: [jira] Created: (LUCENE-854) Create merge policy that doesn't periodically inadvertently optimize

2007-05-11 Thread Michael McCandless
Yonik Seeley [EMAIL PROTECTED] wrote: On 5/2/07, Michael McCandless [EMAIL PROTECTED] wrote: It would merge based on size (not # docs), would be free to merge adjacent segments (not just rightmost segments), and would merge N (configurable) at a time. Hopefully it will always be easy to

Re: [jira] Created: (LUCENE-854) Create merge policy that doesn't periodically inadvertently optimize

2007-05-11 Thread Michael McCandless
Yonik Seeley [EMAIL PROTECTED] wrote: On 5/3/07, Michael McCandless [EMAIL PROTECTED] wrote: I like your idea to keep delete count per segment in the segments file. This information is certainly useful to the merge policy because it should proportionally reducde a segments size according

Re: [jira] Created: (LUCENE-854) Create merge policy that doesn't periodically inadvertently optimize

2007-05-09 Thread Yonik Seeley
On 5/3/07, Michael McCandless [EMAIL PROTECTED] wrote: I like your idea to keep delete count per segment in the segments file. This information is certainly useful to the merge policy because it should proportionally reducde a segments size according to what %tg of its docs are deleted, and, it

Re: [jira] Created: (LUCENE-854) Create merge policy that doesn't periodically inadvertently optimize

2007-05-09 Thread Yonik Seeley
On 5/2/07, Michael McCandless [EMAIL PROTECTED] wrote: It would merge based on size (not # docs), would be free to merge adjacent segments (not just rightmost segments), and would merge N (configurable) at a time. Hopefully it will always be easy to switch the meaning of size so it could be in

Re: [jira] Created: (LUCENE-854) Create merge policy that doesn't periodically inadvertently optimize

2007-05-03 Thread Michael McCandless
Ning Li [EMAIL PROTECTED] wrote: It would merge based on size (not # docs), would be free to merge adjacent segments (not just rightmost segments), and would merge N (configurable) at a time. The part that's still unclear is how it chooses when to trigger a merge and how specifically it

Re: [jira] Created: (LUCENE-854) Create merge policy that doesn't periodically inadvertently optimize

2007-05-02 Thread Ning Li
On 3/31/07, Michael McCandless (JIRA) [EMAIL PROTECTED] wrote: Create merge policy that doesn't periodically inadvertently optimize So we could make a small change to the policy by only merging the first mergeFactor segments

RE: [jira] Created: (LUCENE-854) Create merge policy that doesn't periodically inadvertently optimize

2007-05-02 Thread Steven Parkes
, 2007 6:57 AM To: java-dev@lucene.apache.org Subject: Re: [jira] Created: (LUCENE-854) Create merge policy that doesn't periodically inadvertently optimize On 3/31/07, Michael McCandless (JIRA) [EMAIL PROTECTED] wrote: Create merge policy that doesn't periodically inadvertently optimize

Re: [jira] Created: (LUCENE-854) Create merge policy that doesn't periodically inadvertently optimize

2007-05-02 Thread Michael McCandless
Ning Li [EMAIL PROTECTED] wrote: On 3/31/07, Michael McCandless (JIRA) [EMAIL PROTECTED] wrote: Create merge policy that doesn't periodically inadvertently optimize So we could make a small change to the policy by only

[jira] Created: (LUCENE-854) Create merge policy that doesn't periodically inadvertently optimize

2007-03-31 Thread Michael McCandless (JIRA)
Create merge policy that doesn't periodically inadvertently optimize Key: LUCENE-854 URL: https://issues.apache.org/jira/browse/LUCENE-854 Project: Lucene - Java Issue