Determine if including try_number in the UniqueConstraint improves index efficiency
Open
area:performance
area:task-execution-interface-aip72
- Dominant language
- Python
- Stars
- 46.9k
- Forks
- 17.8k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 483
Description
This is part of the future work of https://github.com/apache/airflow/pull/43243 that migrate TI table's primary key to be a UUID7 string
Determine if including try_number in the UniqueConstraint improves index efficiency.
Contributor guide
Research direction
Review pull request #43243 and the TaskInstance table's primary-key migration context first. Investigate whether adding try_number to the UniqueConstraint changes index efficiency, using the repository's existing database testing or benchmarking approach if applicable. Done means documenting a supported conclusion for the future UUID7-based primary key work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100