lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-1742) Wrap SegmentInfos in public class
Date Tue, 14 Jul 2009 09:51:15 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730755#action_12730755
] 

Michael McCandless commented on LUCENE-1742:
--------------------------------------------

I agree it'd be good to do this, and this baby step (making the read-only methods public)
seems like a good start.

Would we want better names here (Segments/Segment), as Earwin suggested a while back?

Can you also mark these classes as Expert and add the "subject to change w/o warning between
releases" caveat?

> Wrap SegmentInfos in public class 
> ----------------------------------
>
>                 Key: LUCENE-1742
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1742
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Index
>    Affects Versions: 2.4.1
>            Reporter: Jason Rutherglen
>            Priority: Trivial
>             Fix For: 3.0
>
>         Attachments: LUCENE-1742.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Wrap SegmentInfos in a public class so that subclasses of MergePolicy do not need to
be in the org.apache.lucene.index package.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message