elek commented on a change in pull request #2117:
URL: https://github.com/apache/ozone/pull/2117#discussion_r607983462



##########
File path: hadoop-hdds/docs/content/feature/PrefixFSO.md
##########
@@ -0,0 +1,44 @@
+---
+title: "Prefix based FileSystem Optimization"
+weight: 2
+menu:
+   main:
+      parent: Features
+summary: Supports atomic rename and delete operation.
+---
+<!---
+  Licensed to the Apache Software Foundation (ASF) under one or more
+  contributor license agreements.  See the NOTICE file distributed with
+  this work for additional information regarding copyright ownership.
+  The ASF licenses this file to You under the Apache License, Version 2.0
+  (the "License"); you may not use this file except in compliance with
+  the License.  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+-->
+
+The prefix based FileSystem optimization feature supports atomic rename and
+ delete of any directory at any level in the namespace. Also, it will perform
+  rename and delete of any directory in a deterministic/constant time.
+
+

Review comment:
       Do we need to add some recommendation when should it be turned on?
   
   > This feature is strongly recommended to be turned on when Ozone buckets 
are mainly used via Hadoop compatible interfaces, especially with high number 
of files in deep directory hierachy.

##########
File path: hadoop-hdds/docs/content/feature/PrefixFSO.md
##########
@@ -0,0 +1,44 @@
+---
+title: "Prefix based FileSystem Optimization"
+weight: 2
+menu:
+   main:
+      parent: Features
+summary: Supports atomic rename and delete operation.
+---
+<!---
+  Licensed to the Apache Software Foundation (ASF) under one or more
+  contributor license agreements.  See the NOTICE file distributed with
+  this work for additional information regarding copyright ownership.
+  The ASF licenses this file to You under the Apache License, Version 2.0
+  (the "License"); you may not use this file except in compliance with
+  the License.  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+-->
+
+The prefix based FileSystem optimization feature supports atomic rename and
+ delete of any directory at any level in the namespace. Also, it will perform
+  rename and delete of any directory in a deterministic/constant time.
+
+
+## Configuration
+By default the feature is disabled. It can be enabled with the following
+ settings in `ozone-site.xml`:
+
+```XML
+<property>
+   <name>ozone.om.enable.filesystem.paths</name>
+   <value>true</value>
+</property>
+<property>
+   <name>ozone.om.metadata.layout</name>
+   <value>prefix</value>
+</property>
+```

Review comment:
       I would say some warning about the S3 compatibility: similar to this one:
   
   
   > Note: This feature works only when `ozone.om.enable.filesystem.paths` is 
enabled which means that *Hadoop Comptible File System* compatibility is 
favored instead of S3 compatibility. Some irregular S3 key names may be 
rejected or normalized. 




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