I am using the Looker source connector to get data from a specific Look. In order to have access to the data, it was required to read data directly from the raw internal table. After the upgrade of the Snowflake destination to 4.0 and enabling the Legacy raw tables option, the _`_airbyte_data`_ column is empty. Is there a way to fix this? I have all the rows but no values

I'm sorry, but the knowledge sources do not contain enough information to directly address the specific issue of the

_airbyte_data

column being empty after upgrading to Snowflake destination v4.0 with Legacy raw tables enabled. However, there are a few relevant points I can share based on the available information: Known Issue with Legacy Raw Tables in v4.0 There is an open bug reported for Snowflake destination v4.0 when the Legacy raw tables option is enabled. The issue involves a column mismatch during the connection check, where test data is incorrectly placed in the

_airbyte_loaded_at

column. This suggests there may be broader data handling issues in Legacy raw tables mode in this version. [GitHub Issue] What Changed in v4.0 The upgrade to v4.0 moved Snowflake to the Direct-Load paradigm. Key changes relevant to your situation: [Snowflake Migration Guide] • The

Legacy raw tables

option is the equivalent of the old

Disable Final Tables

option — the connector will only write raw tables and will not create final tables. • The connector no longer supports writing both raw and final tables in a single connection. If you need both, you must configure two separate destinations. [Direct Load Tables] Recommended Next Steps 1. Check the open bug: The issue at GitHub #71261 appears to be actively tracked by the Airbyte team. You may want to add your findings there. 2. Try without Legacy raw tables: If your use case allows, test with Legacy raw tables disabled to see if data populates correctly in the final tables. 3. Contact Airbyte support: Given this appears to be a regression bug in v4.0, reaching out to Airbyte support or commenting on the GitHub issue would be the best path to a fix. The knowledge sources do not provide a confirmed workaround for the empty

_airbyte_data

column specifically. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai When I run the connector locally, I can see the records but when running via Airbyte, all the rows on the internal table are empty

The knowledge sources do not contain enough information to specifically address why records appear correctly when running the connector locally but show empty rows in the internal raw table when running via Airbyte. What I can confirm from the knowledge sources is that there is an open bug with the Snowflake destination v4.0.32 when the Legacy raw tables option is enabled, where data is being incorrectly handled during the connection check — specifically, a column mismatch causes test values to be placed in the wrong column position. [GitHub Issue] This behavior difference between local and Airbyte-managed runs could be related to this known regression, but I cannot confirm that with certainty based on the available information. I'd recommend: 1. Adding your findings to the open GitHub issue at #71261, as the Airbyte team is actively investigating it. The more detail you can provide (connector version, exact behavior, logs), the better. 2. Checking your connector version — if you're on v4.0.32, this is the version with the known bug. 3. As a temporary workaround, consider disabling the Legacy raw tables option if your use case allows it, to see if data populates correctly. For a definitive answer, I'd suggest reaching out directly to Airbyte support or the GitHub issue thread. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.