Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 3.0.0-beta1
    • Fix Version/s: 3.2.0
    • Component/s: fs/s3
    • Labels:
      None

      Description

      Many organisations have a "no untagged" resource policy; s3guard runs into this when a table is created untagged. If there's a strict "delete untagged resources" policy, the tables will go without warning.

      Proposed: we add an option which can be used to declare the tags for a table when created, use it in creation. No need to worry about updating/viewing tags, as the AWS console can do that

        Attachments

        1. HADOOP-14734-001.patch
          15 kB
          Abraham Fine
        2. HADOOP-14734-002.patch
          15 kB
          Abraham Fine
        3. HADOOP-14734-003.patch
          8 kB
          Abraham Fine
        4. HADOOP-14734.004.patch
          15 kB
          Gabor Bota
        5. HADOOP-14734.005.patch
          16 kB
          Gabor Bota

          Issue Links

            Activity

              People

              • Assignee:
                gabor.bota Gabor Bota
                Reporter:
                stevel@apache.org Steve Loughran
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: