Fix federation query binary type data query #31346
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.
Fixes #31247.
Changes proposed in this pull request:
Fix federated query failed to get binary type data, test single projection column and multiple projection column queries in e2e federated query scenario.
In the MetaData assertion test for the federated query scenario, the assertion test for the ColumnType is skipped, and mysql makes some implicit transformations to the query result according to the type. Obtained through SQLFederationResultSetMetaData ColumnType is difficult with mysql ColumnType consistent.
Before committing this PR, I'm sure that I have checked the following options:
./mvnw clean install -B -T1C -Dmaven.javadoc.skip -Dmaven.jacoco.skip -e
.