Open pnadolny13 opened 1 year ago
After a second test it looks like it's not repeating the same behavior. I'll do more testing but it seems like maybe it's only doing this when my tables selection is not finding a match.
@pnadolny13 any update on this?
create a PR to address this: https://github.com/MeltanoLabs/tap-snowflake/pull/36
@kgpayne I like the new support for the
tables
parameter but it looks like its implemented differently than I would expect. Let me know if this was discussed in other SDK issues already but here are my thoughts as a user on what I was expecting to happen:Expected Behavior
tables
array, then tap does discovery only on that schema and those tablesIn 2 if I only include a single table name then I would expect that the tap only queries the metadata of that one table.
Current Behavior
The schema seems to be used only to create a connection but not for filtering using that schema name, so my sync job runs
SHOW
queries for every schema in my warehouse still. The tables config works as expected but also iterates all schemas/tables in the process even though I've provided a short list of tables to consider. It doesnt discover the schema for every table but it still has to iterate through each one.Questions and Considerations
tables
array wouldnt it be better to flip the logic of the discovery step and search specifically for those tables instead of iterating all available schemas/tables?