[
https://issues.apache.org/jira/browse/ACCUMULO-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13669762#comment-13669762
]
John Vines commented on ACCUMULO-1471:
--------------------------------------
But I think SortedMapIterator should be treated just like an RFileReader. It is
the MockAccumulo equivalent after all. Sure, there currently are no
optimizations for it (but there could be by implementing locality groups via
multimaps).
I mean, the fundamental problem I think, is that there are portions of the
iterator arguments that are not part of each iterator's contract, but rather an
option that is known to be used SOMEWHERE in the stack. We are not clear on
this behavior, but it's something that had been brought up in the work for
ACCUMULO-652 because that brings in further options. I just remember the column
families between strange because they get used in multiple places in the stack.
> SortedMapIterator.seek() doesn't respect columnFamilies
> -------------------------------------------------------
>
> Key: ACCUMULO-1471
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1471
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.3, 1.5.0
> Reporter: Michael Berman
> Assignee: Michael Berman
> Priority: Minor
> Fix For: 1.5.1, 1.6.0
>
>
> If you specify columnFamilies in a seek() on a SortedMapIterator, it will
> happily return results from other column families. The arguments are never
> even read.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
