[BugFix/Enhancement] enable_min_max_optimization for iceberg timestamp type #67236
+66
−10
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.
Why I'm doing:
enable_min_max_optimization lacked min max meta scan for iceberg partition columns
What I'm doing:
Teach HdfsScannerContext::create_min_max_value_column to do TYPE_DATETIME
For timestamp_tz we do adjust on FE side, since it is FE who reads meta bounds and BE can't access them. Can redo in favor of addind is_adjusted_to_utc to TExprMinMaxValue in thrift. But wanted to keep it simpler.
Fixes #67158
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist:
Bugfix cherry-pick branch check: