Non-breaking schema changes detected, but nothing to review, settings blocked by overlay

Connector Questions & Issues
,
1
  • Is this your first time deploying Airbyte?: Yes
  • OS Version / Instance: MacOS Ventura 13.1
  • Memory / Disk: 16G RAM, 500 GB disk
  • Deployment: Deploying locally with docker compose
  • Airbyte Version: 0.40.30 (Release v0.40.30 · airbytehq/airbyte · GitHub) as of now, use of 0.40.31 and 0.40.32 is discouraged on the Github release page, because they contain bugs.
  • Source name/version: postgres 14
  • Destination name/version: BigQuery
  • Step: Issue happening when I try to review non-breaking schema changes

I am able to successfully replicate from postgres to bigquery. However, when I visit the page for the connection settings, I see this notification: “Non-breaking schema updates detected”.

Screenshot 2023-02-11 at 10.30.18 AM
Screenshot 2023-02-11 at 10.30.18 AM1422×348 27.4 KB

When I click on “Review changes”, I briefly see this loader

Screenshot 2023-02-11 at 10.31.24 AM
Screenshot 2023-02-11 at 10.31.24 AM2118×464 12.7 KB

but then the same overlay reappears, with seemingly no action to take, no schema changes to review, and I am unable to edit replication settings.

Screenshot 2023-02-11 at 10.32.26 AM
Screenshot 2023-02-11 at 10.32.26 AM2196×1114 108 KB

I don’t see any js errors in the browser’s debugger, nor do I see any failed XHRs in the browser’s network request tab.

Here are some logs, but nothing looks terribly wrong.

