You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Alexey Serbin (JIRA)" <ji...@apache.org> on 2016/09/16 02:15:20 UTC

[jira] [Updated] (KUDU-1621) Flush lingering operations upon destruction of AUTO_FLUSH_BACKGROUND session

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

Alexey Serbin updated KUDU-1621:
--------------------------------
    Summary: Flush lingering operations upon destruction of AUTO_FLUSH_BACKGROUND session  (was: Flush lingering operations)

> Flush lingering operations upon destruction of AUTO_FLUSH_BACKGROUND session
> ----------------------------------------------------------------------------
>
>                 Key: KUDU-1621
>                 URL: https://issues.apache.org/jira/browse/KUDU-1621
>             Project: Kudu
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 1.0.0
>            Reporter: Alexey Serbin
>
> In current implementation of AUTO_FLUSH_BACKGROUND mode, it's necessary to call KuduSession::Flush() or KuduSession::FlushAsync() explicitly before destroying/abandoning a session if it's desired to have any pending operations flushed.
> As [~adar] noticed during review of https://gerrit.cloudera.org/#/c/4432/ , it might make sense to change this behavior to automatically flush any pending operations upon closing Kudu AUTO_FLUSH_BACKGROUND session.  That would be more consistent with the semantics of the AUTO_FLUSH_BACKGROUND mode and more user-friendly.



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