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
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?
The text was updated successfully, but these errors were encountered:
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
orgroup.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 asscope:mydataset
. Can this be done also for output datasets?The text was updated successfully, but these errors were encountered: