[GitHub] [hadoop-ozone] bharatviswa504 commented on issue #108: HDDS-1987. Fix listStatus API

[GitBox <gi...@apache.org>]

bharatviswa504 commented on issue #108: HDDS-1987. Fix listStatus API
URL: https://github.com/apache/hadoop-ozone/pull/108#issuecomment-557262889
 
 
   In non-HA, until we flush to DB, we don't return the result. And after that, any list operation performed should return correct values, till that moment, as key delete/create happen in parallel is not a guarranty it is provided by this API.
   
   > A generational stamp (shared between cache and DB) could fix this. (Do we have it? I think not? We have epoch in TableCache entries but I don't think that value is shared with the DB? @bharatviswa504 )
   > 
   > But if we don't have such gen stamp, time stamp could also work? If the time stamp of the DB entry is newer than the one in the cache, we then know the key in DB is created after the key deletion.
   > 
   
   Yes, we can check the timestamp that is a good idea, that should work. But unfortunately, when the key is marked for delete, we make that value null, we have not set the timestamp of key deleted.

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org