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

allow wildcard * on a scope level #6070

Open
txp314 opened this issue Feb 6, 2023 · 2 comments
Open

allow wildcard * on a scope level #6070

txp314 opened this issue Feb 6, 2023 · 2 comments

Comments

@txp314
Copy link

txp314 commented Feb 6, 2023

Description

Hey guys,

last year at the rucio workshop in Lancaster we talked about the possibility to allow wildcards on the scope level.

By doing so queries like:
rucio list-dids --filter 'type=file' '*:some_prefix*' would be possible.

At the moment a * at the scope level is not allowed.

Motivation

If I remember correctly you said at the workshop that this is not a good idea for CERN, due to your huge number of files and scopes, which could make those kind of queries very slow and/or computationally intensive.

Nevertheless, this would be really helpful for other communities. For example in our case at a research institute for solar physics, we create a scope for every observation campaign. Within an observation campaign there is are files from different instruments, which can be distinguished by filename.

So, if we want to get all the data from an instrument no matter in which campaign we could do something like:

rucio list-dids --filter 'type=file' '*:telescopeA*'

I am sure this would be useful for others as well.

Change

The idea in Lancaster during a brief discussion on this topic was to make this feature configurable.
So the default stays the same - no wildcard searches on scopes, but if needed the wildcard search on scope level can be enabled in the configs.

I hope you consider this proposal. Thank you.

@mlassnig
Copy link
Contributor

mlassnig commented Feb 7, 2023

I think this would be a very nice extension, and should be a server side configuration option so users can't work around it :-)

@bari12
Copy link
Member

bari12 commented Feb 8, 2023

Hi Alex,
Yes this is a good idea, but needs to be made configurable as Mario said.

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

No branches or pull requests

4 participants