accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-626) create an iterator fuzz tester
Date Thu, 10 Dec 2015 04:25:11 GMT


ASF GitHub Bot commented on ACCUMULO-626:

Github user joshelser commented on the pull request:
    Rebased on top of master and addressed the current comments:
    * Removed Reflections dependency
    * Reuse Key/Value in the test iterator stack
    * New deepCopy test that iterates over multiple copies.
    * More accurate re-seek test case.
    Only outstanding thing I want to do before an initial commit is to run all of the iterators
in {{o.a.a.c.iterators}} through this framework in accumulo-test (start the dog-fooding).
    Keith had some suggestions about fancier testing (iterator stacks, compaction/scopes,
and delete keys), which I'm not sure I want to try to solve right away. I feel like I've let
these changes sit for far too long already. I'd be happy to wait if anyone else is interested
in working on it short-term, though.

> create an iterator fuzz tester
> ------------------------------
>                 Key: ACCUMULO-626
>                 URL:
>             Project: Accumulo
>          Issue Type: New Feature
>          Components: test
>            Reporter: Eric Newton
>            Assignee: Josh Elser
> Users often write iterators without fully understanding its limits and lifetime. Accumulo
should have an iterator fuzz-tester which will take user data and run the iterator under extreme
conditions.  For example, it should re-create and re-seek the iterator with every key returned.
 It could automatically compare results of such a run with the naive run, which seeks to the
beginning and scans all the data.

This message was sent by Atlassian JIRA

View raw message