MeltanoLabs / MeltanoLabs/tap-postgres

Invalid key properties for views after upgrading to v0.0.17

Open
#535 4 comments 1 reaction 1 assignee View on GitHub

@edgarrmondragon is already working on this.

Since Nov 7, 2024.

bug
Dominant language
Python
Stars
26
Forks
42
PR merge metrics
No merged PRs in 30d

Description

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.