Grant Henke has posted comments on this change. ( http://gerrit.cloudera.org:8080/12327 )
Change subject: KUDU-2677 Implement new gflag for backup history retention ...................................................................... Patch Set 2: (1 comment) http://gerrit.cloudera.org:8080/#/c/12327/2//COMMIT_MSG Commit Message: http://gerrit.cloudera.org:8080/#/c/12327/2//COMMIT_MSG@16 PS2, Line 16: users can just raise the : new flag, and ideally we will keep the semantics of "I want to be able : to back up to this point" in future releases, minimizing user-end : configuration changes. > I feel like I never really understood this argument, but maybe that's becau The primary difference is that a new flag doesn't need to be stable. Additionally the new flag implies some "functional" capability, that may change semantics in the future. With a new flag we don't need to ask users to change the value of a stable flag for an unstable feature. It gives us the flexibility to re-purpose the flag in the future while maintaining the same functional promise or drop it all together when a new mechanism for anchoring is introduced. -- To view, visit http://gerrit.cloudera.org:8080/12327 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-Project: kudu Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: Id6c2c001c50f65e9acdfc032e8aa5efdacbd4d9e Gerrit-Change-Number: 12327 Gerrit-PatchSet: 2 Gerrit-Owner: Will Berkeley <[email protected]> Gerrit-Reviewer: Adar Dembo <[email protected]> Gerrit-Reviewer: Grant Henke <[email protected]> Gerrit-Reviewer: Kudu Jenkins (120) Gerrit-Reviewer: Mike Percy <[email protected]> Gerrit-Comment-Date: Mon, 04 Feb 2019 21:00:52 +0000 Gerrit-HasComments: Yes
