Support in pgloader to migrate databases to YugabyteDB
Nobody has claimed this yet.
- Dominant language
- Common Lisp
- Stars
- 6.5k
- Forks
- 613
- Avg merge
- 3h 46m
- Merged PRs (30d)
- 1
Description
YugabyteDB has support for most of the constructs used by pgloader. For some that are not yet supported, we can have alternate implementation and code paths specific to YugabyteDB to make it work.
There could be some use cases that will not work due to unsupported features in YugabyteDB, we can fail gracefully with a warning.
Some of the alternate ways to handle YugabyteDB are listed here and have been tried to make it work:
https://github.com/yugabyte/yugabyte-db/issues/7886
We should try to make the changes on the lines of Redshift where the code path specific to YugabyteDBs are executed depending on the version string.
If the community has an interest, we can raise the pull request so that migrating the database to YugabyteDB is natively supported by pgloader.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing pgloader's existing Redshift-specific code paths and how they branch on the version string. Compare those approaches with the YugabyteDB alternatives described in yugabyte-db/issues/7886. Done means YugabyteDB migration is natively supported, unsupported features fail gracefully with warnings, and the relevant migration paths work for supported constructs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgres
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100