release-21.2: sql: preserve tuple types when decoding #70392
Merged
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 #70375 on behalf of @jordanlewis.
/cc @cockroachdb/release
Fixes #70360
Previously, when decoding tuples sent across the wire in DistSQL, tuple
labels were not preserved due to an oversight.
This oversight is now corrected, and tuple labels are now properly
preserved in all queries.
Release note (bug fix): fix a bug preventing tuple type labels from
being propagated across queries when run under DistSQL.
Release justification: