Uploaded image for project: 'Apache Ozone'
  1. Apache Ozone
  2. HDDS-7585 Allow Ozone bucket/volume to use non-S3-compliance naming rule
  3. HDDS-7586

Allow users to create an Ozone bucket with non-s3-naming-convention

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.4.0
    • None

    Description

      To configure whether Ozone bucket's name will follow S3 naming rules or not, I propose to add a server side configuration 'ozone.om.namespace.s3.strict' in OM.

      There are two cases of the flag:

      When the config value flag is true, the bucket naming should follow S3 naming rules.

      When the config value flag is false, the bucket naming could choose not to follow S3 naming rules.

      I'd love to hear any feedback from the community! 
      Thank you!

      Attachments

        Issue Links

          fixes

          Bug - A problem which impairs or prevents the functions of the product. HDDS-8498 "Bucket or Volume name has an unsupported character : _" On put to non-existant bucket

          • Major - Major loss of function.
          • Resolved
          is a child of

          Improvement - An improvement or enhancement to an existing feature or task. HDDS-7585 Allow Ozone bucket/volume to use non-S3-compliance naming rule

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link GitHub Pull Request #4037

          Web Link GitHub Pull Request #4524

          Activity

            People

              dteng Dave Teng
              dteng Dave Teng
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: