Skip to content
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

export_workspace: skip writing to local storage #883

Open
jdries opened this issue Sep 26, 2024 · 2 comments · May be fixed by #903
Open

export_workspace: skip writing to local storage #883

jdries opened this issue Sep 26, 2024 · 2 comments · May be fixed by #903
Assignees

Comments

@jdries
Copy link
Contributor

jdries commented Sep 26, 2024

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.

@bossie
Copy link
Collaborator

bossie commented Oct 1, 2024

@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)?

@jdries
Copy link
Contributor Author

jdries commented Oct 1, 2024

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.

bossie added a commit that referenced this issue Oct 11, 2024
@bossie bossie linked a pull request Oct 11, 2024 that will close this issue
@bossie bossie linked a pull request Oct 11, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants