[Project] Improve schema sync reliability

[kmcginnes]

Schema synchronization is a prerequisite to all other operations within Graph Explorer. So if it fails, the app is unusable.

There are a number of cases where schema sync can fail. Most revolve around larger databases. Some of these issues can be avoided with batching or optimized queries.

Related Issues

• Addresses [Bug] Gremlin Connector Timeout when Fetching Vertex Schema upon Database Synchronizing #225
• Addresses Can't synchronize graph database #408
• Addresses [Feature Request] Investigate if for SPARQL endpoints Service Description provides usefull statistics #400
• Addresses [Bug] 413 Payload Too Large #410

Tasks

• Setup local RDF database (BlazeGraph)
• Setup large Neptune database
• [Task] Separate node & edge count from schema sync #479
• [Task] Batch parallel requests #481
• [Task] Research suggested Gremlin query optimization #483
• [Task] Increase payload size of Express.js #484

[kmcginnes]

Removing the following task since it is covered by another project.

• [Task] Research SPARQL service description spec #482
• Project [Project] Optimize SPARQL queries #371