Bugfix/9174 no time column dataset download - #298
Merged
utas-raymondng merged 8 commits intoSep 15, 2026
Merged
Conversation
shaunahu
marked this pull request as ready for review
September 15, 2026 04:01
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
At init, if every requested key has no time column and is hive-partitioned by polygon, the job lists the polygon partition values from directory names only. It sorts them and cuts them into half-open ranges
[lo, hi)(same logic as date split), withget_polygon_count_per_job() = 20partitions per child job. These ranges replacedate_rangesas the array job parameter, passed aspolygon_ranges. Every other dataset still uses the date-range workflow, unchanged.