[jira] [Reopened] (ACCUMULO-3795) flush the scan buffer if non-empty after configured timeout

["Josh Elser (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ACCUMULO-3795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Elser reopened ACCUMULO-3795:
----------------------------------

This appears to be causing failures in a number of integration tests, notably ServerSideErrorIT. It looks like the Exception isn't being propagated back to the client anymore.

> flush the scan buffer if non-empty after configured timeout
> -----------------------------------------------------------
>
>                 Key: ACCUMULO-3795
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3795
>             Project: Accumulo
>          Issue Type: New Feature
>          Components: tserver
>    Affects Versions: 1.6.2
>            Reporter: Ivan Bella
>            Assignee: Eric Newton
>             Fix For: 1.8.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> For scans that may take a long time because of some underlying iterator that has to scan many keys and only returns one every so often, it would be great if we could force results to be returned to the user before the buffer has been completely filled (table.scan.max.memory).  I propose that this be time based.  Perhaps we would add a configuration property called something like table.scan.flush.ms.  Note that the buffer would only be flushed (i.e. returned to the client) iff it is non-empty, and the table.scan.flush.ms threshold has been reached since the beginning of the nextBatch call in Tablet.java.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)