Actually, this is not quite true. If you really want it, you can start the server readonly and disabling caches in order to to get stale data by setting it in neo4j.properties as
read_only = true cache_type = none see http://docs.neo4j.org/chunked/snapshot/operations-monitoring.html#_jmx (just added the clear() to the docs, will come up in some minutes through the build process) This will, however, result in exceptions being thrown in the mutating operations on REST level. Another way to trigger a readonly mode updating the cache is to use JMX. There is a cache.clear() method that you can trigger, making the REST readonly instance eventually consistent (refreshing) at intervals you decide. Code is something along the lines of Neo4jManager manager = new Neo4jManager( graphDb.getManagementBean( Kernel.class ) ); long nodeIDsInUse = manager.getCacheBean().clear(); And of course you can call that via JMX remotely from your inserting system. Would that be something of use? Cheers, /peter neubauer GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer http://www.neo4j.org - Your high performance graph database. http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party. On Wed, Jan 19, 2011 at 10:11 PM, Jim Webber <[email protected]> wrote: > Hi Hemant, > > Bringing up the REST API in readonly mode is not possible I'm afraid. > > We could consider adding it to the Neo4j server, depending on the effort > required and whether there are other workarounds. > > Jim > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
