Thomas Tauber-Marshall created IMPALA-7186:
----------------------------------------------
Summary: Docs for kudu_read_mode
Key: IMPALA-7186
URL: https://issues.apache.org/jira/browse/IMPALA-7186
Project: IMPALA
Issue Type: Improvement
Components: Docs
Affects Versions: Impala 3.1.0
Reporter: Thomas Tauber-Marshall
IMPALA-6812 added a new query option, KUDU_READ_MODE, which should be
documented with something like:
KUDU_READ_MODE Query Option
This query option allows users to set a desired consistency level for scans of
Kudu tables. Possible values are DEFAULT, READ_LATEST, and READ_AT_SNAPSHOT. If
DEFAULT is specified, the value of the startup flag '--kudu_read_mode' will be
used.
READ_LATEST
Kudu provides no consistency guarantees for this mode, expect that all returned
rows were committed at some point, sometimes known as 'Read Committed'
isolation.
READ_AT_SNAPSHOT
Kudu will take a snapshot of the current state of the data and perform the scan
over the snapshot, possibly after briefly waiting for ongoing writes to
complete. This provides "Read Your Writes" consistency within a single Impala
session, except in the case of a Kudu leader change. See the Kudu documentation
for more details.
Type: string
Default: DEFAULT
Added in: Impala 3.1
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
