POSTing this :
{
statements : [ {
statement : match(uc:usercase {name:{name}}) return uc,
params: {
name : myname
},
resultDataContents : [ graph ]
} ]
}
to the transactional endpoint returns:
{
commit: http://mydomain.com:7474/db/data/transaction/106/commit;,
My JVM properties include
# Enter one VM parameter per line, note that some parameters can only be
set once.
# For example, to adjust the maximum memory usage to 512 MB, uncomment the
following line
-Xmx6144m
Xmx4G -Xms4G -Xmn1G
but still i am getting GC overhead limit exceeded error. (I have
SOLVED
thank you! error was due to a ghost previous installation (probably done
with brew), which mapped the command neo4j to the previous folder
installation so it was loading the kernel of version 1.8
Il giorno domenica 22 giugno 2014 17:09:12 UTC+2, Michael Hunger ha scritto:
In the
Hi All,
We recently upgraded the Neo4j version to 2.0.3 and SDN to 3.1.0. Data
upgrade happened successfully.
We were able to run some of the APIs successfully where as some gave issues.
dependency
groupIdorg.springframework.data/groupId
artifactIdspring-data-neo4j/artifactId
parameters
Not
params
Sent from mobile device
Am 26.06.2014 um 10:46 schrieb Tom Zeppenfeldt tomzeppenfe...@gmail.com:
POSTing this :
{
statements : [ {
statement : match(uc:usercase {name:{name}}) return uc,
params: {
name : myname
},
resultDataContents : [
Your constraints are wrong you mixed up labels and identifiers
Please also check the index properties
And I had better success doing a multi-pass for each set of elements to connect
Sent from mobile device
Am 26.06.2014 um 11:58 schrieb Pavan Kumar kumar.pavan...@gmail.com:
My JVM properties
What does your entity look like?
Sent from mobile device
Am 26.06.2014 um 14:52 schrieb Mamta Thakur ghazal.ma...@gmail.com:
Hi All,
We recently upgraded the Neo4j version to 2.0.3 and SDN to 3.1.0. Data
upgrade happened successfully.
We were able to run some of the APIs successfully
@NodeEntity
public class Member {
@GraphId
Long nodeId;
@Indexed(unique = true, numeric = false)
private String id;
private Long facebookUserId;
@RelatedTo(type = MY_FB, direction = Direction.BOTH)
FacebookUser facebookUser;
@RelatedToVia(type = KNOWS, direction =
Ok. Thanks ! I assumed naming was similar to cypher endpoint. And as
always, assuming is not a good thing to do ;)
Met vriendelijke groet / With kind regards
Ir. T. Zeppenfeldt
van der Waalsstraat 30
6706 JR Wageningen
The Netherlands
Mobile: +31 6 23 28 78 06
Phone: +31 3 17 84 22 17
We had the deprecated method in the code and that ran into that error as I
mentioned earlier. The deprecated method is actually not working for me.
Thats why I am looking for an alternate solution.
Regards,
Mamta
On Thursday, June 26, 2014 7:13:37 PM UTC+5:30, Michael Hunger wrote:
As you
I'm interested in the idea of providing dozens of independent Cypher
sessions (eg, for a class or demo). One way to do this would be to run multiple
instances of Neo4j on a single server machine, giving each session its own
console, files, HTTP port, etc. Assuming that the details could be
I have run into a unique situation (bug?). Here is my query that does what
it is supposed to:
MATCH
(:Author {name: {author} })-[:WROTE_BOOK]-(b:Book {name_min: {book}
})-[:HAS_CHAPTER]-(c:Chapter {chapter: {chapter} })-[:HAS_TEXT]-(t:Text),
(lang:Language {language: {lang} }),
FYI - This is using Neo4j 2.1.2 personal enterprise
On Thursday, June 26, 2014 9:32:10 AM UTC-6, Eric Olson wrote:
I have run into a unique situation (bug?). Here is my query that does what
it is supposed to:
MATCH
(:Author {name: {author} })-[:WROTE_BOOK]-(b:Book {name_min: {book}
Bottom line up front: it looks like if you try to attach a new label to a
node, where the label name matches the name of an existing *property* on
the node, then cypher and the shell permits this, and returns valid results
as if it had made the change, but then doesn't make the change.
Can you update to 2.1.2 ?
Can you also return the labels here?
match (d:dept)
where d.org_type='center'
SET d:center
RETURN d.org_type, count(d), collect(distinct labels(d));
On Thu, Jun 26, 2014 at 10:02 PM, M. David Allen allen.m.da...@gmail.com
wrote:
Bottom line up front: it looks
I'll upgrade to 2.1.2 later tonight or tomorrow. But for now, yeah, what
comes back from collect(distinct(labels(d))) says the label was applied:
neo4j-sh (?)$ match (d:dept)
where d.org_type='center'
SET d:center
RETURN d.org_type, count(d), collect(distinct(labels(d)));
Update: upgrading to 2.1.2 was fast enough; unzip, drop in a directory,
update $PATH.
I re-ran the snippet you see below, same output under 2.1.2.
David
On Thursday, June 26, 2014 4:38:00 PM UTC-4, M. David Allen wrote:
I'll upgrade to 2.1.2 later tonight or tomorrow. But for now, yeah,
I recently upgraded from Neo4j 2.0.1 and immediately hit this new error:
{Code:Neo.ClientError.Statement.InvalidSyntax, Message:Cannot match on a
pattern containing only already bound identifiers (line 26, column 3)\n\
MATCH (m)\\n ^},
I didn't see this new incompatibility in the release
I ran into this same problem trying to upgrade from 2.0.1 to 2.1.2.
On Tuesday, June 24, 2014 1:52:46 AM UTC-7, Denys Hryvastov wrote:
Ok,
After having an email thread with neo4j support team (thanks them for
quick and full responses for all my questions) I have decided to use
Looks like you just need to remove the MATCH statement now. WHERE can
immediately follow WITH.
On Thursday, June 26, 2014 5:11:43 PM UTC-7, Bill Scheidel wrote:
I recently upgraded from Neo4j 2.0.1 and immediately hit this new error:
{Code:Neo.ClientError.Statement.InvalidSyntax,
20 matches
Mail list logo
