Skip to content

Add S3TablesCreateNamespaceOperator#66360

Merged
vincbeck merged 1 commit intoapache:mainfrom
john-jac:add-s3tables-create-namespace
May 4, 2026
Merged

Add S3TablesCreateNamespaceOperator#66360
vincbeck merged 1 commit intoapache:mainfrom
john-jac:add-s3tables-create-namespace

Conversation

@john-jac
Copy link
Copy Markdown
Contributor

@john-jac john-jac commented May 4, 2026

What

Add S3TablesCreateNamespaceOperator to create namespaces in Amazon S3 Tables table buckets.

Why

Namespaces organize tables within a table bucket (table bucket → namespace → table). The existing system test used a @task with raw boto3 — this operator replaces that workaround and completes the S3 Tables resource hierarchy.

What was done

  • Operator: S3TablesCreateNamespaceOperator with if_exists idempotency, added to existing s3_tables.py
  • Unit tests: Added to existing test_s3_tables.py — happy path, skip-existing, fail-on-conflict, template fields
  • System test: Updated example_s3_tables.py — replaced @task create_namespace with operator
  • Docs: Updated s3_tables.rst with new section

@john-jac john-jac requested a review from o-nikolas as a code owner May 4, 2026 15:09
@boring-cyborg boring-cyborg Bot added area:dev-tools area:providers backport-to-v3-2-test Mark PR with this label to backport to v3-2-test branch kind:documentation provider:amazon AWS/Amazon - related issues labels May 4, 2026
Copy link
Copy Markdown
Contributor

@vincbeck vincbeck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please check which files are being committed before creating the PR

@john-jac john-jac force-pushed the add-s3tables-create-namespace branch from 416d896 to 7be6f69 Compare May 4, 2026 17:33
@vincbeck vincbeck merged commit 966b0ec into apache:main May 4, 2026
94 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 4, 2026

Backport failed to create: v3-2-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status Branch Result
v3-2-test Commit Link

You can attempt to backport this manually by running:

cherry_picker 966b0ec v3-2-test

This should apply the commit to the v3-2-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:dev-tools area:providers backport-to-v3-2-test Mark PR with this label to backport to v3-2-test branch kind:documentation provider:amazon AWS/Amazon - related issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants