Thank you both for your quick reply!
Responding to a few of Michael's points first:
* We actually tried the upgrade to 6.0 a few months back (when that was the
newest) and were getting similar errors to the ones I'm seeing now. We were
not able to track them down, which is part of the motivation
what decides that the segment is too big ???
I hope you don't mean the MAX_CFS_SEGMENT_SIZE
Thanks & Regards
Aravinth
On Tue, Sep 27, 2016 at 7:36 PM, Michael McCandless <
luc...@mikemccandless.com> wrote:
> One a merged segment is too big, then it will never be merged again,
> unless it
Possibly you are using an analyzer that does not preserve decimal numbers
as a single token? Or, you are using a different analyzer at indexing time
vs search time?
Can you make a small test case showing the issue?
Mike McCandless
http://blog.mikemccandless.com
On Tue, Sep 27, 2016 at 3:06
One a merged segment is too big, then it will never be merged again,
unless it accumulates > 50% deleted documents.
Mike McCandless
http://blog.mikemccandless.com
On Tue, Sep 27, 2016 at 4:03 PM, aravinth thangasami
wrote:
> Hi All,
>
> In TieredMergePolicy,
Hi All,
In TieredMergePolicy, After the sum of segments size reached the
*MaxMergedSegmentSize*
the merge will be called.
My case is,
The first merge is triggered by *MaxMergedSegmentSize.*
After that,On addition of one more segment to the index,
the sum of sizes of segments may be greater than
Please do not cross-post to multiple mailing lists.
This belongs to java-user only.
It is also generally better to describe the problem in more detail in the mail,
than attaching a zip.
- What are you indexing
- How are you searching, and what did you expect to find
- What do you actually see and
Hi,
Kindly post your suggestions..
Chitra
On Mon, Sep 26, 2016 at 3:48 PM, Chitra R wrote:
> Hi,
>
> Issues(LUCENE-4795): Add FacetsCollector based on SortedSetDocValues
>
> https://issues.apache.org/jira/browse/LUCENE-4795
>
>
> i) In the above discussion,