On Tue, Dec 28, 2010 at 17:05, Peter Neubauer
wrote:
> is there anything we need to change in the Neo4j
> REST API before 1.2 in order to be done here?
I'm not sure, but I think the new plugins feature exposes URL's with
hyphens instead of underscores.
> It seems the only thing
> required here a
All,
is this ok now, and is there anything we need to change in the Neo4j
REST API before 1.2 in order to be done here? It seems the only thing
required here are changes on the Python side?
Cheers,
/peter neubauer
GTalk: neubauer.peter
Skype peter.neubauer
Phone +46 704 106975
L
After a second look it turns out that what you have reported is in fact not
a problem. It is handled properly, we print a warning to let the user know
that there we couldn't find the JMX connection URL to this JVM, but it's not
severe. I've lowered the log level from INFO to CONFIG in rev 8111. Neo
On Thu, Dec 23, 2010 at 12:34 PM, George Ciubotaru
wrote:
>
> Taking a second look over that locking mechanism, I've noticed that it uses
> read locks for a delete operation. Should there be write locks instead?
>
Yes, sorry about that it should be write locks. The read locks will
still allow fo
Hi Ron,
The 1.5 requirement is for Neo4j kernel, the core of embedded Neo4j. Neo4j
HA actually requires JDK 6, and has not been tested on other JDKs than
Sun/OpenJDK. The Exception you are reporting is in fact from the use of a
Sun specific class, it is going to be resolved when we get around to m
5 matches
Mail list logo
