[ https://issues.apache.org/jira/browse/KUDU-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Serbin resolved KUDU-1621. --------------------------------- Fix Version/s: n/a Resolution: Won't Fix Automatically flushing data in the {{KuduSession}} might block, indeed. It seems the current approach of issuing a warning when data is not flushed is good enough: it's uniform across all flush modes and avoids application hanging on close. > Flush lingering operations upon destruction of an 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 > Priority: Major > Fix For: n/a > > > 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 (v8.3.4#803005)