Support for remote JanusGraph (gremlin server) for Egeria local graph repository

[lpalashevski]

Currently, local Egeria graph repository connector is using graph instances via embedded JanusGraph library.

As discussed on the previous community calls, support for remote JanusGraph connector is needed in order to be able to deploy Egeria as repository in a resilient and scaleable deployment scenario for production.

• Access multiple graph instances in separate active nodes of Janus Graph servers improving resilience;
• Possibility to load balance between active graph instances allowing the graph to scale and handle increased load;

[lpalashevski]

Known changes that will impact already existing embedded implementation:

• Graph instance is not available on the client side; graph instances are managed on the server and the client code can do remote connection for traversals using Cluster object from Gremlin driver.
• No direct transaction management is possible when executing queries remotely (default behaviour is that every traversal is executed in a dedicated transaction on the server); This means the queries should be adjusted accordingly.
• Schema management using Janus Management API can be done by invoking remote requests using the Client form Gremlin driver; All the schema management calls, creating labels, indexes, reindexing can be done in the same way but on the server side by sending text commands as request.

[lpalashevski]

The change for open lineage connector implemented with this PR https://github.com/odpi/egeria/pull/3266

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.