Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Mon, 9 Nov 2015 19:28:11 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12559679.1339070749000.19076.1447097291005@Atlassian.JIRA>
In-Reply-To: <JIRA.12559679.1339070749000@Atlassian.JIRA>
References: <JIRA.12559679.1339070749000@Atlassian.JIRA>
 <JIRA.12559679.1339070749578@arcas>
Subject: [jira] [Commented] (ACCUMULO-626) create an iterator fuzz tester
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ACCUMULO-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14997200#comment-14997200 ] 

ASF GitHub Bot commented on ACCUMULO-626:
-----------------------------------------

Github user keith-turner commented on the pull request:

    https://github.com/apache/accumulo/pull/50#issuecomment-155165730
  
    There may be value in running some of these test against an iterator stack and not just a single iterator.


> create an iterator fuzz tester
> ------------------------------
>
>                 Key: ACCUMULO-626
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-626
>             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
(v6.3.4#6332)