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

Support queries in remote zones #329

Open
alanking opened this issue Nov 11, 2022 · 2 comments
Open

Support queries in remote zones #329

alanking opened this issue Nov 11, 2022 · 2 comments
Assignees
Milestone

Comments

@alanking
Copy link

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.

@trel
Copy link
Contributor

trel commented Nov 12, 2022

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...

@korydraughn korydraughn self-assigned this Nov 13, 2022
@korydraughn korydraughn added this to the 2.6.1 milestone Nov 13, 2022
@korydraughn korydraughn modified the milestones: 2.6.1, 3.0.0 Jan 23, 2023
@JustinKyleJames
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants