aws-samples / aws-samples/aws-glue-data-catalog-replication-utility
Feature Request - replicated glue catalog metadata to reflect destination s3 buckets
- Dominant language
- Java
- Stars
- 80
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
Firstly, Thanks to this amazing utility. It really helped!
It would be good to have a feature that involves replicated glue catalog's (destination) metadata to point to its respective cross-region replicated (destination) buckets instead of default source buckets (which source glue catalog metadata is pointed to)? Today, we will have to manually update the catalog table definition (glue APIs) with the new replicated bucket locations (destination).
Contributor guide
Research direction
The issue concerns AWS Glue Data Catalog replication and destination bucket locations, but names no files, tests, or entry points. Start by tracing the replication path and Glue API updates; done means replicated catalog table definitions point to their corresponding destination buckets without manual updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, java
- Domain
- cloud, data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100