We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
After the release of v0.0.17 we began to see StreamMapConfigError fatal errors in our replication pipeline.
StreamMapConfigError
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.
The text was updated successfully, but these errors were encountered:
revert: Optimise metadata discovery for large databases
800a133
Related: - Reverts #528 - Closes #535 This reverts commit 9bb40d1.
Thanks for reporting @ellisvalentiner!
Sorry, something went wrong.
revert: Optimise metadata discovery for large databases (#536)
c436267
Related: - Reverts #528 - #535 This reverts commit 9bb40d1.
edgarrmondragon
No branches or pull requests
After the release of v0.0.17 we began to see
StreamMapConfigError
fatal errors in our replication pipeline.Example:
No configuration changes were made and reverting to v0.0.16 fixed the problem.
The text was updated successfully, but these errors were encountered: