stephen_bailey
08/04/2021, 2:17 PMcalls
endpoint having a bunch of nested tables, like "participants", "topics", "analytics", etc.
As a developer, I could implement this mega-table as a single stream (truer to the interface and an "EL" workflow), or I could create more sensible child tables along the lines of the "multistream" approach described in this issue (https://gitlab.com/meltano/sdk/-/issues/167). I'm curious if anyone has a philosophical opinion on the approach?