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
As far as I understand/see the web editor requests "all user jobs" without limit/paging. We started noticing that this causes issues in practice as it is not uncommon for some larger users to work with hundreds/thousands of jobs.
We started implementing the paging feature in the components of the Geopyspark backend, but as noted in Open-EO/openeo-api#550, pagination is unfortunately client-driven at the moment, so with this feature request we'd like to see this being adopted in the web editor
The text was updated successfully, but these errors were encountered:
Also, this probably should be consistently implemented, i.e. also for files, UDPs and web services.
Collections
Collection Items
Processes
Batch Jobs
UDP
Files
Secondary web services
Logs
Related note: We need to discuss how the search field should work if not all pages are loaded yet. Users may expect that is searches all entries although not all of them may have been loaded yet so that the Editor can't search through them.
As far as I understand/see the web editor requests "all user jobs" without limit/paging. We started noticing that this causes issues in practice as it is not uncommon for some larger users to work with hundreds/thousands of jobs.
We started implementing the paging feature in the components of the Geopyspark backend, but as noted in Open-EO/openeo-api#550, pagination is unfortunately client-driven at the moment, so with this feature request we'd like to see this being adopted in the web editor
The text was updated successfully, but these errors were encountered: