Adar Dembo has posted comments on this change. ( http://gerrit.cloudera.org:8080/15616 )
Change subject: WIP: KUDU-3097 whether master keep record could be configurable ...................................................................... Patch Set 4: > But it would cause some inconsistent between table and tablets. Cause tablet > should be keep in memory forever in order to not overlap with previously > deleted table. > E.g table t1 with tablet uuid 1,2,3 > Then I deleted it, the tablet uuid 1,2,3 shouldn't be bind to other new table > t2,t3 ... > And also I have to handle other things like this, table not exists but tablet > still in tablet_map_. > > So if I want to implement this behave, I should handle things like this. > > Is my understand about this right? Table and tablet UUIDs are expected to be universally unique, so you don't need to preserve them in-memory just to avoid reusing them in the future. There shouldn't ever be any collisions. Furthermore, table and tablet metadata should always be consistent with one another: either both should be preserved, or both should be deleted. It'd be problematic to preserve tablet metadata while discarding table metadata. Hope this helps! -- To view, visit http://gerrit.cloudera.org:8080/15616 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-Project: kudu Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I1088080d706edadeed9d93f54704c7f4bfe2b6a2 Gerrit-Change-Number: 15616 Gerrit-PatchSet: 4 Gerrit-Owner: wangning <1994wangn...@gmail.com> Gerrit-Reviewer: Adar Dembo <a...@cloudera.com> Gerrit-Reviewer: Kudu Jenkins (120) Gerrit-Reviewer: wangning <1994wangn...@gmail.com> Gerrit-Comment-Date: Wed, 08 Apr 2020 20:29:42 +0000 Gerrit-HasComments: No
