ArafatKhan2198 commented on PR #4245: URL: https://github.com/apache/ozone/pull/4245#issuecomment-1790152640
> Hey @ArafatKhan2198 @smengcl @dombizita: > > Last year, when @xBis7 and I implemented this for legacy buckets, we were going to do object store buckets as well. > > We didn't because @avijayanhwx (the engineer who originally created this epic), told us it would be good to support "object store prefixes", (and we didn't have time to do the extra work.) > > It looks like this PR still doesn't support them. Instead it just assigns all object store keys to the corresponding bucket. I'm fine with that, but just want to be sure that everyone understands it wasn't the initial intention. > > FYI: this is how @avijayanhwx defined the prefixes, (from an email he sent me): > > _"What I mean as object store prefix is not dissimilar to a directory in legacy FS buckets, but there is added complexity in Recon to track them since they will not be present in the OM metadata. For example, in a pure OS bucket, the rocksdb entry would be /vol1/bucket1/application1/instance1/file1. The prefixes ( /vol1/bucket1/application1 & /vol1/bucket1/application1/instance1) are not created as keys in RocksDB. We wanted to explore how to capture them and calculate summaries at prefix levels. Feel free to think about the need to do it as well as how we could design it. Thanks for taking this up."_ @GeorgeJahad @xBis7 That's a great suggestion! thanks for explaining it so well. I'm presently in the process of creating a design document outlining how we can implement prefix-based searching for OBS (Object Store) buckets. You can monitor the progress of this initiative on Jira using the following link: https://issues.apache.org/jira/browse/HDDS-9535. Our primary objective at the moment is to ensure that our customers don't encounter any confusion when using Recon with various bucket types. Implementing prefix-based filtering will likely be a crucial improvement, and I'll be working on it soon. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
