What does a Snowflake Architect need to consider when implementing a Snowflake Connector for Kafka?
What does a Snowflake Architect need to consider when implementing a Snowflake Connector for Kafka?
When implementing a Snowflake Connector for Kafka, it is crucial to understand that the connector will automatically create necessary objects for data ingestion. Specifically, it creates one table and one pipe for each topic. If the connector is unable to create these objects, it will result in an exception. Therefore, proper permissions and configurations must be ensured to avoid operational issues.
Should be A. Default retention time is 7 days, only key/pair auth is supported and the connector will create a pipe, table and stage
Ye should be A. https://docs.snowflake.com/en/user-guide/kafka-connector-overview
Correction: The answer should be D. The connector creates the following objects for each topic: One internal stage to temporarily store data files for each topic. One pipe to ingest the data files for each topic partition. One table for each topic. If the table specified for each topic does not exist, the connector creates i
I think answer is "A": Each Kafka message is passed to Snowflake in JSON format or Avro format. Only issue with "D" answer is the last part of statement, does Snowflake raising the Exception, if unable to connector cannot create the table or the pipe.
The answer should be A