Move NoDeletionPolicy to core

[Shai Erera <se...@gmail.com>]

Hi

I've noticed benchmark has a NoDeletionPolicy class and I was wondering if
we can move it to core. I might want to use it for the parallel index stuff,
but I think it'll also fit nicely in core, together with the other No*
classes. In addition, this class should be made a singleton.

If moving to core is acceptable, do you think any bw policy needs to be
enforced (such as deprecating the one in benchmark and reference the one in
core? I'll also want to change the package name from o.a.l.benchmark.utils
to o.a.l.index, where the other IDPs are.

Simple move and change (and update to benchmark algs which use it.

Shai

Re: Move NoDeletionPolicy to core

[Michael McCandless <lu...@mikemccandless.com>]

+1

I don't think bw needs to be kept -- contrib/benchmark is allowed to change.

Mike

On Thu, Apr 8, 2010 at 5:44 AM, Shai Erera <se...@gmail.com> wrote:
> Hi
>
> I've noticed benchmark has a NoDeletionPolicy class and I was wondering if
> we can move it to core. I might want to use it for the parallel index stuff,
> but I think it'll also fit nicely in core, together with the other No*
> classes. In addition, this class should be made a singleton.
>
> If moving to core is acceptable, do you think any bw policy needs to be
> enforced (such as deprecating the one in benchmark and reference the one in
> core? I'll also want to change the package name from o.a.l.benchmark.utils
> to o.a.l.index, where the other IDPs are.
>
> Simple move and change (and update to benchmark algs which use it.
>
> Shai
>

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