MeltanoLabs / MeltanoLabs/tap-postgres
Allow Log Based to work with SQLAlchemy URI as well as providing host/user/port etc
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
We could pull all of this from the sqlalchemy url too so folks don't have to use host, user, etc (Useful mainly for odd paramaters folks may need to use in the sqlalchemy url)
Originally posted by @visch in https://github.com/MeltanoLabs/tap-postgres/pull/249#discussion_r1357366591
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
The issue names no files or tests. Start by locating the log-based replication entry point and the existing host, user, and port configuration, then trace how the SQLAlchemy URI is handled. Done means log-based operation can obtain those connection details, including unusual URI parameters, directly from the SQLAlchemy URI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python, sqlalchemy
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100