Support NULL time in First/Last/FirstBy/LastBy aggregations #17064
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:
This PR introduces robust support for NULL timestamps in FIRST, LAST, FIRST_BY, and LAST_BY aggregation functions. Previously, rows with NULL time might have been handled inconsistently or ignored.
Key Changes:
Null Time Handling Strategy:
Priority: Data with a Valid Time always takes precedence over data with a Null Time.
Fallback Policy: If only NULL time data exists, the aggregations now adopt a "First Null Wins" strategy. This means the first encountered value with a NULL timestamp is retained as the result, ensuring consistent behavior across both First and Last families.
Comprehensive Support:
Applied these changes to both standard Accumulators (for global aggregation) and GroupedAccumulators (for GROUP BY queries).
Covered all supported data types (INT32, INT64, FLOAT, DOUBLE, BINARY, BOOLEAN).