accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3294) Need mechanism to update iterator settings
Date Mon, 16 Nov 2015 16:07:11 GMT


Keith Turner commented on ACCUMULO-3294:

The way sampling works in 1.8.0-SNAPSHOT is a [good example|].
 Scans will never use a tables sampling configuration directly (its only used by compactions).
 If a scan wants to use the table config, it must read the table config and pass it to the
scanner.  This has two nice properties.

 * The sampling config is consistent across the entire scan (no need to worry about scan sampling
config changing mid scan).
 * The user can verify the sampling config is as expected.   

Encouraging this pattern would be nice with iterators.   Often client side code is tightly
coupled with a set of iterators.  However when configuring table iterators, clients can not
verify (in a race condition free way) that the scan iterators are what's expected.

> Need mechanism to update iterator settings
> ------------------------------------------
>                 Key: ACCUMULO-3294
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: client
>            Reporter: John Vines
>            Assignee: Jonathan Park
>             Fix For: 1.8.0
>         Attachments: bug3294.patch, bug3294.patch.1
> Currently our API supports attachIterator, removeIterator, and getIteratorSettings. There
is no mechanism to directly change an iterators settings.

This message was sent by Atlassian JIRA

View raw message