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" <[email protected]> wrote:
> Can an iterator check a table-specific configuration value? > > > On Tue, Apr 8, 2014 at 10:38 AM, Christopher <[email protected]> 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 <[email protected]> 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 >> > >
