You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ozone.apache.org by el...@apache.org on 2020/12/07 19:05:51 UTC
[ozone] 01/01: add more examples
This is an automated email from the ASF dual-hosted git repository.
elek pushed a commit to branch HDDS-4097
in repository https://gitbox.apache.org/repos/asf/ozone.git
commit 538600c2a235af36851388578e5abf77c143de47
Author: Elek Márton <el...@apache.org>
AuthorDate: Mon Dec 7 20:05:29 2020 +0100
add more examples
---
hadoop-hdds/docs/content/design/s3_hcfs.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/hadoop-hdds/docs/content/design/s3_hcfs.md b/hadoop-hdds/docs/content/design/s3_hcfs.md
index 88b4c6d..1c19bd0 100644
--- a/hadoop-hdds/docs/content/design/s3_hcfs.md
+++ b/hadoop-hdds/docs/content/design/s3_hcfs.md
@@ -92,7 +92,7 @@ As a result we can have three main options:
|-|-|-|-|-|-|
| default | DISABLED | DISABLED | 100 % compatibility | FULLY UNSUPPORTED | implemented, default |
| ozone.om.enable.filesystem.paths=true | ENABLED | ENABLED | limited compatibility | FULLY SUPPORTED | implemented |
-| ozone.om.enable.intermediate.dirs=true | ENABLED | DISABLED | 100% compatibility | SUPPORTED but partial view. | NOT implemented |
+| ozone.om.enable.intermediate.dirs=true | ENABLED | DISABLED | 100% compatibility | SUPPORTED but partial view | NOT implemented |
Let's talk all of these option in more details
@@ -142,7 +142,7 @@ This approach makes the normalization and prefix creation independent from each
| `ozone.om.enable.filesystem.paths=true` | Enable intermediate dir generation **AND** key name normalization |
| `ozone.om.enable.intermediate.dirs=true` | Enable only the intermediate dir generation |
-This mode can be 100% S3 compatibility (no forced normalization). But some of the path which are saved via S3 (like `a/b//////v`) couldn't be displayed via `ofs/o3fs`. This is the same behavior what S3A provides when incompatible path is found in S3.
+This mode can be 100% S3 compatibility (no forced normalization). But some of the path which are saved via S3 (like `a/b//////v`, `2019:12:23.txt` or `../../a.txt`) couldn't be displayed via `ofs/o3fs`. This is the same behavior what S3A provides when incompatible path is found in S3.
With this approach `ofs/o3fs` can show only a partial view
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@ozone.apache.org
For additional commands, e-mail: commits-help@ozone.apache.org