[Project] Improve neighbor count query experience

[kmcginnes]

Neighbor counts are queried when a node is added to the graph. This can be from search or through expansion.

Sometimes these queries take a long time or fail. The UI currently does not surfaces these errors to the user and the progress reporting is inconsistent.

The neighbor count queries can also be taxing to the graph database server. Typically, a request per node added to the graph will be executed. This can amount to hundreds of requests executed in parallel. This can be improved with batching or combining multiple queries together. And many of the neighbor count queries are inefficient and can be improved.

Related Issues

• Addresses [Feature Request] Handle errors in keyword search better #256
• Addresses [Bug] Value in "Limit returned neighbors to" is exceeded (SPARQL ENDPOINT) #184
• Addresses [Bug] RDF: Adding resource to the canvas is very slow or fails with out of memory #263
• Partially addresses [Bug] Neighbor expansion is slow and unreliable #324
• Partially addresses [Feature Request] Retry failed requests #269
• Partially addresses [Feature Request] Improve SPARQL query performance #240
• Partially addresses [Project] Optimize database queries #358
• Partially addresses [Project] Database queries should use React Query #304

Tasks

• [Task] Wrap fetchNeighbors in React Query #338
• [Task] Wrap fetchNeighborsCount in React Query #339
• [Task] Add spinner and error state to sidebar for expansion and node counts #438
• [Task] Optimize the Gremlin query for neighbors #380
• [Task] Optimize the Gremlin query for neighbor types and count #342
• [Task] Optimize the openCypher query for neighbor types and count #388
• [Task] Optimize the openCypher query for neighbors #389
• [Task] Optimize the SPARQL query for neighbor types and count #344
• [Task] Optimize the SPARQL query for neighbors #384
• [Task] Add expansion limit option per connection #442
• [Task] Improve label of proxy options in connection #444
• [Task] Gather metrics on query improvements #459

---

Tip

Please use a 👍 reaction to provide a +1/vote.

This helps the community and maintainers prioritize this request.

Important

If you are interested in working on this issue or have submitted a pull request, please leave a comment.

[kmcginnes]

Closing this project since the remaining open tickets are tracked by another project:

• [Project] Optimize SPARQL queries #371