[
https://issues.apache.org/jira/browse/KUDU-3757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Serbin updated KUDU-3757:
--------------------------------
Code Review: https://gerrit.cloudera.org/#/c/24151/
> Allow specifying an experimental flag set to default value without requiring
> --unlock_experimental_flags
> --------------------------------------------------------------------------------------------------------
>
> Key: KUDU-3757
> URL: https://issues.apache.org/jira/browse/KUDU-3757
> Project: Kudu
> Issue Type: Improvement
> Components: CLI, master, tserver
> Reporter: Alexey Serbin
> Assignee: Alexey Serbin
> Priority: Major
>
> It turns out that adding 'experimental' or 'unsafe' flag to an already
> existing flag leads to unexpected results when the flag was used with its
> default (in most cases safe and tested) value. E.g., that happened to the
> '\-\-use_hybrid_clock' flag
> [1|https://github.com/apache/kudu/commit/27ac60210]: if specifying
> '\-\-use_hybrid_clock=true', it's necessary to also specify
> '\-\-unlock_unsafe_flags' [2|https://github.com/apache/kudu/commit/ab974c7da]
> Since the idea behind locking 'experimental' and 'unsafe' flags was to warn
> users when they override the safe and tested default values, it makes sense
> to issue the warning and/or exit on flag validation only if the custom
> setting deviates from the default value for such flags.
> [1] https://github.com/apache/kudu/commit/27ac60210
> [2] https://github.com/apache/kudu/commit/ab974c7da
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
