lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Willnauer (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3084) MergePolicy.OneMerge.segments should be List<SegmentInfo> not SegmentInfos
Date Thu, 12 May 2011 07:41:47 GMT


Simon Willnauer commented on LUCENE-3084:

bq. NavigableSet ist Java 6. SortedSet only works if the set ordering is defined by its contents
fair enough. I still think we can make it SortedSet as we know the ordering otherwise we could
not build the list right?

for now I think we should implement Iterable<SI> and offer a method List<SI> asList()
to make it consistent with FIS and Document (conclusion from the discussion with uwe on IRC).

Eventually I would prefer having a set here really.

> MergePolicy.OneMerge.segments should be List<SegmentInfo> not SegmentInfos
> --------------------------------------------------------------------------
>                 Key: LUCENE-3084
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>            Priority: Minor
>             Fix For: 3.2, 4.0
>         Attachments: LUCENE-3084-trunk-only.patch, LUCENE-3084-trunk-only.patch, LUCENE-3084.patch
> SegmentInfos carries a bunch of fields beyond the list of SI, but for merging purposes
these fields are unused.
> We should cutover to List<SI> instead.

This message is automatically generated by JIRA.
For more information on JIRA, see:

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

View raw message