-
Notifications
You must be signed in to change notification settings - Fork 9
Roadmap
Jordan Matelsky edited this page Oct 14, 2020
·
2 revisions
Features that will exist, someday.
Status | Description |
---|---|
🤔 | Currently under development |
⏳ | No plans to implement yet |
Attributes derived from the graph, not from the data (e.g. degree, betweenness centrality, etc)
A.!degree > 5
A -> B
degree{my_node} > 5
To represent an unknown number of intermediate nodes before reaching a final destination.
All examples represent the following, where dont_care_B
and dont_care_C
are omitted:
A -> dont_care_B
dont_care_B -> dont_care_C
dont_care_C -> D
A -(2)-> D
With attributes:
A -(2 [weight > 4])-> D
When making a query, allow the user to notate that they want the query to also return the edge/node metadata attributes that satisfy the constraints:
X -> Y [weight > 4]
X.type != excitatory
Here, we want to notate that we care about X.type
and [XY].weight
, and that the returned table should look like:
X | Y | [XY].weight | X.type |
---|
Instead of just containing X and Y headers.
Desired attributes can be signified with an asterisk:
X -> Y [weight > 4]
X.type != excitatory
+[XY].weight
+X.type