Snowflake-to-Fabric Iceberg Mirroring: Scheduling Limits and Decimal Type Bugs Documented
Engineers integrating Snowflake Iceberg tables into Microsoft Fabric via mirroring have documented two significant issues uncovered through support investigations. First, Fabric currently offers no configurable mirroring schedules or replication windows, and stopping then restarting the service triggers a full data reload rather than resuming from the last change-data-capture position. Second, a type mismatch bug causes Spark reads to fail when a Parquet file stores a decimal column as INT32, even though the SQL analytics endpoint handles the same data without error. The team traced the discrepancy across Snowflake, Fabric table schema, and the underlying Parquet files, and submitted findings to Microsoft support. As a workaround, non-vectorized Spark reads resolved the decimal issue, though with notable performance and capacity trade-offs; the team is next evaluating whether routing Snowflake replication from AWS to Azure improves overall economics.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in