Skip to content

Fix rendered_map_index sort order for mapped task instances#67531

Closed
manipatnam wants to merge 1 commit into
apache:mainfrom
manipatnam:fix/rendered-map-index-sort
Closed

Fix rendered_map_index sort order for mapped task instances#67531
manipatnam wants to merge 1 commit into
apache:mainfrom
manipatnam:fix/rendered-map-index-sort

Conversation

@manipatnam
Copy link
Copy Markdown
Contributor

@manipatnam manipatnam commented May 26, 2026

No description provided.

Sorting mapped task instances by rendered_map_index was producing
lexicographic order ("0","1","10","11","2") instead of numeric order
(0,1,2,...,10,11), and caused a 500 error on cursor pagination when
a CASE expression was used in to_replace.

Map rendered_map_index to the integer map_index column via a string
alias in SortParam.to_replace. This routes ORDER BY through the
integer column, fixing both the sort order and cursor pagination.

Also adds secondary_sort parameter to SortParam as generic
infrastructure for appending tiebreaker columns to ORDER BY.
@boring-cyborg boring-cyborg Bot added the area:API Airflow's REST/HTTP API label May 26, 2026
@manipatnam manipatnam closed this May 26, 2026
@manipatnam manipatnam deleted the fix/rendered-map-index-sort branch May 26, 2026 07:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:API Airflow's REST/HTTP API

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant