What’s the ETA on allowing new source tables in a ...
# advice-data-ingestion
r
What’s the ETA on allowing new source tables in a PG instance to be added without having to refresh the entire destination? Combined with the throughput on large tables, this starts to become a problem 😞
m
This is a work in progress @Rocky Appiah but very complex one 😞 had a lot of changes in Airbyte protocol
r
Ok so no ETA at the moment?
Any recommendations on workarounds until then?
m
No ETA unfortunately, recommendation is separate big tables in single connections and small tables in a generic one
r
@Marcos Marx (Airbyte): this won’t break capturing incremental updates? i.e.:
Incremental | Deduped + history
i.e.: one connection won’t clear data in the replication slot? causing the second connection to miss updates?
Or do we need a separate slot for each connection, I assume so 😞
m
If you break into multiple connection the best practice is to have individual slots
r
@Marcos Marx (Airbyte): can I use the same publications for all tables, just different replication slots yes?