I'm torn. MergePolicy (and MergeScheduler) are "expected" to be something expert users could alter; their API is designed to be exposed & stable. I think they should be visilbe in the javadocs.
But, unfortunately, to do their job they must use other package private APIs (SegmentInfos) which we intentionally would like to keep more malleable. Is there some way to make them package private, yet include them (and only them, ie not all package private classes) in the javadocs? At a minimum we should update the javadocs expressing this issue. Mike Chris Hostetter <hossman_luc...@fucit.org> wrote: > > : I'd rather not make SegmentInfos public; it's a large API and we do > : make changes to it as we change the index format. It's also quite > : internal to Lucene. > : > : Making your own MergePolicy/Scheduler is very much an "advanced" use > : case... so I think it's acceptable to have to put it into o.a.l.index > : package? > > i don't know enough aboutthe APIs involved to have an opinion on this, but > your comments lead me to conclude: if we assume subclassing MergePolicy is > so advanced that you should only do it in the o.a.l.index package, then > shouldn't MergePolicy itself be pacakge protected? > > > > -Hoss > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
