Open-EO / Open-EO/openeo-python-driver
non-API compliant UDP vs pre-defined process precedence
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 8
- Avg merge
- 6d 3h
- Merged PRs (30d)
- 4
Description
See first commit in this issue, due to a major performance and robustness problem in operations, I now gave predefined processes precedence over udp's. This avoids expensive udp lookups.
We need to further improve upon this quick solution.
Either we respect the API, and implement some caching of UDP names in the registry. This would not be super difficult, and allows us to respect the API.
The other solution is to double check if a user saves a udp, if the name is perhaps not a predefined process name, and throw an error instead of storing the UDP. That would make our backend more strict than what the API prescribes, but avoids ugly situations. I prefer this solution.
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 reviewing the first commit in this issue and the current handling of UDP names versus predefined processes. Compare the two proposed approaches against the API behavior and operational performance; done means the chosen approach is implemented and the precedence or validation behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100