Fix inaccurate references to prepared statement header#12641
Merged
martint merged 1 commit intotrinodb:masterfrom Jun 1, 2022
Merged
Fix inaccurate references to prepared statement header#12641martint merged 1 commit intotrinodb:masterfrom
martint merged 1 commit intotrinodb:masterfrom
Conversation
mosabua
approved these changes
Jun 1, 2022
v-jizhang
added a commit
to v-jizhang/presto
that referenced
this pull request
Jun 2, 2022
Cherry-pick of trinodb/trino#12641 Co-authored-by: Colebow <cole.bowden@starburstdata.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
The header here is X-Trino-Prepared-Statement, but a couple references say that it is X-Trino-Prepared-Statements, which is wrong. This fixes that.
Fix
Docs
Documentation
( ) No documentation is needed.
(x) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.
Release notes
(x) No release notes entries required.
( ) Release notes entries required with the following suggested text: