Hi
As a follow up to my talk last week, I would like to start a discussion on this topic about redesign the Schema Management.
General idea is to deprecated direct access to JanusGraph server using other things than a gremlin client/driver, such as the ManagementSystem or StandardJanusGraph.
Main advantage, we can change internally core components without having breaking changes in our front facing api.
I started to work on the first precondition to reduce the requirements to access a janusgraph instance using a java/groovy gremlin client/driver. PR: https://github.com/JanusGraph/janusgraph/pull/1521
Idea of an implementation order:
Any thoughts?
Greetings
Jan
—— “We strongly encourage all users of JanusGraph to use the Gremlin query language for any queries executed on JanusGraph and to not use JanusGraph’s APIs outside of the management system.“
--
You received this message because you are subscribed to the Google Groups "JanusGraph developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-de...@googlegroups.com.
To post to this group, send email to janusgr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/39FD5214-025E-4E07-B548-27D62E4D2BB8%40gdata.de.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "JanusGraph developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-de...@googlegroups.com.
To post to this group, send email to janusgr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/af141fb1-fe85-41fc-99cc-ea2974e2d31f%40googlegroups.com.