@kapa.ai i am creating a connection from jira to snowflake with airbyte for stream of issue_remote_links but i am getting one error in the logs

INFO sync-operations-1 i.a.i.b.d.t.TyperDeduperUtil(runMigrationsAsync$lambda$12):165 Maybe executing SnowflakeDV2Migration migration for stream AIRBYTE_JIRA_SCHEMA_SEP_24.issue_remote_links.
2025-12-30 12:19:37 destination INFO sync-operations-1 i.a.i.d.s.m.SnowflakeDV2Migration(migrateIfNecessary):32 Initializing DV2 Migration check
2025-12-30 12:19:37 destination INFO sync-operations-1 i.a.i.b.d.t.BaseDestinationV1V2Migrator(migrateIfNecessary):19 Assessing whether migration is necessary for stream ISSUE_REMOTE_LINKS
2025-12-30 12:19:37 destination INFO sync-operations-1 i.a.i.b.d.t.BaseDestinationV1V2Migrator(shouldMigrate):43 Checking whether v1 raw table _airbyte_raw_issue_remote_links in dataset AIRBYTE_JIRA_SCHEMA_SEP_24 exists
2025-12-30 12:19:38 destination INFO sync-operations-1 i.a.c.d.j.DefaultJdbcDatabase(unsafeQuery$lambda$6):127 closing connection
2025-12-30 12:19:38 destination WARN sync-operations-1 i.a.c.d.j.DefaultJdbcDatabase(unsafeQuery):138 closing connection because of an Exception net.snowflake.client.jdbc.SnowflakeSQLException: SQL compilation error:
Table 'SPX_DB."airbyte_internal"."AIRBYTE_JIRA_SCHEMA_SEP_24_raw__stream_issue_remote_links"' does not exist or not authorized.
	at net.snowflake.client.jdbc.SnowflakeUtil.checkErrorAndThrowExceptionSub(SnowflakeUtil.java:176) ~[snowflake-jdbc-3.20.0.jar:3.20.0]
	at net.snowflake.client.jdbc.SnowflakeUtil.checkErrorAndThrowException(SnowflakeUtil.java:109) ~[snowflake-jdbc-3.20.0.jar:3.20.0]
	at net.snowflake.client.core.StmtUtil.pollForOutput(StmtUtil.java:490) ~[snowflake-jdbc-3.20.0.jar:3.20.0]
	at net.snowflake.client.core.StmtUtil.execute(StmtUtil.java:396) ~[snowflake-jdbc-3.20.0.jar:3.20.0]
	at net.snowflake.client.core.SFStatement.executeHelper(SFStatement.java:498) ~[snowflake-jdbc-3.20.0.jar:3.20.0]
	at net.snowflake.client.core.SFStatement.executeQueryInternal(SFStatement.java:215) ~[snowflake-jdbc-3.20.0.jar:3.20.0]
	at net.snowflake.client.core.SFStatement.executeQuery(SFStatement.java:149) ~[snowflake-jdbc-3.20.0.jar:3.20.0]
	at net.snowflake.client.core.SFStatement.execute(SFStatement.java:786) ~[snowflake-jdbc-3.20.0.jar:3.20.0]
	at net.snowflake.client.core.SFStatement.execute(SFStatement.java:693) ~[snowflake-jdbc-3.20.0.jar:3.20.0]
	at net.snowflake.client.jdbc.SnowflakeStatementV1.executeQueryInternal(SnowflakeStatementV1.java:297) ~[snowflake-jdbc-3.20.0.jar:3.20.0]
	at net.snowflake.client.jdbc.SnowflakePreparedStatementV1.executeQuery(SnowflakePrep

does this table creation is mandatory

The knowledge sources don’t describe this exact SnowflakeDV2Migration log line or explicitly say whether that specific raw table must exist, so I can’t give a definitive, implementation‑level answer. I can, however, explain what the docs do say that’s relevant. 1. Raw tables and Destinations V2 / migrations - With Destinations V2, Airbyte uses raw tables (by default in the

airbyte_internal

schema) as staging for Typing & Deduping, and migrations may look for legacy raw tables when upgrading table layouts. [[Raw tables upgrade](https://docs.airbyte.com/release_notes/upgrading_to_destinations_v2#upgrading-as-a-user-of-raw-tables); [Snowflake migration](https://docs.airbyte.com/integrations/destinations/snowflake-migrations)] - For Snowflake, upgrading to Destinations V2 and then to Direct Load changes how raw vs final tables are handled; there are options like “Disable Final Tables” / “Legacy raw tables” that control whether raw tables are created and used. [[Snowflake migration](https://docs.airbyte.com/integrations/destinations/snowflake-migrations)] 2. Is that specific raw table “mandatory”? The docs do not explicitly state that a table named exactly:

text    SPX_DB."airbyte_internal"."AIRBYTE_JIRA_SCHEMA_SEP_24_raw__stream_issue_remote_links"

must exist for the Jira → Snowflake sync to work, nor do they document the SnowflakeDV2Migration behavior for a single stream. So I can’t say with certainty that its creation is always mandatory. What the docs do say: - Raw tables are considered an internal staging layer whose structure and location can change, and Airbyte does not guarantee long‑term stability of raw tables. [[Raw tables upgrade](https://docs.airbyte.com/release_notes/upgrading_to_destinations_v2#upgrading-as-a-user-of-raw-tables)] - When upgrading/migrating, Airbyte may create new raw tables in

airbyte_internal

and leave old ones in place; downstream processes should not rely on specific raw table names. [[Raw tables upgrade](https://docs.airbyte.com/release_notes/upgrading_to_destinations_v2#upgrading-as-a-user-of-raw-tables); [Postgres migration](https://docs.airbyte.com/integrations/destinations/postgres-migrations)] That suggests: - The migration code expects to be able to query a v1 raw table; if it can’t see it (doesn’t exist or no permission), it logs an error like the one you’re seeing. - Whether this is fatal or just a warning depends on the connector version and configuration, but the docs don’t say. 3. What you can safely check, based on docs From the available documentation, the only concrete, supported checks are: - Permissions / schema existence: Ensure the Snowflake user and role configured in the destination have access to the

airbyte_internal

schema and can create/read tables there. [[Snowflake getting started](https://docs.airbyte.com/integrations/sources/snowflake#getting-started); [Snowflake migration](https://docs.airbyte.com/integrations/destinations/snowflake-migrations)] - Destination options: Verify whether you have any options enabled that change raw/final table behavior (e.g., “Disable Final Tables”, “Legacy raw tables” for Snowflake), since those control whether raw tables are created and how migrations behave. [[Snowflake migration](https://docs.airbyte.com/integrations/destinations/snowflake-migrations)] Because the knowledge sources don’t document this exact migration path or error, I can’t say more precisely whether you can safely ignore it or must ensure that particular raw table exists. If the sync is failing (not just logging a warning), the next step—outside what’s covered in the docs—would be to: - Confirm whether any

_airbyte_raw_*issue_remote_links*

table exists in

airbyte_internal

. - Double‑check Snowflake role/database/schema permissions. - If the problem persists, open a topic on the Airbyte forum with the full log and your destination configuration, as recommended for Jira/Snowflake troubleshooting. [[Jira troubleshooting](https://docs.airbyte.com/integrations/sources/jira#troubleshooting)]