-
Notifications
You must be signed in to change notification settings - Fork 94
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
Active Node-Edge N-Distance GraphQL Query #3248
Comments
Just to flag something which is kinda tricky with this approach is dealing with graph isolates e.g: [scheduling]
cycling mode = integer
initial cycle point = 1
[[dependencies]]
[[[P1]]]
graph = """
foo[-P1] => foo => bar => baz
pub # graph isolate
""" |
Yes, could be tricky. Although, if the isolates are active ( |
I believe we are aiming for Cylc 8 here @matthewrmshin! |
This is in reference to the desired HYBRID mode noted in the Exeter-June-2019 meeting, and as a solution could present a way of masking the Cylc 8 to 9 backend transition.
To create a query to return that active task/job-edge view:
level
ordistance
(i.e. geodesic distance, because level implies a tree?).D0
(distance
=0) nodes, then loop on all edges to collect edges and nodes (D1
) who are the source or target ofD0
... Repeat forD1..N
If we think that resolver would be too computationally expensive, then for every node we could store edges that connect to it, as either source or target, in a list field of that node.
(by store I mean the edge IDs of course)
The text was updated successfully, but these errors were encountered: