lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (JIRA)" <>
Subject [jira] [Commented] (LUCENE-8331) MergePolicy simulator utility
Date Tue, 29 May 2018 12:33:00 GMT


David Smiley commented on LUCENE-8331:

bq. can it just be a utility class that I call from a test or so I mean I am not sure how
userfriendly it is to specify classpaths etc. I'd just run it from a test.

Ooh, ok.  FWIW what I do is simply right-click the main method and tell my IDE to run it.
 It fails the first go-round because it needs args so then I update the args.  Since it's
on the test classpath and run from my IDE, there's no issue.  I expect others can just run
it similarly?  Documentation could spell this out!  Why would a test call this?  To assert
that the stats are "good"?

{quote}I think it should support deletes and should not use IW then I ok with it
Sure thing – now made possible with LUCENE-8330.  I'll work on this.

> MergePolicy simulator utility
> -----------------------------
>                 Key: LUCENE-8331
>                 URL:
>             Project: Lucene - Core
>          Issue Type: New Feature
>            Reporter: David Smiley
>            Assignee: David Smiley
>            Priority: Major
>         Attachments: LUCENE-8331.patch
> This issue introduces a MergePolicy simulator utility to help evaluate the effectiveness
of a MergePolicy.  The simulator does not result in the actual indexing and merging of segments;
instead it provides some dummy constructs to MergePolicy to evaluate its decisions.  Therefore
you can do simulation runs in little time.
> I'm not sure where it would live.  Perhaps dev-tools, or in tests, or in benchmark?
> I mentioned this recently here:

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message