rakeshadr commented on pull request #1891:
URL: https://github.com/apache/ozone/pull/1891#issuecomment-776480046


   > From the description it's not fully clear what is the goal of this tool. 
Can you please help me to understand the use-case? Looks interesting...
   > 
   > (Is it similar to the `ozone debug ldb`?)
   
   Thanks @elek for the interest in this work. As we know, with prefix based 
implementation keypath stores only leaf node(fileName/dirName)i and table key 
like <parentID/fileName>. The idea behind this tool is to print only necessary 
information to quickly help to inter-connect the path elements. `ldb` is 
printing entire details and which is difficult to go through all the content 
and find out any mistakes quickly. I believe, we would add more tools based on 
the usability/debugability.
   
   Welcome thoughts/feedback:-)
   
      ```
       For example, if a key "a/b/key1" created into a FSOBucket then each
       path component will be assigned an ObjectId and linked to its parent path
       component using parent's objectID.
      
       Say, Bucket's ObjectID = 512, which is the parent for its immediate child
       element.
   
      | ------------------------------------------|
      | PathComponent |   ObjectID   |   ParentID |
      | ------------------------------------------|
      |      a        |     1024     |     512    |
      | ------------------------------------------|
      |      b        |     1025     |     1024   |
      | ------------------------------------------|
      |     key1      |     1026     |     1025   |
      | ------------------------------------------|
   ```
   


----------------------------------------------------------------
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]

Reply via email to