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: Too Many Versions!
Date Thu, 13 Mar 2014 20:54:43 GMT
Instead of setting maxVersions large, it would be better to remove the
iterator from the table.  Also, iterator names are expected to be unique,
so having "vers" be the name of the default versioning iterator and your
scan versioning iterator is not recommended.  It might be possible to
override the options of an existing iterator for a particular scan.

Given your configuration, I would expect the scan time option of
maxVersions=1 to be used for both your scan time iterator and the table
iterator of the same name.

On Thu, Mar 13, 2014 at 12:43 PM, John Armstrong <jrja@ccri.com> wrote:

> On Thu 13 Mar 2014 02:59:45 PM EDT, Billie Rinaldi wrote:
>
>> When you say that you have configured your table to keep maxint versions
>> of each key, do you mean
>> that another versioning iterator already exists on the table with a
>> different number of max
>> versions?  What is the name and priority of this iterator?
>>
>
> I have the table iterator options set.  Reading from the shell:
>
> table    | table.iterator.majc.vers .................. |
> 20,org.apache.accumulo.core.iterators.user.VersioningIterator
> table    | table.iterator.majc.vers.opt.maxVersions .. | 2147483647
> table    | table.iterator.minc.vers .................. |
> 20,org.apache.accumulo.core.iterators.user.VersioningIterator
> table    | table.iterator.minc.vers.opt.maxVersions .. | 2147483647
> table    | table.iterator.scan.vers .................. |
> 20,org.apache.accumulo.core.iterators.user.VersioningIterator
> table    | table.iterator.scan.vers.opt.maxVersions .. | 2147483647
>
>

Mime
View raw message