chore(ansible) Rename the landing bucket for iceberg tables#319
Conversation
The bucket will only store iceberg tables so name accordingly.
|
Warning Review limit reached
More reviews will be available in 32 minutes and 43 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
0601908 to
6238f3d
Compare
Summary
Clarify that the landing bucket for data ingested directly to iceberg tables only contains iceberg data. It removes
the key prefix and names the bucket accordingly with iceberg in the name.
The motivation for this change is the likelihood of other landing buckets existing for raw data in other formats. There is now a clear naming pattern for suffixes of
-landing-{descriptor}.