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
It is possible to navigate to collections and data objects in a remote zone which is federated with the zone to which the Metalnx service is connected. It is not possible to run queries in said zones, hindering data discovery. There should be an option for running queries similar to the -z option for iquest which specifies the zone in which the query is to be run.
The text was updated successfully, but these errors were encountered:
I would suggest a multi-select option in a federated deployment... with the default being the local zone, but a sticky preference being available to the user in the preferences settings.
If 'all zones' is a thing that is interesting, then we have to consider the paging logic of the results. Or we open a new tab with results from each selected zone, each with its own paging...
We discussed this and decided to move it to milestone 3.0.0 because the solution will require some UI changes to properly handle paging.
Either the query will be per zone or the results will be in separate tabs by zone. There is not a clean way to stitch a large result set into a clean pageable list.
It is possible to navigate to collections and data objects in a remote zone which is federated with the zone to which the Metalnx service is connected. It is not possible to run queries in said zones, hindering data discovery. There should be an option for running queries similar to the
-z
option foriquest
which specifies the zone in which the query is to be run.The text was updated successfully, but these errors were encountered: