BDP-25893: OH table PARTITIONED BY DATE #278
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.
Summary
Before this PR, OH didn't support following SQL:
After this PR, it does.
Details
OH server achieves this by considering DATE as a clustering column, just like string (say with value "2025-01-01").
There was a design choice to consider DATE as a timestamp column, but it would require major redesign on our REST TimeSpec APIs. Considering as a clustering column, doesn't miss-out on any optimization strategies.
Changes
For all the boxes checked, please include additional details of the changes made in this pull request.
Testing Done
✅ Added unit tests
✅ Build succeeds
For all the boxes checked, include a detailed description of the testing done for the changes made in this pull request.
Additional Information
For all the boxes checked, include additional details of the changes made in this pull request.