[
https://issues.apache.org/jira/browse/ACCUMULO-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161245#comment-13161245
]
Eric Newton commented on ACCUMULO-200:
--------------------------------------
+1
> Undefined behavior when adding an iterator that conflicts with existing
> iterators
> ---------------------------------------------------------------------------------
>
> Key: ACCUMULO-200
> URL: https://issues.apache.org/jira/browse/ACCUMULO-200
> Project: Accumulo
> Issue Type: Task
> Components: client
> Affects Versions: 1.3.5
> Reporter: Billie Rinaldi
> Assignee: Billie Rinaldi
> Labels: iterator
> Fix For: 1.4.0
>
>
> There are two ways for an iterator configuration to conflict with the
> existing configuration: in the distinguishing name of the iterator, and in
> the priority of the iterator. I propose throwing an exception when either of
> these conflicts occurs, allowing the user to remove the conflicting iterators
> or to change the configuration of the new iterator, then to try again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
