I propose a small change in the validation of the snowflake.topic2table.map property regarding the topics being configured.
We have faced more than once a failed copy/paste between the topics and the snowflake.topic2table.map properties, messing up with casing or some simple miss-typing, generating silent errors in the sinks, as the topics would still be ingested in Snowflake, but not in the desired table, causing some headaches.
So, the change I propose is the following: In the Utils.parseTopicToTable method, validate that, each topic present in the map, matches with, at least, one of the defined topics / regexes, and if a topic is not present, throw a new error informing about the mismatch between the topics being configured as source, and the mappings available, so the developer:
Makes sure that every topic configured in the snowflake.topic2table.map property is being ingested by the connector.
Knows if a mismatch happens between the configured topics and the mapping between topics and tables.
Hi Snowflake Team,
I propose a small change in the validation of the
snowflake.topic2table.map
property regarding the topics being configured.We have faced more than once a failed copy/paste between the
topics
and thesnowflake.topic2table.map
properties, messing up with casing or some simple miss-typing, generating silent errors in the sinks, as the topics would still be ingested in Snowflake, but not in the desired table, causing some headaches.So, the change I propose is the following: In the Utils.parseTopicToTable method, validate that, each topic present in the map, matches with, at least, one of the defined topics / regexes, and if a topic is not present, throw a new error informing about the mismatch between the topics being configured as source, and the mappings available, so the developer:
snowflake.topic2table.map
property is being ingested by the connector.