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

cdc: changefeed raise error "empty value is not supported" #250

Closed
pingyu opened this issue Oct 9, 2022 · 0 comments · Fixed by #277
Closed

cdc: changefeed raise error "empty value is not supported" #250

pingyu opened this issue Oct 9, 2022 · 0 comments · Fixed by #277
Labels
type/bug Something isn't working

Comments

@pingyu
Copy link
Collaborator

pingyu commented Oct 9, 2022

Bug Report

1. Describe the bug

Changefeed raise following error:
code: CDC:ErrProcessorUnknown
message: empty value is not supported

2. Minimal reproduce step (Required)

3. What did you see instead (Required)

4. What did you expect to see? (Required)

5. What is your migration tool and TiKV version? (Required)

@pingyu pingyu added the type/bug Something isn't working label Oct 9, 2022
pingyu added a commit that referenced this issue Oct 9, 2022
* patch by removing empty value check in client-go

Signed-off-by: pingyu <[email protected]>

* make CI happy

Signed-off-by: pingyu <[email protected]>

Signed-off-by: pingyu <[email protected]>
pingyu added a commit that referenced this issue Oct 28, 2022
* add empty value to IT

Signed-off-by: pingyu <[email protected]>

* add real replace; fix fmt

Signed-off-by: pingyu <[email protected]>

* set empty with []byte{} instead of nil

Signed-off-by: pingyu <[email protected]>

* prolong sleep of move_keyspan test case

Signed-off-by: pingyu <[email protected]>

* update client-go

Signed-off-by: pingyu <[email protected]>

Signed-off-by: pingyu <[email protected]>
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.

1 participant