Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid key properties for views after upgrading to v0.0.17 #535

Open
ellisvalentiner opened this issue Nov 6, 2024 · 1 comment
Open
Assignees
Labels
bug Something isn't working

Comments

@ellisvalentiner
Copy link

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
Copy link
Member

Thanks for reporting @ellisvalentiner!

edgarrmondragon added a commit that referenced this issue Nov 7, 2024
@edgarrmondragon edgarrmondragon self-assigned this Nov 7, 2024
@edgarrmondragon edgarrmondragon added the bug Something isn't working label Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Development

No branches or pull requests

2 participants