[
https://issues.apache.org/jira/browse/ACCUMULO-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161148#comment-13161148
]
Billie Rinaldi commented on ACCUMULO-197:
-----------------------------------------
Good point. Actually, it looks like a Mutation can hold two identical keys,
but one of them gets removed when they are inserted into the in-memory map.
Also, two identical keys inserted in different mutations will be considered
different keys and both will appear in the in-memory map.
> remove the VersioningIterator: inserting duplicate keys gives duplicate keys
> on scan
> ------------------------------------------------------------------------------------
>
> Key: ACCUMULO-197
> URL: https://issues.apache.org/jira/browse/ACCUMULO-197
> Project: Accumulo
> Issue Type: Bug
> Components: tserver
> Reporter: Eric Newton
> Assignee: Keith Turner
>
> {noformat}
> root@test> createtable t
> root@test t> deleteiter -minc -majc -scan -n vers
> root@test t> insert a b c v -t 123
> root@test t> insert a b c v2 -t 123
> root@test t> scan -st
> a b:c [] 123 v2
> a b:c [] 123 v
> root@test t>
> {noformat}
> I expect that we would return only one value, although probably not
> deterministically. We need to define what accumulo *should* do in this case.
--
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
