-
Notifications
You must be signed in to change notification settings - Fork 108
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
Rucio list parent dids #9935
Rucio list parent dids #9935
Conversation
Jenkins results:
|
@germanfgv just to make sure we have the correct concept of parent in the context of Rucio.
In that case, if I call this API |
In order to list all the rules locking the parent container of a block, I will use listParentDIDs to get the parent container and then use listDataRules to get its rules. |
Sorry, I don't know how I came up with rules here(!) |
I could have created a method using both list_parent_dids and list_did_rules to directly get the parents's rules, but I decided against that. My reasoning was that being able to list parent DIDs may be useful for other purposes in RucioInjector.py, so I created listParentDIDs. @amaltaro Do you agree with this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@germanfgv code looks good to me. And I agree in separating these APIs for dids and rules too.
I asked a question in the code though, other than that it's good to go from my side.
Actually, I would ask you to implement a unit test for it. But since I'm working on a few other unit tests for this Rucio wrapper, I can take care of that.
Thanks German |
Builds towards fixing #9623
Status
ready
Description
Wrapper for Rucio API's list_parent_dids()
Is it backward compatible (if not, which system it affects?)
YES
Related PRs
As stated in #9933, we need to list parent DIDs for each block
External dependencies / deployment changes
No