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 have some data and I want to automatically create a graph from it and then query that graph. I know my graph root node's original ID, so I can use the feature added here https://github.inl.gov/Digital-Engineering/DeepLynx/pull/298, awesome! But conceivably, my container could contain more than one node that has this same root node original ID. However, if graph query filters were added for root_node_data_source_id, and root_node_metatype_id it would solve this potential issue. You could confidently query a graph by original node ID, and be sure that your root node is actually what you think it is. And you could also get results for a graph that spans more than one data source.
Impact
More graph query functionality, making it easier for users and reducing their need for post processing graph query results.
The text was updated successfully, but these errors were encountered:
Use Case
I have some data and I want to automatically create a graph from it and then query that graph. I know my graph root node's original ID, so I can use the feature added here https://github.inl.gov/Digital-Engineering/DeepLynx/pull/298, awesome! But conceivably, my container could contain more than one node that has this same root node original ID. However, if graph query filters were added for root_node_data_source_id, and root_node_metatype_id it would solve this potential issue. You could confidently query a graph by original node ID, and be sure that your root node is actually what you think it is. And you could also get results for a graph that spans more than one data source.
Impact
More graph query functionality, making it easier for users and reducing their need for post processing graph query results.
The text was updated successfully, but these errors were encountered: