Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Sat, 7 Nov 2015 18:02:10 +0000 (UTC)
From: "Josh Elser (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12559679.1339070749000.8235.1446919330970@Atlassian.JIRA>
In-Reply-To: <JIRA.12559679.1339070749000@Atlassian.JIRA>
References: <JIRA.12559679.1339070749000@Atlassian.JIRA>
 <JIRA.12559679.1339070749578@arcas>
Subject: [jira] [Assigned] (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:all-tabpanel ]

Josh Elser reassigned ACCUMULO-626:
-----------------------------------

    Assignee: Josh Elser  (was: John Vines)

> 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)