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

Scope of output datasets in task metadata? #30

Open
MoAly98 opened this issue Mar 22, 2024 · 0 comments
Open

Scope of output datasets in task metadata? #30

MoAly98 opened this issue Mar 22, 2024 · 0 comments

Comments

@MoAly98
Copy link

MoAly98 commented Mar 22, 2024

Hi,

I was just wondering if there is an existing way to extract the scope of an output dataset associated with some panda task?

I have a code where I want to be able to extract containers associated to a grid task then access that container with the Rucio API. Rucio API expects the scope of the container/dataset to be given (afaik), but panda-client does not store the scope of the output dataset in the task metadata (again, afaik). Currently the "hack" is to figure out the scope from the "official" ordering of user.xxx or group.xxx at the start of container name but I want to generalise this. The scope is stored for the input dataset as part of the "datasetname" field, which shows as scope:mydataset. Can this be done also for output datasets?

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

No branches or pull requests

1 participant