HIVE-28744: fix INT_TYPE and BIGINT_TYPE range estimate values #5637
+2
−2
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.
What changes were proposed in this pull request?
Fix
INT
andBIGINT
type column range statistics estimate values.Why are the changes needed?
When
hive.stats.estimate
andhive.stats.fetch.column.stats
are enabled and Int or bigint columns don't have col stats about ranges, incorrect ranges are used in the query plan, which returns the wrong num rows.e.g) If
{BIGINT Type col} > INTEGER.MAX_VALUE
is in query, estimated numRows is always 0.{BIGINT Type col} > INTEGER.MAX_VALUE
, and EXPLAIN it.Does this PR introduce any user-facing change?
No
Is the change a dependency upgrade?
No
How was this patch tested?