You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Andrew Wong (Jira)" <ji...@apache.org> on 2020/06/01 19:14:00 UTC
[jira] [Commented] (IMPALA-7184) Support Kudu's READ_YOUR_WRITES
scan mode
[ https://issues.apache.org/jira/browse/IMPALA-7184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121264#comment-17121264 ]
Andrew Wong commented on IMPALA-7184:
-------------------------------------
[~twmarshall] sorry for not responding earlier. Yeah, based on the current behavior, seems that is the expectation, which seems similar to the semantics of passing around propagated timestamps from writes. FWIW, the default ancient history has been set to 7 days in recent releases.
I filed KUDU-3137 to improve the existing behavior to account for shorter AHM intervals though.
> Support Kudu's READ_YOUR_WRITES scan mode
> -----------------------------------------
>
> Key: IMPALA-7184
> URL: https://issues.apache.org/jira/browse/IMPALA-7184
> Project: IMPALA
> Issue Type: Improvement
> Reporter: Thomas Tauber-Marshall
> Assignee: Thomas Tauber-Marshall
> Priority: Major
> Labels: kudu
>
> Kudu recently added a new scan mode called READ_YOUR_WRITES which provides better consistency guarantees than READ_LATEST or READ_AT_SNAPSHOT, the options currently supported by Impala.
> Unfortunately, READ_YOUR_WRITES is currently affected by a bug that makes it unusable by Impala (KUDU-2233). Once this is fixed, we should add support for it, and consider either setting it as the default, or at least using it in tests, see the discussion in https://gerrit.cloudera.org/#/c/10503/
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org