[ 
https://issues.apache.org/jira/browse/HDDS-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17165155#comment-17165155
 ] 

Yiqun Lin edited comment on HDDS-2939 at 7/26/20, 4:06 AM:
-----------------------------------------------------------

Hi [~rakeshr], I take the quick look for the first PR PR-1230. It reuses the 
PrefixTable to store like directory info I have a question: this will not break 
original key lookup behavior? We don't have the object id assigned for keys in 
prefix table, but current logic assumes that each entry key has its own 
objectId in table. Or maybe we will have a step to generate this object id 
firstly when users start to enable this feature from their existed Ozone system.


was (Author: linyiqun):
Hi [~rakeshr], I take the quick look for the first PR PR-1230. It reuses the 
PrefixTable to store like directory info I have a question: this will not break 
original key lookup behavior? We don't have the object id assigned for keys in 
prefix table, but current logic assumes that each entry key has its own 
objectId in table.

> Ozone FS namespace
> ------------------
>
>                 Key: HDDS-2939
>                 URL: https://issues.apache.org/jira/browse/HDDS-2939
>             Project: Hadoop Distributed Data Store
>          Issue Type: New Feature
>          Components: Ozone Manager
>            Reporter: Supratim Deka
>            Assignee: Rakesh Radhakrishnan
>            Priority: Major
>              Labels: Triaged
>         Attachments: Ozone FS Namespace Proposal v1.0.docx
>
>
> Create the structures and metadata layout required to support efficient FS 
> namespace operations in Ozone - operations involving folders/directories 
> required to support the Hadoop compatible Filesystem interface.
> The details are described in the attached document. The work is divided up 
> into sub-tasks as per the task list in the document.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to