accumulo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Billie Rinaldi <billie.rina...@gmail.com>
Subject Re: What priority for purge filter
Date Mon, 09 Dec 2013 17:25:55 GMT
In the event that the value could change (by having a new version of the
value written) in the column used to determine whether or not to keep the
row, the purge iterator should be applied after the VersioningIterator.
This means it should be given a larger priority.


On Mon, Dec 9, 2013 at 9:02 AM, Terry P. <texpilot@gmail.com> wrote:

> Greetings all,
> With Accumulo v1.4.2, we have a purge filter/iterator that extents
> RowFilter and I have a question about what priority it should be
> implemented with. I see the default VersioningIterator runs at priority 20.
>
> Our purge iterator is designed to suppress (scan time) or remove (majc or
> minc compactions) rows based on the value in a column. Is it more efficient
> to run our purge iterator at a higher priority than the VersioningIterator,
> or does it really matter? Our VersioningIterator maxVersions is set to the
> default of 1 which is what we want/need.
>
> Thanks in advance,
> Terry
>

Mime
View raw message