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", Mes
match (c: Client)-[WORKS_FOR]->(co: Company) return c, co limit 10
This query is doing a full graph lookup and capturing 100's of millions of
results and then only returning 10 of them. This will never return with
Neo4j. You need to pick a starting point in your graph and start executing
quer
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
> neo4
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 rel
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'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)));
+---
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
wrote:
> Bottom line up front: it looks like if you try to atta
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.
Example
Awesome, thanks a lot.
Would you mind writing a quick blog post about it?
Cheers Michael
Sent from mobile device
Am 26.06.2014 um 17:39 schrieb Eric Olson :
> Sorry I never got back to you on this Michael! Adding the USING INDEX did the
> trick. I thought creating indexes was enough and that
On Thursday, June 26, 2014 8:40:31 AM UTC-7, C. Thomas Stover wrote:
>
> Although in the case you describe the problem is going to be the memory
> required for the data will be many more times greater than the code.
>
Thanks for the detailed response. FWIW, in a class or demo situation, the
data
On Thu, 26 Jun 2014 07:07:04 -0700, Rich Morin wrote:
> However, dozens of Neo4j (and JVM?) instances could use up a lot of
> memory, even if the data sets are small. So, assuming that the instances
> are running directly under the (Linux or Mac OS X) operating system),
> could they share unmodifi
Sorry I never got back to you on this Michael! Adding the USING INDEX did
the trick. I thought creating indexes was enough and that I would never
have to reference them in my queries, but oh well. This is cool :) I have
used this to speed up a lot of my complex queries. I am getting 10x faster
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
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} }),
(vers
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 wo
As you updated your graph it still runs with the indexing type strategy
So either stick with the deprecated method
or
Switch the strategy to label based in your spring config
Make a backup first if you go with option 2
Sent from mobile device
Am 26.06.2014 um 15:37 schrieb Mamta Thakur :
>
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 up
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
E-mail
@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 = Direction.BOT
What does your entity look like?
Sent from mobile device
Am 26.06.2014 um 14:52 schrieb Mamta Thakur :
> 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 is
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 :
> My JVM properties include
>
> # Enter on
parameters
Not
params
Sent from mobile device
Am 26.06.2014 um 10:46 schrieb Tom Zeppenfeldt :
> POSTing this :
>
> {
> "statements" : [ {
> "statement" : "match(uc:usercase {name:{name}}) return uc",
> "params": {
> "name" : "myname"
> },
> "resultDataContents" : [ "gra
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.
org.springframework.data
spring-data-neo4j
3.1.0.RELEASE
Code:
Iterator repoItr =
memberRepos
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 th
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 tr
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/transactio
26 matches
Mail list logo