Open-EO / Open-EO/openeo-python-driver
consistent behavior default_job_options in UDP
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 8
- Avg merge
- 6d 3h
- Merged PRs (30d)
- 4
Description
Currently the default_job_options are only used when the UDP is executed as a process.
When created a datacube from the Json and creating a job, the default job options are not used.
This is somewhat inconsistent behavior as we strive to have standardization with UDPs
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
Start by tracing default_job_options through UDP process execution and through datacube creation from JSON followed by job creation. Compare the two paths and use the linked discussion to clarify the intended standardized behavior; done means default job options are applied consistently in both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100