[
https://issues.apache.org/jira/browse/ACCUMULO-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15009804#comment-15009804
]
Jonathan Park commented on ACCUMULO-3294:
-----------------------------------------
No substantial reason. My original reason was that since the method was called
"update", I added a check so that it couldn't be used like a "set". It adds a
little bit protection from surprises for clients since if I as a client (and
perhaps its just me) am trying to "update" an iterator setting, I'm assuming
that the iterator is there. If it suddenly disappears while I'm trying to
update, then perhaps something happened that means I shouldn't update. It's not
a spectacular solution to provide this protection since it's performing a
read/modify/write with no locks so the iterator could still disappear.
I don't feel too strongly about the check since there are use-cases for it not
being there so if removing the check and making this behave more like a "set"
is better aligned with other efforts, I can remove it.
What would the new interface look like if we want this to update all of a
tables iterators at once? A Collection<IteratorSettingScopePair>?
> Need mechanism to update iterator settings
> ------------------------------------------
>
> Key: ACCUMULO-3294
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3294
> Project: Accumulo
> Issue Type: Improvement
> Components: client
> Reporter: John Vines
> Assignee: Jonathan Park
> Fix For: 1.8.0
>
> Attachments: bug3294.patch, bug3294.patch.1
>
>
> Currently our API supports attachIterator, removeIterator, and
> getIteratorSettings. There is no mechanism to directly change an iterators
> settings.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
