[
https://issues.apache.org/jira/browse/KUDU-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004113#comment-16004113
]
Dan Burkert commented on KUDU-1993:
-----------------------------------
Changing the fix version to 1.3.2, since I don't think this made the cutoff for
1.3.1.
> The validation of 'grouped' flags works incorrectly if flags re-ordered
> -----------------------------------------------------------------------
>
> Key: KUDU-1993
> URL: https://issues.apache.org/jira/browse/KUDU-1993
> Project: Kudu
> Issue Type: Bug
> Components: master, tserver
> Affects Versions: 1.3.0, 1.3.1
> Reporter: Alexey Serbin
> Assignee: Alexey Serbin
> Fix For: 1.3.1, 1.4.0
>
>
> To illustrate the issue, run with the following order of the
> {{webserver_certificate_file,webserver_private_key_file}} grouped flags:
> {noformat}
> ./bin/kudu-tserver --webserver_certificate_file=/tmp/x.pem
> --webserver_private_key_file=/tmp/y.pem
> WARNING: Logging before InitGoogleLogging() is written to STDERR
> E0503 18:43:23.122520 21873 webserver_options.cc:93]
> --webserver_certificate_file and --webserver_private_key_file must be set as
> a group
> E0503 18:43:23.122825 21873 webserver_options.cc:93]
> --webserver_certificate_file and --webserver_private_key_file must be set as
> a group
> ERROR: failed validation of new value '/tmp/y.pem' for flag
> 'webserver_private_key_file'
> {noformat}
> Specifying the flags in different order passes the validation with no issues.
> The problem happens because a gflag validator is fired upon parsing
> particular flag, but since current 'group' flags validators assume the
> counterpart flags have already been parsed and set, it depends on the order
> of the flags in the command line.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
