elek commented on pull request #1255:
URL: https://github.com/apache/hadoop-ozone/pull/1255#issuecomment-666323762
> The container key DB is a by product of processing the OM snapshot DB. It
hosts the reverse mapping of the OM data, the Container->Key mapping in a
specific format
Thanks to explain it. :bulb:
Now I understand, if om is time-stampe-ed, we need a same internal db.
> Based on whether we take a whole snapshot or just apply delta changes from
the OM DB, we have to create a "new" container key DB or just add more entries
to it. Hence, the "timestamp" is associated with its name
I am still not sure about this one (but as I wrote I am not familiar). In
case of a new snapshot: why don't we drop the previous one and start to use a
new one? Why do we need a new db with new timestamp? To have a backup? Or to
use the old version for some reason?
(Sorry, it's not strongly related to this patch. And wouldn't like to
challenge anything, just try to understand, for example to create a video when
I understood ;-)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
