You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When doing save_result => export_workspace,
the data is stored once in default location and once in workspace.
This is problematic for huge processing jobs, because we will have to pay for the storage.
The text was updated successfully, but these errors were encountered:
@jdries What are the implications from the user's point of view? Does this mean that the STAC Collection of batch job results has no items then (also because OpenEO won't be able to serve the assets anymore)?
or can we make those items point to the location where we exported the results to?
If complex, the main thing to achieve here is simply that the file is gone, potentially triggered by a feature flag or job option if the impact is too unpredictable.
When doing save_result => export_workspace,
the data is stored once in default location and once in workspace.
This is problematic for huge processing jobs, because we will have to pay for the storage.
The text was updated successfully, but these errors were encountered: