Hi, In the context of fixing https://issues.apache.org/jira/browse/KUDU-2699, if going with the approach posted for review at https://gerrit.cloudera.org/#/c/12471/, it's necessary to adapt the command for the kudu-tidy-bot job accordingly.
One alternative is to keep the old command for the branches without that patch, but for master and newer branches use new, updated command. Probably, we would want to back-port it into 1.9.x to be along with commit 861ecc12f. The command would look like in https://gerrit.cloudera.org/#/c/12471/4//COMMIT_MSG The other alternative is suggested by Adar: let's just run the kudu-tidy-bot job against the changes in the master branch, since our development process is making the changes in the master branch and cherry-picking them into the release/maintenance branches. Personally, I prefer the latter option. What do you think? Should I go ahead with the second option or there might be some objections? Thanks, Alexey
