Dawid Weiss created LUCENE-7706:
-----------------------------------

             Summary: Make MergeScheduler.clone() abstract or drop it entirely?
                 Key: LUCENE-7706
                 URL: https://issues.apache.org/jira/browse/LUCENE-7706
             Project: Lucene - Core
          Issue Type: Task
            Reporter: Dawid Weiss
            Assignee: Dawid Weiss
            Priority: Trivial
             Fix For: master (7.0)


I didn't look too closely, but MergeScheduler has this piece of documentation:
{code}
 *  <p>Implementers of sub-classes should make sure that {@link #clone()}
 *  returns an independent instance able to work with any {@link IndexWriter}
 *  instance.</p>
{code}

Now, we don't seem to be using this at all... I think. MergeScheduler doesn't 
even implement Cloneable. But in any case, I think it'd be better to provide an 
abstract covariant of this sort:

{code}
public abstract MergeScheduler clone() {
  return this;
}
{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to