I ended up using Cypher using neo4j-jdbc to handle scheduled updates. This can be done while the Graph DB is still running. Unlike the embedded graphdb which requires the graph db to be stopped while performing the updates.
However, Cypher is more verbose than using Embedded graph db API On Friday, January 15, 2016 at 6:34:46 PM UTC-5, Roopa ML wrote: > > Hi, > > I want to know the best practice to create a graph database. > That is creating nodes, relationship between nodes. > > Right now we are using batch importer. However this cannot be used > periodically on production system since we need to shutdown the database. > > Hence what are the options for creating and periodically updating a graph > database? > > Thanks > -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
