accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3795) flush the scan buffer if non-empty after configured timeout
Date Thu, 14 May 2015 17:56:00 GMT


Josh Elser commented on ACCUMULO-3795:

Maybe {{table.scan.max.latency}} to keep some consistency with {{table.scan.max.memory}} instead
of {{ threshold}}? We already have nice parsing for {{TimeDuration}} in
{{Property}}s. Don't need to specifically set ms.

Sounds like a good addition though.

> flush the scan buffer if non-empty after configured timeout
> -----------------------------------------------------------
>                 Key: ACCUMULO-3795
>                 URL:
>             Project: Accumulo
>          Issue Type: New Feature
>          Components: tserver
>    Affects Versions: 1.6.2
>            Reporter: Ivan Bella
>            Assignee: Eric Newton
>             Fix For: 1.8.0
> 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  Note that the buffer would only be flushed (i.e. returned
to the client) iff it is non-empty, and the threshold has been reached
since the beginning of the nextBatch call in

This message was sent by Atlassian JIRA

View raw message