Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Sat, 4 Jan 2014 22:34:50 +0000 (UTC)
From: "Josh Elser (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12646938.1368150912105.43780.1388874890808@arcas>
In-Reply-To: <JIRA.12646938.1368150912105@arcas>
References: <JIRA.12646938.1368150912105@arcas>
Subject: [jira] [Resolved] (ACCUMULO-1403) setiter fails when given a
 sortedkeyvalueiterator
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/ACCUMULO-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Elser resolved ACCUMULO-1403.
----------------------------------

    Resolution: Fixed

Happy to get this one crossed off as it's been a long-standing gripe.

{{setiter}} can now take a SortedKeyValueIterator and will prompt for a name (but using the value from the -name option when present) and will prompt for key-value pairs in the same manner that setiter does for the OptionDescriber.

These changes *do not* affect how classes which implement OptionDescriber are handled.


> setiter fails when given a sortedkeyvalueiterator
> -------------------------------------------------
>
>                 Key: ACCUMULO-1403
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1403
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: Mike Drob
>            Assignee: Josh Elser
>             Fix For: 1.6.0
>
>
> When providing a class that implements SortedKeyValueIterator, but not OptionDescriber, to setiter, the command fails. 
> For example, the following command fails:
> {noformat}
> setiter -class org.apache.accumulo.core.iterators.ColumnFamilyCounter -p 1
> {noformat}
> More reasonable behaviour might be to set the iterator without needing the user to input extra options. 


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)