[
https://issues.apache.org/jira/browse/ACCUMULO-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864640#comment-15864640
]
Christopher Tubbs commented on ACCUMULO-4586:
---------------------------------------------
Well, I'm not going to veto if you make the change in a patch release, but it
makes me uncomfortable changing the behavior when it seems like a valid (if
unintentional) use case. I don't see the urgency of changing it, either. It's
not exactly a critical part of of our code base. I'd be happy with a doc fix
only in a patch release, and a deprecation and enforcement via an API change in
newer versions.
Do you have any insight into whether the additional checks will affect
performance?
> Make rowiterator fail when unsorted data is observed
> ----------------------------------------------------
>
> Key: ACCUMULO-4586
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4586
> Project: Accumulo
> Issue Type: Bug
> Affects Versions: 1.6.6, 1.7.1, 1.8.0
> Reporter: Keith Turner
> Fix For: 2.0.0
>
>
> A batchscanner was used as a row iterator data source. The rowiterator
> expects data in sorted order and the batch scanner does not supply data in
> sorted order. The row iterator should have a sanity check to ensure source
> data is in sorted order.
> https://lists.apache.org/thread.html/c24448d171d8414321bccfc778c7fc8b53e45892cae9daafa220503f@%3Cuser.accumulo.apache.org%3E
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
