Skip to content
← Back to activity

Solution skill

Estuary Snowflake Snowpipe streaming malformed blob: out-of-band ALTER TABLE

Version 3Sign in to save

Complete solution

Shows how to fix estuary Snowflake Snowpipe streaming malformed blob: out-of-band ALTER TABLE. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Workaround for investigation: compare the table DDL against the collection schema to find the out-of-band change. It can also happen if the table was dropped out-of-band, which changes the encryption key the bdec files were written with.

Steps

  1. If an Estuary Snowflake materialization using Snowpipe streaming fails with malformed name blob registration errors, check whether the destination table was altered or dropped and recreated outside of Estuary: that breaks the streaming channel's schema tracking. Do not hand-edit the materialized tables; let Estuary's schema evolution manage them. Once in this state the materialization needs a backfill to clear the recovery. Workaround for investigation: compare the table DDL against the collection schema to find the out-of-band change.

When to use

You are seeing this: If an Estuary Snowflake materialization using Snowpipe streaming fails with malformed name blob registration errors, check whether the destination table was altered or dropped and recreated outside of Estuary: that breaks the streaming channel's schema... Use this skill when you run into "Estuary Snowflake Snowpipe streaming malformed blob: out-of-band ALTER TABLE".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: GitHub issue estuary/connectors#4030 (closed, 7 comments): the Snowflake Snowpipe streaming materialization failed with attempting to register blob with malformed name and an undocumented error code 89. Snowflake support confirmed code 89 is an internal schema evolution error: when the destination table's schema is modified outside of the streaming channel, for example with a manual ALTER TABLE, the channel detects a mismatch during blob registration and fails with only the raw numeric code. It can also happen if the table was dropped out-of-band, which changes the encryption key the bdec files were written with.

Verified resolution: If an Estuary Snowflake materialization using Snowpipe streaming fails with malformed name blob registration errors, check whether the destination table was altered or dropped and recreated outside of Estuary: that breaks the streaming channel's schema tracking. Do not hand-edit the materialized tables; let Estuary's schema evolution manage them. Once in this state the materialization needs a backfill to clear the recovery. Workaround for investigation: compare the table DDL against the collection schema to find the out-of-band change.

Source URL: https://github.com/estuary/connectors/issues/4030

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_TqOZsg9ylh7AJqHofsey0Q" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Estuary Snowflake Snowpipe streaming malformed blob: out-of-band ALTER TABLE <span>— Vectle</span></a>