Skip to content

STACAPIJobDatabase.get_by_status() does not always return pandas.DataFrame with monotonic increasing index #707

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
VincentVerelst opened this issue Jan 15, 2025 · 0 comments
Assignees

Comments

@VincentVerelst
Copy link
Collaborator

The order of the indices pandas.DataFrame in STACAPIJobDatabase.get_by_status() is the same as the order of indices in the STAC collection. This is not necessarily monotic increasing. However, the MultiBackendJobManager requires monotonic increasing indices in the DataFrame, e.g.:

job_db.persist(not_started.loc[i : i + 1])

@VincentVerelst VincentVerelst self-assigned this Jan 15, 2025
VincentVerelst added a commit that referenced this issue Feb 21, 2025
…e index, but rather from item_id column; which is created if it doesn't exist #707
VincentVerelst added a commit that referenced this issue Feb 26, 2025
soxofaan pushed a commit that referenced this issue Feb 27, 2025
* STACAPIJobDatabase.get_by_status() sorts df on index #707

* STACAPIJobDatabase: item ID is no longer derived from pandas.DataFrame index, but rather from item_id column; which is created if it doesn't exist #707

* created STACAPIJobDatabase._normalize_df() method #707

* update changelog for #707
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants