-
Notifications
You must be signed in to change notification settings - Fork 42
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
do not auto-add save_result when export_workspace is used #623
Labels
Comments
Indeed, there is quite some technical debt to clean up around "save_result" handling. Related tickets: |
soxofaan
added a commit
that referenced
this issue
Sep 24, 2024
started working on draft at #630 |
soxofaan
added a commit
that referenced
this issue
Sep 25, 2024
soxofaan
added a commit
that referenced
this issue
Sep 25, 2024
soxofaan
added a commit
that referenced
this issue
Sep 25, 2024
done with 58f0205 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current behaviour:
openeo-python-client/openeo/rest/datacube.py
Line 2079 in 29ae888
If last node is not save_result, then add it automatically.
Better: check the entire graph for save_result processes? If there are any, then the user probably knows what he's doing.
The text was updated successfully, but these errors were encountered: