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

bug(cassandra-sink): sink columns can be subset of target #16633

Closed
fuyufjh opened this issue May 8, 2024 · 1 comment · Fixed by #16821
Closed

bug(cassandra-sink): sink columns can be subset of target #16633

fuyufjh opened this issue May 8, 2024 · 1 comment · Fixed by #16821
Assignees
Labels
type/bug Something isn't working
Milestone

Comments

@fuyufjh
Copy link
Member

fuyufjh commented May 8, 2024

Describe the bug

The Cassandra sink asks the target table to have exactly the same set of columns as Sink. This is not consistent with other sinks: generally, the sink’s definition just need to be a subset of target table.

if (columnDescs.size() != cassandraColumnDescMap.size()) {
throw Status.FAILED_PRECONDITION
.withDescription("Don't match in the number of columns in the table")
.asRuntimeException();
}

Error message/log

ERROR:  Failed to run the query

Caused by these errors (recent errors listed first):
  1: gRPC request to meta service failed: Internal error
  2: failed to validate sink
  3: sink cannot pass validation: FAILED_PRECONDITION: Don't match in the number of columns in the table

To Reproduce

No response

Expected behavior

No response

How did you deploy RisingWave?

No response

The version of RisingWave

No response

Additional context

No response

@fuyufjh fuyufjh added the type/bug Something isn't working label May 8, 2024
@github-actions github-actions bot added this to the release-1.10 milestone May 8, 2024
@BugenZhao
Copy link
Member

Duplicated with #16607?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants