Skip to content

compatibility hints for topic-based subscription connectors - #10

Merged
andreyorst merged 2 commits into
mainfrom
rabbitmq
Apr 28, 2026
Merged

andreyorst merged 2 commits into
mainfrom
rabbitmq

Conversation

@andreyorst

Copy link
Copy Markdown
Contributor

No description provided.

@andreyorst
andreyorst requested a review from spicyfalafel April 27, 2026 12:25
Comment thread docs/modules/topic-based-subscriptions/aidbox-topic-based-subscriptions.md Outdated
@andreyorst
andreyorst merged commit 9e66fd1 into main Apr 28, 2026
2 checks passed
@andreyorst
andreyorst deleted the rabbitmq branch April 28, 2026 09:04
spicyfalafel added a commit that referenced this pull request May 26, 2026
…xport

Two parts:

1. **Strip "Phase 0/N" jargon** from the data-lakehouse tutorial. Phase
   numbers are an internal codebase organisation detail (managed-
   initial-export!'s body is structured as Phase 0..5) and mean
   nothing to a reader. Rephrase three places:
   - EXTERNAL_USE_LOCATION privilege rows (managed-zerobus + managed-
     sql tabs) — describe what the grant lets the module do, not which
     phase calls it.
   - Troubleshooting #10 (DELTA_CREATE_TABLE_SCHEME_MISMATCH) — refer
     to "auto-cleanup" instead of "Phase 0 auto-cleanup".
   - Troubleshooting #11 (staging-s3-cleanup-skipped log) — same.

2. **Document the same S3-staging-cleanup behaviour in
   $viewdefinition-export reference.** The $vd-export code path uses
   the identical `ensure-staging-table!` machinery (S3 files outlive
   UC `DROP TABLE`; cleanup runs at the start of the next call), but
   the reference said nothing about it. Add a "Staging cleanup on
   S3" subsection inside "How it works (kind=data-lakehouse)"
   covering the two practical consequences for typical cron-driven
   use: prefix rotation defeats auto-cleanup, and the
   `EXTERNAL_USE_LOCATION` grant is what enables it. Link out to
   the data-lakehouse tutorial's setup for the grant table itself.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants