I'm setting up a new server for an application (node.js with Neo4j 1.8.3)
that hasn't been used for a while.
I installed Neo4J 1.8.3 on Thursday, on Ubuntu 14.04 running on Linode.
Today I reviewed
the log file (neo4j.0.0.log) and saw the following error:
Oct 02, 2014 5:02:48 PM java.util.pref
can you try to run: bin/neo4j console
to see where the issue is?
Thanks Michael
On Sun, Oct 5, 2014 at 11:37 PM, Jared Windover
wrote:
> Hi guys,
>
> I've installed neo4j with pacman and am able to run the web console,
> however when I try to just start the server (either with neo4j start or
>
Hi guys,
I've installed neo4j with pacman and am able to run the web console,
however when I try to just start the server (either with neo4j start or
systemctl start neo4j.service) it says it failed to start within the
timeout period, but it doesn't wait for the full timeout period. Looking at
Right
then you have to lable your nodes
like
match (n) where n.crime_type SET n:Crime;
and then create the index:
create index on :Crime(crime_type);
On Sun, Oct 5, 2014 at 8:53 PM, Mohana Krishna, IIT Bombay, India <
mohana...@gmail.com> wrote:
> Michael,
>
> Can you please give me the fu
Michael,
Can you please give me the full syntax of creating index from attribute? I
couldn't find exact syntax. The syntax for already labelled nodes is
available. Nodes in my db are unlabelled as of now and I am trying to
create index from a common attribute to all nodes. My attribute name is
Yes you must call both
The idea is that you have to explicitely confirm that the tx is successful
before closing it
Not confirmed tx will be rolled back on close()
Von meinem iPhone gesendet
> Am 05.10.2014 um 14:02 schrieb Frandro :
>
> The following code newly begins transaction each 1000 b
tx.close() will either commit your transaction if you called tx.success(), or
roll it back if you either did not call tx.success() or called tx.failure().
When you start a new transaction without closing the one you already have, the
new transaction will become a sub-transaction of the outer one
The following code newly begins transaction each 1000 batch job.
Is the following code correct?
Do I have to invoke the tx.close() method each 1000 batch job in the middle?
It seems there's no problem without calling the method.
What are success() and close() for? It's confusing.
Transaction t
Hi Jerry,
Very cool to hear that you're finding the LDBC work useful.
Please see the email I sent to your private email a little while ago.
Best,
Alex
On Sun, Oct 5, 2014 at 4:08 AM, jer wrote:
> I did a little more testing, it seems that at least there is some problem
> in importing the graph.d
