[
https://issues.apache.org/jira/browse/ACCUMULO-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13776734#comment-13776734
]
John Vines commented on ACCUMULO-1737:
--------------------------------------
I mean, the behavior will give you ordered batches out of order, but I don't
think that's a guaranteed behavior (hence my comment).
> MultiTableBatchScanner
> ----------------------
>
> Key: ACCUMULO-1737
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1737
> Project: Accumulo
> Issue Type: Improvement
> Components: client
> Reporter: John Vines
>
> We currently have the BatchScanner, which does not guarantee in order results
> with the benefit of higher parallellization. Unfortunately, if you want to
> query multiple tables, the only option is to chain BatchScanner's together,
> but you lose something of the optimizations under the hood for both using
> system resources well as well as getting data back in order. We have another
> ticket for multi-table accumulo input format for mapreduce, but I would like
> to see a multi table version of a batch scanner for regular client use.
--
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
