MeltanoLabs / MeltanoLabs/target-postgres
Additional Configuration Option support
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 23
- Avg merge
- 4h 45m
- Merged PRs (30d)
- 4
Description
It seems like we'd want to support at least the following configurations. We may want to make seperate issues for these if they are a significant effort
- #70
- Host,Username,Port,Password,DBName, with SQL Alchemy having folks specify a url may be ok for now, it's the same thing. Seperate issue potentially - https://github.com/MeltanoLabs/target-postgres/pull/32
- #71
- #72
- Support primary_key_required - https://github.com/MeltanoLabs/target-postgres/issues/54
- Support temp_directory for copy commands
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 the unchecked configuration items, especially #70 and support for temp_directory for copy commands, along with the referenced issue and pull request. Confirm which checklist entries remain applicable and identify the configuration entry points and tests; done means the remaining supported options work and the checklist is updated.
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
- Needs clarification
- Newbie friendliness
- 25/100