FYI @s Just wanted to let you know but I noticed with the Snowflake destination, sometimes it creates tables with a different naming than what a user would expect and i didn't quite understand why yet... For example, I created a source with the file connector specifying the stream's name to be

airports

but i end up with tables called

airport_1604942713720

instead (which breaks normalization afterward since it's relying on finding

airports

.... I hope the work on the naming would kind of solve these kinds of issues!

thanks for the heads up!

and i don't see the same behavior on BigQuery (working properly there)