Invalid key properties for views after upgrading to v0.0.17

[ellisvalentiner]

After the release of v0.0.17 we began to see StreamMapConfigError fatal errors in our replication pipeline.

Example:

{
    "cmd_type": "elb",
    "consumer": false,
    "event": "singer_sdk.exceptions.StreamMapConfigError: Invalid key properties for 'qux_v': [foo,bar]. Property 'bar' was not detected in schema.",
    "job_name": "prod:tap-postgres-to-target-bigquery:2fe81bba-8465-46be-8d76-f19e9c64b121",
    "level": "info",
    "name": "tap-postgres",
    "producer": true,
    "run_id": "0f9ffca2-015c-4590-bc1c-fdf33b62ddc2",
    "stdio": "stderr",
    "string_id": "tap-postgres",
    "timestamp": "2024-11-06T13:14:36.636636Z"
}

No configuration changes were made and reverting to v0.0.16 fixed the problem.

[edgarrmondragon]

Thanks for reporting @ellisvalentiner!

[edgarrmondragon]

qq @ellisvalentiner is qux_v a view?

[ellisvalentiner]

qq @ellisvalentiner is qux_v a view?

@edgarrmondragon Yes it is a view (same behavior using a materialized view).

[edgarrmondragon]

qq @ellisvalentiner is qux_v a view?

@edgarrmondragon Yes it is a view (same behavior using a materialized view).

@ellisvalentiner gotcha, thanks for confirming!