Hey there! This is probably a simple fix, but what...
# troubleshooting
c
Hey there! This is probably a simple fix, but what is the recommended approach for propagating tap schema changes to target? We are extracting from Cloud SQL and going to BigQuery. Our tap recognizes new fields added in Cloud SQL, but no new columns are added in BigQuery
Here's our current yaml if that is helpful:
Copy code
version: 1
default_environment: prod
project_id: cfb52f8c-bd9f-4a26-a068-79ff66e35b1b
environments:
  - name: prod
plugins:
  extractors:
    - name: tap-postgres
      variant: meltanolabs
      pip_url: meltanolabs-tap-postgres
      config:
        filter_schemas: [public]
      metadata:
        "*":
          replication_method: INCREMENTAL
          replication_key: updated_at
      select:
        - "public-*.*"
        - "!public-alembic_version.*"
  loaders:
    - name: target-bigquery
      variant: z3z1ma
      pip_url: git+<https://github.com/z3z1ma/target-bigquery.git>
      config:
        denormalized: true
t
@Edgar Ramírez (Arch.dev) when you get a chance can you take a look here?
e
The tap's catalog may be cached, so using
meltano run --refresh-catalog tap-postgres target-bigquery
might do it
❤️ 1
c
I will try that, thank you very much!