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

Postgres CDC cannot match primary keys with capitalized names #16677

Closed
neverchanje opened this issue May 10, 2024 · 0 comments · Fixed by #16793
Closed

Postgres CDC cannot match primary keys with capitalized names #16677

neverchanje opened this issue May 10, 2024 · 0 comments · Fixed by #16793
Assignees
Labels
need-cherry-pick-release-1.9 Open a cherry-pick PR to branch release-1.8 after the current PR is merged type/bug Something isn't working
Milestone

Comments

@neverchanje
Copy link
Contributor

neverchanje commented May 10, 2024

Describe the bug

PG:

create table person (
  "Id" int,
  "name" varchar(64),
  "email_address" varchar(200),
  "credit_card" varchar(200),
  "city" varchar(200),
  PRIMARY KEY ("Id")
);

RW:

create table person (
    "Id" int,
    "name" varchar,
    "email_address" varchar,
    "credit_card" varchar,
    "city" varchar,
    PRIMARY KEY ("Id")
) with (
    connector = 'postgres-cdc',
    hostname = 'postgres',
    port = '5432',
    username = 'myuser',
    password = '123456',
    database.name = 'mydb',
    schema.name = 'public',
    table.name = 'person',
    slot.name = 'person'
);

The primary key is 'Id' in both Postgres and RW. However, the source failed to create:

Error message/log

source cannot pass validation: INVALID_ARGUMENT: Primary key mismatch

How did you deploy RisingWave?

integration_tests/postgres-cdc

The version of RisingWave

origin/v1.8.1+Npgsql

Additional context

No response

@neverchanje neverchanje added the type/bug Something isn't working label May 10, 2024
@github-actions github-actions bot added this to the release-1.10 milestone May 10, 2024
@neverchanje neverchanje added the need-cherry-pick-release-1.9 Open a cherry-pick PR to branch release-1.8 after the current PR is merged label May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need-cherry-pick-release-1.9 Open a cherry-pick PR to branch release-1.8 after the current PR is merged type/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants