You start by defining minimum segment size, number of segments per tier, and
maximum segment size. From that, the "budget" or maximum number of segments
allowed is calculated. Each move up a level (tier) increases the size of the
segment allowed at that next higher tier until the largest segment size is
Then the code compares the number of segments eligible for merge to that
limit. If over that limit, the code then scores each merge and selects the
merge with the best score.
-- Jack Krupansky
Sent: Tuesday, June 12, 2012 4:43 AM
Subject: problem understanding the documentation for the TieredMergePolicy
I've read the documentation about the TiredMergePolicy class. But I just
can't get behind what this sentence is trying to state:
[..] For normal merging, this policy first computes a "budget" of how
many segments are allowed by be in the index. [...]
Would somebody be so kind to explain it to me?
Thanks, thanks a lot