release-23.2: changefeedccl: fix custom key column when used with CDC queries #116967
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport 1/1 commits from #115163 on behalf of @wenyihu6.
/cc @cockroachdb/release
Previously, CDC custom key column caused incorrect behaviour with CDC queries,
leading to a
retryable error: No column with name <name> in this row
. This wasbecause we forgot to add columns to
colsByName
map when generating projectionrows for CDC queries. This caused
DatumNamed
to return a column not found error. This patch addresses the issue by populating
the
colsByName
map during the addition of columns for CDC queries. Note thatthe issue with supporting
ALTER CHANGEFEED
with CDC queries remainsunresolved.
Fixes: #114196
Release note (bug fix): CDC custom key column now functions with CDC queries
correctly. For example,
CREATE CHANGEFEED WITH key_column=..., unordered AS SELECT * FROM table
now works correctly instead of retrying forever. Note thatsome functionalities with CDC custom keys are not fully supported, see 115267
for more details.
Release justification: bug fixes for CDC custom key column when used with CDC queries