[multistage] disable calcite float to double cast #11518
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.
Map float and double to the same RelDataType to disable calcite float to double cast so that queries like
select count(*) from table where aFloatColumn = 0.05works correctly in multi-stage query engine.Without this PR,
select count(*) from table where aFloatColumn = 0.05will be converted toselect count(*) from table where CAST(aFloatColumn as "DOUBLE") = 0.05. While casting from float to double does not always produce the same double value as the original float value, this leads to wrong query result.With this PR, the behavior in multi-stage query engine will be the same as the query in v1 query engine.