airbyte-worker                    | 2023-02-11 15:33:47 INFO i.a.w.t.TemporalAttemptExecution(get):136 - Docker volume job log path: /tmp/workspace/33c16b77-e630-4930-addf-4ee893107cde/0/logs.log
airbyte-worker                    | 2023-02-11 15:33:47 INFO i.a.w.t.TemporalAttemptExecution(get):141 - Executing worker wrapper. Airbyte version: 0.40.30
airbyte-worker                    | 2023-02-11 15:33:47 INFO i.a.a.c.AirbyteApiClient(retryWithJitter):172 - Attempt 0 to save workflow id for cancellation
airbyte-worker                    | 2023-02-11 15:33:47 INFO i.a.c.i.LineGobbler(voidCall):114 - Checking if airbyte/source-postgres:1.0.42 exists...
airbyte-worker                    | 2023-02-11 15:33:47 INFO i.a.c.i.LineGobbler(voidCall):114 - airbyte/source-postgres:1.0.42 was found locally.
airbyte-worker                    | 2023-02-11 15:33:47 INFO i.a.w.p.DockerProcessFactory(create):125 - Creating docker container = source-postgres-discover-33c16b77-e630-4930-addf-4ee893107cde-0-azjxo with resources io.airbyte.config.ResourceRequirements@72c55523[cpuRequest=,cpuLimit=,memoryRequest=,memoryLimit=] and allowedHosts null
airbyte-worker                    | 2023-02-11 15:33:47 INFO i.a.w.p.DockerProcessFactory(create):170 - Preparing command: docker run --rm --init -i -w /data/33c16b77-e630-4930-addf-4ee893107cde/0 --log-driver none --name source-postgres-discover-33c16b77-e630-4930-addf-4ee893107cde-0-azjxo --network host -v airbyte_workspace:/data -v /tmp/airbyte_local:/local -e DEPLOYMENT_MODE=OSS -e USE_STREAM_CAPABLE_STATE=true -e FIELD_SELECTION_WORKSPACES= -e AIRBYTE_ROLE= -e WORKER_ENVIRONMENT=DOCKER -e APPLY_FIELD_SELECTION=false -e WORKER_JOB_ATTEMPT=0 -e WORKER_CONNECTOR_IMAGE=airbyte/source-postgres:1.0.42 -e AUTO_DETECT_SCHEMA=true -e AIRBYTE_VERSION=0.40.30 -e WORKER_JOB_ID=33c16b77-e630-4930-addf-4ee893107cde airbyte/source-postgres:1.0.42 discover --config source_config.json
airbyte-worker                    | 2023-02-11 15:33:47 INFO i.a.w.i.VersionedAirbyteStreamFactory(create):102 - Reading messages from protocol version 0.2.0
airbyte-worker                    | 2023-02-11 15:33:48 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Running source under deployment mode: OSS
airbyte-worker                    | 2023-02-11 15:33:48 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Starting source: io.airbyte.integrations.base.ssh.SshWrappedSource
airbyte-worker                    | 2023-02-11 15:33:48 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - integration args: {discover=null, config=source_config.json}
airbyte-worker                    | 2023-02-11 15:33:48 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Running integration: io.airbyte.integrations.base.ssh.SshWrappedSource
airbyte-worker                    | 2023-02-11 15:33:48 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Command: DISCOVER
airbyte-worker                    | 2023-02-11 15:33:48 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Integration config: IntegrationConfig{command=DISCOVER, configPath='source_config.json', catalogPath='null', statePath='null'}
airbyte-worker                    | 2023-02-11 15:33:48 WARN i.a.w.i.DefaultAirbyteStreamFactory(internalLog):164 - Unknown keyword order - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword
airbyte-worker                    | 2023-02-11 15:33:48 WARN i.a.w.i.DefaultAirbyteStreamFactory(internalLog):164 - Unknown keyword airbyte_secret - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword
airbyte-worker                    | 2023-02-11 15:33:48 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Starting connection with method: NO_TUNNEL
airbyte-worker                    | 2023-02-11 15:33:48 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - HikariPool-1 - Starting...
airbyte-worker                    | 2023-02-11 15:33:48 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - HikariPool-1 - Start completed.
airbyte-worker                    | 2023-02-11 15:33:49 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Checking schema: public
airbyte-worker                    | 2023-02-11 15:33:49 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Internal schemas to exclude: [catalog_history, information_schema, pg_catalog, pg_internal]
airbyte-worker                    | 2023-02-11 15:33:49 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Set initial fetch size: 10 rows
airbyte-worker                    | 2023-02-11 15:33:49 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Table schema_migrations column version (type varchar[2147483647], nullable false) -> JsonSchemaType({type=string})
airbyte-worker                    | 2023-02-11 15:33:49 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Table ar_internal_metadata column key (type varchar[2147483647], nullable false) -> JsonSchemaType({type=string})
airbyte-worker                    | 2023-02-11 15:33:49 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Table ar_internal_metadata column value (type varchar[2147483647], nullable false) -> JsonSchemaType({type=string})
airbyte-worker                    | 2023-02-11 15:33:49 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Table ar_internal_metadata column created_at (type timestamp[29], nullable false) -> JsonSchemaType({type=string, format=date-time, airbyte_type=timestamp_without_timezone})
airbyte-worker                    | 2023-02-11 15:33:49 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Table ar_internal_metadata column updated_at (type timestamp[29], nullable false) -> JsonSchemaType({type=string, format=date-time, airbyte_type=timestamp_without_timezone})
airbyte-worker                    | 2023-02-11 15:33:49 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Table order_book_entries column id (type bigserial[19], nullable false) -> JsonSchemaType({type=number, airbyte_type=integer})
airbyte-worker                    | 2023-02-11 15:33:49 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Table order_book_entries column side (type varchar[2147483647], nullable false) -> JsonSchemaType({type=string})
airbyte-worker                    | 2023-02-11 15:33:49 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Table order_book_entries column event_time (type timestamp[29], nullable false) -> JsonSchemaType({type=string, format=date-time, airbyte_type=timestamp_without_timezone})
airbyte-worker                    | 2023-02-11 15:33:49 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Table order_book_entries column product_id (type varchar[2147483647], nullable false) -> JsonSchemaType({type=string})
airbyte-worker                    | 2023-02-11 15:33:49 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Table order_book_entries column price_level (type varchar[2147483647], nullable false) -> JsonSchemaType({type=string})
airbyte-worker                    | 2023-02-11 15:33:49 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Table order_book_entries column new_quantity (type varchar[2147483647], nullable false) -> JsonSchemaType({type=string})
airbyte-worker                    | 2023-02-11 15:33:49 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Table order_book_entries column created_at (type timestamp[29], nullable false) -> JsonSchemaType({type=string, format=date-time, airbyte_type=timestamp_without_timezone})
airbyte-worker                    | 2023-02-11 15:33:49 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Table order_book_entries column updated_at (type timestamp[29], nullable false) -> JsonSchemaType({type=string, format=date-time, airbyte_type=timestamp_without_timezone})
airbyte-worker                    | 2023-02-11 15:33:49 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Found table: public.schema_migrations
airbyte-worker                    | 2023-02-11 15:33:49 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Found table: public.ar_internal_metadata
airbyte-worker                    | 2023-02-11 15:33:49 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Found table: public.order_book_entries
airbyte-worker                    | 2023-02-11 15:33:49 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - using CDC: false
airbyte-worker                    | 2023-02-11 15:33:49 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Discover primary keys for tables: [schema_migrations, ar_internal_metadata, order_book_entries]
airbyte-worker                    | 2023-02-11 15:33:49 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - HikariPool-1 - Shutdown initiated...
airbyte-worker                    | 2023-02-11 15:33:49 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - HikariPool-1 - Shutdown completed.
airbyte-worker                    | 2023-02-11 15:33:49 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - using CDC: false
airbyte-worker                    | 2023-02-11 15:33:49 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Completed integration: io.airbyte.integrations.base.ssh.SshWrappedSource
airbyte-worker                    | 2023-02-11 15:33:49 INFO i.a.w.i.DefaultAirbyteStreamFactory(internalLog):167 - Completed source: io.airbyte.integrations.base.ssh.SshWrappedSource
airbyte-worker                    | 2023-02-11 15:33:49 INFO i.a.w.t.TemporalAttemptExecution(get):163 - Stopping cancellation check scheduling...

This is possible related to 🪟Auto detect schema: Remove backdrop on non-breaking change, add toast on no refresh by edmundito · Pull Request #21998 · airbytehq/airbyte · GitHub, which is fixed in 0.40.31, but that seems more about permitting settings to be edited even if there are schema changes detected, whereas my problem seems more related to a false-positive on schema changes.

2

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
Best,
The Community Assistance Team