MeltanoLabs / MeltanoLabs/target-postgres
Specify custom (non-default) schemas for streams?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 23
- Avg merge
- 4h 45m
- Merged PRs (30d)
- 4
Description
I'm currently using the "transferwise" target-postgres variant's schema_mapping setting to load data from different source dbs into their own schemas. This has been useful to keep data well-organized in the target postgres db.
I'm interested in switching to this variant, but don't see this option mentioned in the docs or in plans for future support. Would it be possible to add this functionality?
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 reading the linked schema_mapping documentation and the future-support discussion in issue #4, then compare how the current target-postgres variant handles stream schemas. Define the supported custom-schema behavior and verify that streams can be loaded into source-specific PostgreSQL schemas without breaking default behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100