Remove iterators programmatically

[Liz Ferme <li...@gmail.com>]

Hi,

Is it possible to temporarily disable (in client code) a scan time iterator
that's been configured for a table? We want to write an iterator that's
enabled by default, but we want to give anyone writing queries the option
of disabling it for their query. There are other ways around our problem if
this isn't possible, but this way seems the most straightforward.

Thanks,
Liz

Re: Remove iterators programmatically

[Liz Ferme <li...@gmail.com>]

Thanks for the replies. I'll keep an eye on ACCUMULO-415, and in the
meantime we'll do it a different way.

Liz


On Tue, Apr 8, 2014 at 10:41 AM, Josh Elser <jo...@gmail.com> wrote:

> Hi Liz,
>
> If you've configured an iterator on a table, there presently isn't a
> way for you to not use that iterator. You'd have to manually enable
> your custom iterator when you actually want to use it.
>
> In the future, you can watch ACCUMULO-415 [1] which would likely be
> relevant for what you're asking.
>
> [1] https://issues.apache.org/jira/browse/ACCUMULO-415
>
> On Tue, Apr 8, 2014 at 10:15 AM, Liz Ferme <li...@gmail.com> wrote:
> > Hi,
> >
> > Is it possible to temporarily disable (in client code) a scan time
> iterator
> > that's been configured for a table? We want to write an iterator that's
> > enabled by default, but we want to give anyone writing queries the
> option of
> > disabling it for their query. There are other ways around our problem if
> > this isn't possible, but this way seems the most straightforward.
> >
> > Thanks,
> > Liz
>

Re: Remove iterators programmatically

[Josh Elser <jo...@gmail.com>]

Hi Liz,

If you've configured an iterator on a table, there presently isn't a
way for you to not use that iterator. You'd have to manually enable
your custom iterator when you actually want to use it.

In the future, you can watch ACCUMULO-415 [1] which would likely be
relevant for what you're asking.

[1] https://issues.apache.org/jira/browse/ACCUMULO-415

On Tue, Apr 8, 2014 at 10:15 AM, Liz Ferme <li...@gmail.com> wrote:
> Hi,
>
> Is it possible to temporarily disable (in client code) a scan time iterator
> that's been configured for a table? We want to write an iterator that's
> enabled by default, but we want to give anyone writing queries the option of
> disabling it for their query. There are other ways around our problem if
> this isn't possible, but this way seems the most straightforward.
>
> Thanks,
> Liz

Re: Remove iterators programmatically

[Christopher <ct...@apache.org>]

So, yeah. User configured iterators can override table configured ones.
That's probably a bad idea, but I suppose it does work that way now.
 On Apr 8, 2014 7:22 PM, "David Medinets" <da...@gmail.com> wrote:

> Can an iterator check a table-specific configuration value?
>
>
> On Tue, Apr 8, 2014 at 10:38 AM, Christopher <ct...@apache.org> wrote:
>
>> The intention of the configured iterators are for a table owner to
>> configure query for users. Users have the ability to specify optional
>> scan-time iterators in the client configuration when they scan.
>>
>> --
>> Christopher L Tubbs II
>> http://gravatar.com/ctubbsii
>>
>>
>> On Tue, Apr 8, 2014 at 10:15 AM, Liz Ferme <li...@gmail.com> wrote:
>> > Hi,
>> >
>> > Is it possible to temporarily disable (in client code) a scan time
>> iterator
>> > that's been configured for a table? We want to write an iterator that's
>> > enabled by default, but we want to give anyone writing queries the
>> option of
>> > disabling it for their query. There are other ways around our problem if
>> > this isn't possible, but this way seems the most straightforward.
>> >
>> > Thanks,
>> > Liz
>>
>
>

Re: Remove iterators programmatically

[David Medinets <da...@gmail.com>]

Can an iterator check a table-specific configuration value?


On Tue, Apr 8, 2014 at 10:38 AM, Christopher <ct...@apache.org> wrote:

> The intention of the configured iterators are for a table owner to
> configure query for users. Users have the ability to specify optional
> scan-time iterators in the client configuration when they scan.
>
> --
> Christopher L Tubbs II
> http://gravatar.com/ctubbsii
>
>
> On Tue, Apr 8, 2014 at 10:15 AM, Liz Ferme <li...@gmail.com> wrote:
> > Hi,
> >
> > Is it possible to temporarily disable (in client code) a scan time
> iterator
> > that's been configured for a table? We want to write an iterator that's
> > enabled by default, but we want to give anyone writing queries the
> option of
> > disabling it for their query. There are other ways around our problem if
> > this isn't possible, but this way seems the most straightforward.
> >
> > Thanks,
> > Liz
>

Re: Remove iterators programmatically

[Christopher <ct...@apache.org>]

The intention of the configured iterators are for a table owner to
configure query for users. Users have the ability to specify optional
scan-time iterators in the client configuration when they scan.

--
Christopher L Tubbs II
http://gravatar.com/ctubbsii


On Tue, Apr 8, 2014 at 10:15 AM, Liz Ferme <li...@gmail.com> wrote:
> Hi,
>
> Is it possible to temporarily disable (in client code) a scan time iterator
> that's been configured for a table? We want to write an iterator that's
> enabled by default, but we want to give anyone writing queries the option of
> disabling it for their query. There are other ways around our problem if
> this isn't possible, but this way seems the most straightforward.
>
> Thanks,
> Liz