You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "echonesis (via GitHub)" <gi...@apache.org> on 2026/01/03 03:55:48 UTC
[PR] HDDS-14285. [Website v2] [Docs] [Core Concepts] Buckets Overview [ozone-site]
echonesis opened a new pull request, #207:
URL: https://github.com/apache/ozone-site/pull/207
## What changes were proposed in this pull request?
Complete the page https://ozone-site-v2.staged.apache.org/docs/core-concepts/namespace/buckets/overview using the content from the section "Buckets " in the v1 page https://ozone.apache.org/docs/edge/concept/volumesbucketskeys.html
Note: the bucket quota description should go into the page https://ozone-site-v2.staged.apache.org/docs/core-concepts/namespace/buckets/quotas, and the bucket encryption should go into https://ozone-site-v2.staged.apache.org/docs/core-concepts/namespace/buckets/encryption.
> We link GDPR documentation back to Doc V1 until it's migrated to Doc V2.
## What is the link to the Apache Jira?
https://issues.apache.org/jira/browse/HDDS-14285
## How was this patch tested?
- [x] The CI checks on my fork are passing
- [x] I verified the rendered content using a local preview
- [x] I manually verified the steps provided in this change work as described
GitHub Actions CI: https://github.com/echonesis/ozone-site/actions/runs/20671827892
--
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: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-14285. [Website v2] [Docs] [Core Concepts] Buckets Overview [ozone-site]
Posted by "echonesis (via GitHub)" <gi...@apache.org>.
echonesis commented on code in PR #207:
URL: https://github.com/apache/ozone-site/pull/207#discussion_r2659005530
##########
docs/03-core-concepts/03-namespace/02-buckets/01-overview.md:
##########
@@ -4,4 +4,58 @@ sidebar_label: Overview
# Buckets Overview
-**TODO:** File a subtask under [HDDS-9857](https://issues.apache.org/jira/browse/HDDS-9857) and complete this page or section.
+## What is a Bucket?
+
+A **Bucket** is the second level in the Ozone data hierarchy, residing within a volume. Buckets are analogous to directories or folders in a traditional file system.
+They serve as containers for keys (data objects).
+
+**Key Characteristics:**
+
+- **Contained within Volumes:** Every bucket must belong to a volume.
+- **Container for Keys:** A bucket can contain any number of keys.
+- **No Nested Buckets:** Unlike directories, buckets cannot contain other buckets.
+
+## Details
+
+### Creation and Management
+
+Buckets are created within a specified volume.
+
+```bash
+ozone sh bucket create /myvolume/mybucket
+```
+
+For more details on bucket operations, refer to the [Ozone CLI documentation](../../../04-user-guide/01-client-interfaces/01-o3.md#bucket-operations).
+
+### Bucket Layouts (Object Store vs. File System Optimized)
+
+Ozone supports different bucket layouts, primarily:
+
+- **Object Store (OBS):** The traditional object storage layout, where keys are stored with their full path names. This is suitable for S3-like access patterns.
+- **File System Optimized (FSO):** An optimized layout for Hadoop Compatible File System (HCFS) semantics, where intermediate directories are stored separately, improving performance for file system operations like listing and renaming.
+For more details, refer to the [Prefix FSO documentation](../../../07-system-internals/07-features/01-filesystem-optimization.md).
+
+### Erasure Coding
+
+Erasure Coding (EC) can be enabled at the bucket level to define data redundancy strategies. This allows for more efficient storage compared to replication, especially for large datasets.
+For more information, see the [Erasure Coding documentation](../../../07-system-internals/07-features/04-erasure-coding.md).
+
+### Snapshots
+
+Ozone's snapshot feature allows users to take point-in-time consistent images of a given bucket. These snapshots are immutable and can be used for backup, recovery, archival, and incremental replication purposes.
+For more details, refer to the [Ozone Snapshot documentation](../../../07-system-internals/07-features/03-bucket-snapshots.md).
+
+### GDPR Compliance
+
+Ozone provides features to support GDPR compliance, particularly the "right to be forgotten." When a GDPR-compliant bucket is created, encryption keys for deleted data are immediately removed, making the data unreadable even if the underlying blocks haven't been physically purged yet.
+For more details, refer to the [GDPR documentation](https://ozone.apache.org/docs/edge/security/gdpr.html).
Review Comment:
Thanks for pointing this out.
I will migrate the GDPR part to [Administrator Guide] -> [Configuration] -> [Security] -> [GDPR].
What do you think? I'm open to your perspective on this!
--
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: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-14285. [Website v2] [Docs] [Core Concepts] Buckets Overview [ozone-site]
Posted by "jojochuang (via GitHub)" <gi...@apache.org>.
jojochuang commented on code in PR #207:
URL: https://github.com/apache/ozone-site/pull/207#discussion_r2659455636
##########
docs/03-core-concepts/03-namespace/02-buckets/01-overview.md:
##########
@@ -4,4 +4,58 @@ sidebar_label: Overview
# Buckets Overview
-**TODO:** File a subtask under [HDDS-9857](https://issues.apache.org/jira/browse/HDDS-9857) and complete this page or section.
+## What is a Bucket?
+
+A **Bucket** is the second level in the Ozone data hierarchy, residing within a volume. Buckets are analogous to directories or folders in a traditional file system.
+They serve as containers for keys (data objects).
+
+**Key Characteristics:**
+
+- **Contained within Volumes:** Every bucket must belong to a volume.
+- **Container for Keys:** A bucket can contain any number of keys.
+- **No Nested Buckets:** Unlike directories, buckets cannot contain other buckets.
+
+## Details
+
+### Creation and Management
+
+Buckets are created within a specified volume.
+
+```bash
+ozone sh bucket create /myvolume/mybucket
+```
+
+For more details on bucket operations, refer to the [Ozone CLI documentation](../../../04-user-guide/01-client-interfaces/01-o3.md#bucket-operations).
+
+### Bucket Layouts (Object Store vs. File System Optimized)
+
+Ozone supports different bucket layouts, primarily:
+
+- **Object Store (OBS):** The traditional object storage layout, where keys are stored with their full path names. This is suitable for S3-like access patterns.
+- **File System Optimized (FSO):** An optimized layout for Hadoop Compatible File System (HCFS) semantics, where intermediate directories are stored separately, improving performance for file system operations like listing and renaming.
+For more details, refer to the [Prefix FSO documentation](../../../07-system-internals/07-features/01-filesystem-optimization.md).
+
+### Erasure Coding
+
+Erasure Coding (EC) can be enabled at the bucket level to define data redundancy strategies. This allows for more efficient storage compared to replication, especially for large datasets.
+For more information, see the [Erasure Coding documentation](../../../07-system-internals/07-features/04-erasure-coding.md).
+
+### Snapshots
+
+Ozone's snapshot feature allows users to take point-in-time consistent images of a given bucket. These snapshots are immutable and can be used for backup, recovery, archival, and incremental replication purposes.
+For more details, refer to the [Ozone Snapshot documentation](../../../07-system-internals/07-features/03-bucket-snapshots.md).
+
+### GDPR Compliance
+
+Ozone provides features to support GDPR compliance, particularly the "right to be forgotten." When a GDPR-compliant bucket is created, encryption keys for deleted data are immediately removed, making the data unreadable even if the underlying blocks haven't been physically purged yet.
+For more details, refer to the [GDPR documentation](https://ozone.apache.org/docs/edge/security/gdpr.html).
Review Comment:
Yeah looks good to me.
--
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: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-14285. [Website v2] [Docs] [Core Concepts] Buckets Overview [ozone-site]
Posted by "echonesis (via GitHub)" <gi...@apache.org>.
echonesis commented on code in PR #207:
URL: https://github.com/apache/ozone-site/pull/207#discussion_r2659006909
##########
docs/03-core-concepts/03-namespace/02-buckets/01-overview.md:
##########
@@ -4,4 +4,58 @@ sidebar_label: Overview
# Buckets Overview
-**TODO:** File a subtask under [HDDS-9857](https://issues.apache.org/jira/browse/HDDS-9857) and complete this page or section.
+## What is a Bucket?
+
+A **Bucket** is the second level in the Ozone data hierarchy, residing within a volume. Buckets are analogous to directories or folders in a traditional file system.
+They serve as containers for keys (data objects).
+
+**Key Characteristics:**
+
+- **Contained within Volumes:** Every bucket must belong to a volume.
+- **Container for Keys:** A bucket can contain any number of keys.
+- **No Nested Buckets:** Unlike directories, buckets cannot contain other buckets.
+
+## Details
+
+### Creation and Management
+
+Buckets are created within a specified volume.
+
+```bash
+ozone sh bucket create /myvolume/mybucket
+```
+
+For more details on bucket operations, refer to the [Ozone CLI documentation](../../../04-user-guide/01-client-interfaces/01-o3.md#bucket-operations).
+
+### Bucket Layouts (Object Store vs. File System Optimized)
+
+Ozone supports different bucket layouts, primarily:
+
+- **Object Store (OBS):** The traditional object storage layout, where keys are stored with their full path names. This is suitable for S3-like access patterns.
+- **File System Optimized (FSO):** An optimized layout for Hadoop Compatible File System (HCFS) semantics, where intermediate directories are stored separately, improving performance for file system operations like listing and renaming.
+For more details, refer to the [Prefix FSO documentation](../../../07-system-internals/07-features/01-filesystem-optimization.md).
+
+### Erasure Coding
+
+Erasure Coding (EC) can be enabled at the bucket level to define data redundancy strategies. This allows for more efficient storage compared to replication, especially for large datasets.
+For more information, see the [Erasure Coding documentation](../../../07-system-internals/07-features/04-erasure-coding.md).
Review Comment:
Thanks!
I will update it in the next commit.
--
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: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-14285. [Website v2] [Docs] [Core Concepts] Buckets Overview [ozone-site]
Posted by "echonesis (via GitHub)" <gi...@apache.org>.
echonesis commented on code in PR #207:
URL: https://github.com/apache/ozone-site/pull/207#discussion_r2659007095
##########
docs/03-core-concepts/03-namespace/02-buckets/01-overview.md:
##########
@@ -4,4 +4,58 @@ sidebar_label: Overview
# Buckets Overview
-**TODO:** File a subtask under [HDDS-9857](https://issues.apache.org/jira/browse/HDDS-9857) and complete this page or section.
+## What is a Bucket?
+
+A **Bucket** is the second level in the Ozone data hierarchy, residing within a volume. Buckets are analogous to directories or folders in a traditional file system.
+They serve as containers for keys (data objects).
+
+**Key Characteristics:**
+
+- **Contained within Volumes:** Every bucket must belong to a volume.
+- **Container for Keys:** A bucket can contain any number of keys.
+- **No Nested Buckets:** Unlike directories, buckets cannot contain other buckets.
+
+## Details
+
+### Creation and Management
+
+Buckets are created within a specified volume.
+
+```bash
+ozone sh bucket create /myvolume/mybucket
+```
+
+For more details on bucket operations, refer to the [Ozone CLI documentation](../../../04-user-guide/01-client-interfaces/01-o3.md#bucket-operations).
+
+### Bucket Layouts (Object Store vs. File System Optimized)
+
+Ozone supports different bucket layouts, primarily:
+
+- **Object Store (OBS):** The traditional object storage layout, where keys are stored with their full path names. This is suitable for S3-like access patterns.
+- **File System Optimized (FSO):** An optimized layout for Hadoop Compatible File System (HCFS) semantics, where intermediate directories are stored separately, improving performance for file system operations like listing and renaming.
+For more details, refer to the [Prefix FSO documentation](../../../07-system-internals/07-features/01-filesystem-optimization.md).
Review Comment:
Thanks!
I will update it in the next commit.
##########
docs/03-core-concepts/03-namespace/02-buckets/01-overview.md:
##########
@@ -4,4 +4,58 @@ sidebar_label: Overview
# Buckets Overview
-**TODO:** File a subtask under [HDDS-9857](https://issues.apache.org/jira/browse/HDDS-9857) and complete this page or section.
+## What is a Bucket?
+
+A **Bucket** is the second level in the Ozone data hierarchy, residing within a volume. Buckets are analogous to directories or folders in a traditional file system.
+They serve as containers for keys (data objects).
+
+**Key Characteristics:**
+
+- **Contained within Volumes:** Every bucket must belong to a volume.
+- **Container for Keys:** A bucket can contain any number of keys.
+- **No Nested Buckets:** Unlike directories, buckets cannot contain other buckets.
+
+## Details
+
+### Creation and Management
+
+Buckets are created within a specified volume.
+
+```bash
+ozone sh bucket create /myvolume/mybucket
+```
+
+For more details on bucket operations, refer to the [Ozone CLI documentation](../../../04-user-guide/01-client-interfaces/01-o3.md#bucket-operations).
+
+### Bucket Layouts (Object Store vs. File System Optimized)
+
+Ozone supports different bucket layouts, primarily:
+
+- **Object Store (OBS):** The traditional object storage layout, where keys are stored with their full path names. This is suitable for S3-like access patterns.
Review Comment:
Thanks!
I will update it in the next commit.
--
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: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-14285. [Website v2] [Docs] [Core Concepts] Buckets Overview [ozone-site]
Posted by "jojochuang (via GitHub)" <gi...@apache.org>.
jojochuang commented on code in PR #207:
URL: https://github.com/apache/ozone-site/pull/207#discussion_r2658935343
##########
docs/03-core-concepts/03-namespace/02-buckets/01-overview.md:
##########
@@ -4,4 +4,58 @@ sidebar_label: Overview
# Buckets Overview
-**TODO:** File a subtask under [HDDS-9857](https://issues.apache.org/jira/browse/HDDS-9857) and complete this page or section.
+## What is a Bucket?
+
+A **Bucket** is the second level in the Ozone data hierarchy, residing within a volume. Buckets are analogous to directories or folders in a traditional file system.
+They serve as containers for keys (data objects).
+
+**Key Characteristics:**
+
+- **Contained within Volumes:** Every bucket must belong to a volume.
+- **Container for Keys:** A bucket can contain any number of keys.
+- **No Nested Buckets:** Unlike directories, buckets cannot contain other buckets.
+
+## Details
+
+### Creation and Management
+
+Buckets are created within a specified volume.
+
+```bash
+ozone sh bucket create /myvolume/mybucket
+```
+
+For more details on bucket operations, refer to the [Ozone CLI documentation](../../../04-user-guide/01-client-interfaces/01-o3.md#bucket-operations).
+
+### Bucket Layouts (Object Store vs. File System Optimized)
+
+Ozone supports different bucket layouts, primarily:
+
+- **Object Store (OBS):** The traditional object storage layout, where keys are stored with their full path names. This is suitable for S3-like access patterns.
+- **File System Optimized (FSO):** An optimized layout for Hadoop Compatible File System (HCFS) semantics, where intermediate directories are stored separately, improving performance for file system operations like listing and renaming.
+For more details, refer to the [Prefix FSO documentation](../../../07-system-internals/07-features/01-filesystem-optimization.md).
+
+### Erasure Coding
+
+Erasure Coding (EC) can be enabled at the bucket level to define data redundancy strategies. This allows for more efficient storage compared to replication, especially for large datasets.
+For more information, see the [Erasure Coding documentation](../../../07-system-internals/07-features/04-erasure-coding.md).
+
+### Snapshots
+
+Ozone's snapshot feature allows users to take point-in-time consistent images of a given bucket. These snapshots are immutable and can be used for backup, recovery, archival, and incremental replication purposes.
+For more details, refer to the [Ozone Snapshot documentation](../../../07-system-internals/07-features/03-bucket-snapshots.md).
Review Comment:
TODO: We need to add a short intro to Snapshot under Core Concepts -> Namespace -> Buckets -> Snapshots
##########
docs/03-core-concepts/03-namespace/02-buckets/01-overview.md:
##########
@@ -4,4 +4,58 @@ sidebar_label: Overview
# Buckets Overview
-**TODO:** File a subtask under [HDDS-9857](https://issues.apache.org/jira/browse/HDDS-9857) and complete this page or section.
+## What is a Bucket?
+
+A **Bucket** is the second level in the Ozone data hierarchy, residing within a volume. Buckets are analogous to directories or folders in a traditional file system.
+They serve as containers for keys (data objects).
+
+**Key Characteristics:**
+
+- **Contained within Volumes:** Every bucket must belong to a volume.
+- **Container for Keys:** A bucket can contain any number of keys.
+- **No Nested Buckets:** Unlike directories, buckets cannot contain other buckets.
+
+## Details
+
+### Creation and Management
+
+Buckets are created within a specified volume.
+
+```bash
+ozone sh bucket create /myvolume/mybucket
+```
+
+For more details on bucket operations, refer to the [Ozone CLI documentation](../../../04-user-guide/01-client-interfaces/01-o3.md#bucket-operations).
+
+### Bucket Layouts (Object Store vs. File System Optimized)
+
+Ozone supports different bucket layouts, primarily:
+
+- **Object Store (OBS):** The traditional object storage layout, where keys are stored with their full path names. This is suitable for S3-like access patterns.
+- **File System Optimized (FSO):** An optimized layout for Hadoop Compatible File System (HCFS) semantics, where intermediate directories are stored separately, improving performance for file system operations like listing and renaming.
+For more details, refer to the [Prefix FSO documentation](../../../07-system-internals/07-features/01-filesystem-optimization.md).
Review Comment:
Link to Core Concepts -> Namespace -> Buckets -> Layouts -> File System Optimized (FSO)
##########
docs/03-core-concepts/03-namespace/02-buckets/01-overview.md:
##########
@@ -4,4 +4,58 @@ sidebar_label: Overview
# Buckets Overview
-**TODO:** File a subtask under [HDDS-9857](https://issues.apache.org/jira/browse/HDDS-9857) and complete this page or section.
+## What is a Bucket?
+
+A **Bucket** is the second level in the Ozone data hierarchy, residing within a volume. Buckets are analogous to directories or folders in a traditional file system.
+They serve as containers for keys (data objects).
+
+**Key Characteristics:**
+
+- **Contained within Volumes:** Every bucket must belong to a volume.
+- **Container for Keys:** A bucket can contain any number of keys.
+- **No Nested Buckets:** Unlike directories, buckets cannot contain other buckets.
+
+## Details
+
+### Creation and Management
+
+Buckets are created within a specified volume.
+
+```bash
+ozone sh bucket create /myvolume/mybucket
+```
+
+For more details on bucket operations, refer to the [Ozone CLI documentation](../../../04-user-guide/01-client-interfaces/01-o3.md#bucket-operations).
+
+### Bucket Layouts (Object Store vs. File System Optimized)
+
+Ozone supports different bucket layouts, primarily:
+
+- **Object Store (OBS):** The traditional object storage layout, where keys are stored with their full path names. This is suitable for S3-like access patterns.
+- **File System Optimized (FSO):** An optimized layout for Hadoop Compatible File System (HCFS) semantics, where intermediate directories are stored separately, improving performance for file system operations like listing and renaming.
+For more details, refer to the [Prefix FSO documentation](../../../07-system-internals/07-features/01-filesystem-optimization.md).
+
+### Erasure Coding
+
+Erasure Coding (EC) can be enabled at the bucket level to define data redundancy strategies. This allows for more efficient storage compared to replication, especially for large datasets.
+For more information, see the [Erasure Coding documentation](../../../07-system-internals/07-features/04-erasure-coding.md).
+
+### Snapshots
+
+Ozone's snapshot feature allows users to take point-in-time consistent images of a given bucket. These snapshots are immutable and can be used for backup, recovery, archival, and incremental replication purposes.
+For more details, refer to the [Ozone Snapshot documentation](../../../07-system-internals/07-features/03-bucket-snapshots.md).
+
+### GDPR Compliance
+
+Ozone provides features to support GDPR compliance, particularly the "right to be forgotten." When a GDPR-compliant bucket is created, encryption keys for deleted data are immediately removed, making the data unreadable even if the underlying blocks haven't been physically purged yet.
+For more details, refer to the [GDPR documentation](https://ozone.apache.org/docs/edge/security/gdpr.html).
Review Comment:
TODO: migrate GDPR specific content.
But I actually want to remove this section because the feature is never intended for production and as far as I am aware no one uses it.
##########
docs/03-core-concepts/03-namespace/02-buckets/01-overview.md:
##########
@@ -4,4 +4,58 @@ sidebar_label: Overview
# Buckets Overview
-**TODO:** File a subtask under [HDDS-9857](https://issues.apache.org/jira/browse/HDDS-9857) and complete this page or section.
+## What is a Bucket?
+
+A **Bucket** is the second level in the Ozone data hierarchy, residing within a volume. Buckets are analogous to directories or folders in a traditional file system.
+They serve as containers for keys (data objects).
+
+**Key Characteristics:**
+
+- **Contained within Volumes:** Every bucket must belong to a volume.
+- **Container for Keys:** A bucket can contain any number of keys.
+- **No Nested Buckets:** Unlike directories, buckets cannot contain other buckets.
+
+## Details
+
+### Creation and Management
+
+Buckets are created within a specified volume.
+
+```bash
+ozone sh bucket create /myvolume/mybucket
+```
+
+For more details on bucket operations, refer to the [Ozone CLI documentation](../../../04-user-guide/01-client-interfaces/01-o3.md#bucket-operations).
+
+### Bucket Layouts (Object Store vs. File System Optimized)
+
+Ozone supports different bucket layouts, primarily:
+
+- **Object Store (OBS):** The traditional object storage layout, where keys are stored with their full path names. This is suitable for S3-like access patterns.
+- **File System Optimized (FSO):** An optimized layout for Hadoop Compatible File System (HCFS) semantics, where intermediate directories are stored separately, improving performance for file system operations like listing and renaming.
+For more details, refer to the [Prefix FSO documentation](../../../07-system-internals/07-features/01-filesystem-optimization.md).
+
+### Erasure Coding
+
+Erasure Coding (EC) can be enabled at the bucket level to define data redundancy strategies. This allows for more efficient storage compared to replication, especially for large datasets.
+For more information, see the [Erasure Coding documentation](../../../07-system-internals/07-features/04-erasure-coding.md).
Review Comment:
please use the EC doc at Core Concepts -> Replication -> Erasure Coding.
##########
docs/03-core-concepts/03-namespace/02-buckets/01-overview.md:
##########
@@ -4,4 +4,58 @@ sidebar_label: Overview
# Buckets Overview
-**TODO:** File a subtask under [HDDS-9857](https://issues.apache.org/jira/browse/HDDS-9857) and complete this page or section.
+## What is a Bucket?
+
+A **Bucket** is the second level in the Ozone data hierarchy, residing within a volume. Buckets are analogous to directories or folders in a traditional file system.
+They serve as containers for keys (data objects).
+
+**Key Characteristics:**
+
+- **Contained within Volumes:** Every bucket must belong to a volume.
+- **Container for Keys:** A bucket can contain any number of keys.
+- **No Nested Buckets:** Unlike directories, buckets cannot contain other buckets.
+
+## Details
+
+### Creation and Management
+
+Buckets are created within a specified volume.
+
+```bash
+ozone sh bucket create /myvolume/mybucket
+```
+
+For more details on bucket operations, refer to the [Ozone CLI documentation](../../../04-user-guide/01-client-interfaces/01-o3.md#bucket-operations).
+
+### Bucket Layouts (Object Store vs. File System Optimized)
+
+Ozone supports different bucket layouts, primarily:
+
+- **Object Store (OBS):** The traditional object storage layout, where keys are stored with their full path names. This is suitable for S3-like access patterns.
Review Comment:
Link to Core Concepts -> Namespace -> Buckets -> Layouts -> Object Store Buckets (OBS)
--
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: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-14285. [Website v2] [Docs] [Core Concepts] Buckets Overview [ozone-site]
Posted by "jojochuang (via GitHub)" <gi...@apache.org>.
jojochuang merged PR #207:
URL: https://github.com/apache/ozone-site/pull/207
--
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: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-14285. [Website v2] [Docs] [Core Concepts] Buckets Overview [ozone-site]
Posted by "echonesis (via GitHub)" <gi...@apache.org>.
echonesis commented on code in PR #207:
URL: https://github.com/apache/ozone-site/pull/207#discussion_r2659007789
##########
docs/03-core-concepts/03-namespace/02-buckets/01-overview.md:
##########
@@ -4,4 +4,58 @@ sidebar_label: Overview
# Buckets Overview
-**TODO:** File a subtask under [HDDS-9857](https://issues.apache.org/jira/browse/HDDS-9857) and complete this page or section.
+## What is a Bucket?
+
+A **Bucket** is the second level in the Ozone data hierarchy, residing within a volume. Buckets are analogous to directories or folders in a traditional file system.
+They serve as containers for keys (data objects).
+
+**Key Characteristics:**
+
+- **Contained within Volumes:** Every bucket must belong to a volume.
+- **Container for Keys:** A bucket can contain any number of keys.
+- **No Nested Buckets:** Unlike directories, buckets cannot contain other buckets.
+
+## Details
+
+### Creation and Management
+
+Buckets are created within a specified volume.
+
+```bash
+ozone sh bucket create /myvolume/mybucket
+```
+
+For more details on bucket operations, refer to the [Ozone CLI documentation](../../../04-user-guide/01-client-interfaces/01-o3.md#bucket-operations).
+
+### Bucket Layouts (Object Store vs. File System Optimized)
+
+Ozone supports different bucket layouts, primarily:
+
+- **Object Store (OBS):** The traditional object storage layout, where keys are stored with their full path names. This is suitable for S3-like access patterns.
+- **File System Optimized (FSO):** An optimized layout for Hadoop Compatible File System (HCFS) semantics, where intermediate directories are stored separately, improving performance for file system operations like listing and renaming.
+For more details, refer to the [Prefix FSO documentation](../../../07-system-internals/07-features/01-filesystem-optimization.md).
+
+### Erasure Coding
+
+Erasure Coding (EC) can be enabled at the bucket level to define data redundancy strategies. This allows for more efficient storage compared to replication, especially for large datasets.
+For more information, see the [Erasure Coding documentation](../../../07-system-internals/07-features/04-erasure-coding.md).
+
+### Snapshots
+
+Ozone's snapshot feature allows users to take point-in-time consistent images of a given bucket. These snapshots are immutable and can be used for backup, recovery, archival, and incremental replication purposes.
+For more details, refer to the [Ozone Snapshot documentation](../../../07-system-internals/07-features/03-bucket-snapshots.md).
Review Comment:
Thanks!
I've updated it and created a brief intro to bucket snapshot under Core Concepts -> Namespace -> Buckets -> Snapshots.
--
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: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org