Meltano supported target-postgres

[pnadolny13]

• Repo: https://github.com/MeltanoLabs/target-postgres
• Slack channel: https://meltano.slack.com/archives/C04CLA0S4G0/p1669058552528759

Development Scope:

• [x] tagged release
• [x] tests pass in CI
• [x] branch protection
• [x] cookiecutter TODOs completed and removed
• [x] clean README
• [x] Added to meltano hub
• [ ] feature coverage relative to Hub default https://hub.meltano.com/loaders/target-postgres--transferwise/?
  • [ ] https://github.com/MeltanoLabs/target-postgres/pull/89
  • [ ] https://github.com/MeltanoLabs/target-postgres/issues/86
  • [ ] https://github.com/MeltanoLabs/target-postgres/issues/71
  • [ ] https://github.com/MeltanoLabs/target-postgres/issues/54
  • [ ] https://github.com/MeltanoLabs/target-postgres/issues/2

Out of scope features mentioned:

• https://github.com/MeltanoLabs/target-postgres/issues/3
• https://github.com/MeltanoLabs/target-postgres/issues/73

[pnadolny13]

@tayloramurphy I created this to define the scope of development for these new plugins, track status, and decide when its ready to recommend. Can you help fill in the description with the features (specific to this source) we expect the initial release to support? It will help us and users understand what done is and when we're there.

cc @visch @aaronsteers

[visch]

I don't know when we want to make the swap for the default variant the MeltanoLabs variant.

What I can say is what features does transferwise have that we don't have. Note that because transferwise has been used for a lot longer time they have a lot of "longtail" fixes that we just haven't hit yet with the meltanolabs variant. I also haven't been trying to build at feature parity. Maybe we could take the tests from their variant just to verify everything works as expected.

"Important" features missing from meltanolabs variant. I'm not sure these should hold up the swap to default variant recommendation. The target does work today in a lot of use cases:

1. Activate Version - https://github.com/MeltanoLabs/target-postgres/pull/89 (Done, just needs to get merged)
2. anyOf - https://github.com/MeltanoLabs/target-postgres/issues/86
3. SSL - https://github.com/MeltanoLabs/target-postgres/issues/71 (Should be easy)
4. Append Only - https://github.com/MeltanoLabs/target-postgres/issues/54
5. Allow Column Alters - https://github.com/MeltanoLabs/target-postgres/issues/2
6. Parallelism - https://github.com/MeltanoLabs/target-postgres/issues/3 (Should be easy)
7. Native Batch Support - https://github.com/MeltanoLabs/target-postgres/issues/73

@aaronsteers has prioritized these for me generally in the order from top to botom (Not including anything Parallelism or below)

[aaronsteers]

Thanks, @visch! If SSH (https://github.com/MeltanoLabs/target-postgres/issues/71) becomes difficult, we can push it back. And for anyOf, we can keep the scope there nice and small by focusing on the "nullable" use cases - and not yet handling more complex data type intersections.

With those two notes, I think the above list looks great. Thanks again.

[pnadolny13]

@aaronsteers @visch this is great! I updated the issue checklist with what I think is the consensus in/out of scope items. Definitely feel free to change them if more stuff comes up thats blocking us recommending this variant.

@aaronsteers @visch I did ^^^ the same thing as I mentioned in https://github.com/MeltanoLabs/Meta/issues/35#issuecomment-1413982770