Open-EO / Open-EO/openeo-python-client
Client side local caching feature (for synchronous and/or async requests)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 217
- Forks
- 56
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
When you iterate on a usecase implementation, e.g. in jupyter, it can be annoying to have to wait for a synchronous download of a the exact same cube you already downloaded a couple of minutes ago.
The client could provide an opt-in feature to store the process graph (and some other metadata) alongside with e.g. a geotiff/netcdf download, which allows it to skip the download the next time if it sees the exact same process graph is requested.
This feature could also be provided for batch jobs: e.g. don't create a new job if client figures out a job already exists with exact the same process graph (and job options)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified in the issue. Start by tracing synchronous downloads and batch-job creation, then define how opt-in metadata matching should recognize identical process graphs and job options; done means repeated matching requests reuse cached downloads or existing jobs without creating duplicates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100