So it's actually a bug that it doesn't fail correctly. Please report
it as GH issue.
On Sun, Feb 2, 2014 at 7:22 AM, Michael Hunger
wrote:
> You cannot return the scalar values and the aggregate of the same
> values at the same time.
> You have to match again.
>
> But it shouldn't eat your CPU bu
You cannot return the scalar values and the aggregate of the same
values at the same time.
You have to match again.
But it shouldn't eat your CPU but just fail correctly with an error.
How many nodes do you have in your db?
MATCH (A)
WITH head(collect(A)) as B
MATCH (A)
RETURN A, B
On Sun, Feb
Sorry, can you give an example. I don't understand.
template.fetch(entity.collection) should fetch the whole collections content.
On Sun, Feb 2, 2014 at 3:53 AM, Michael Azerhad
wrote:
> Hello,
>
> My question is pretty simple:
> May it be a normal scenario when neo4jTemplate.fetch returns ALWAY
Constraint indexes are created differently than non-constraint schema indexes.
Yet only one index can exist for a particular label/property key combination at
a time. Therefor you have to drop the ordinary index before you can create a
constraint on the same label/property key. A constraint othe
Windows 7 x64 accessing Neo4j via Chrome using localhost:7474/browser .
Neo4j version 2.0, have replicated issue with GrapheneDB Neo4j 2.0 via
Neo4j Browser. Doubt it has anything to do with my hardware.
--
You received this message because you are subscribed to the Google Groups
"Neo4j" group
I've done a similar query below though the MATCH has a more specific
pattern rather than querying all nodes. If I only return A or B the query
works fine, but with A and B the database will lock on "Executing query.."
then return "Unknown error". If the query is a bug let me know and I'll
post
Hello,
My question is pretty simple:
May it be a normal scenario when neo4jTemplate.fetch returns ALWAYS the
first collection's element? (concerning a @RelatedTo collection's field
without any @Fetch annotation)
On the contrary, when @Fetch is placed, the whole collection is well
retrieved.
if it already exists it is not created again
and yes for unique constraints we create a companion index
On Sun, Feb 2, 2014 at 12:28 AM, Aran Mulholland
wrote:
> If I use the following command:
>
> CREATE INDEX ON :Player(name)
>
> or
>
> CREATE CONSTRAINT ON pl:Player
> ASSERT pl.name IS UNIQUE
If I use the following command:
CREATE INDEX ON :Player(name)
or
CREATE CONSTRAINT ON pl:Player
ASSERT pl.name IS UNIQUE
and the index or constraint already exists, does it hurt to issue the
command twice?
Also, does creating a constraint implicitly create an index?
Copied from the excellent
Thanks for finding it and the heads up, we'll fix it.
Cheers
On Sat, Feb 1, 2014 at 11:02 PM, wrote:
> Hi,
> When I run the CalculateShortestPath example in,
> https://github.com/neo4j/neo4j/tree/master/community/embedded-examples
>
>
> I get the following exception :
> Exception in t
Hi,
When I run the CalculateShortestPath example in,
https://github.com/neo4j/neo4j/tree/master/community/embedded-examples
I get the following exception :
Exception in thread "main" org.neo4j.graphdb.NotInTransactionException
at
org.neo4j.kernel.impl.transaction.AbstractTransactio
I have tried your suggestion and it works !
Thanks!
Shing
On Saturday, February 1, 2014 9:04:14 PM UTC, Michael Hunger wrote:
>
> you have to run this fist:
>
> cd neo4j/community/licensecheck-config
> $ mvn install
>
> Am 01.02.2014 um 19:35 schrieb shingh...@gmail.com :
>
> > Hi,
> >
The error I get with your SO query is related to merge within foreach.
Michael
Am 01.02.2014 um 22:17 schrieb Brennan Kinney :
> Is that the cause? As the query does seem to work once or at least with a
> single year. I don't know why it was breaking with future queries.
>
> On Saturday, 1 Feb
Is that the cause? As the query does seem to work once or at least with a
single year. I don't know why it was breaking with future queries.
On Saturday, 1 February 2014 23:48:53 UTC+13, Brennan Kinney wrote:
>
> I've spent some time building a query with the intention of saving time,
> can't fi
I think the exception for nested foreachs is fixed for 2.0.1 which is due soon.
Michael
Am 01.02.2014 um 12:40 schrieb Brennan Kinney :
> It was more of a exercise about learning what I can do and how with Cypher.
> If you try the query with multiple years you could try 1999, 2000, 2004, they
What is your actual write load?
How big was your batch size? Currently for 2.1 1000 elements is sensible. It
will change back to 30-50k for Neo4j 2.1
#0 use parameters
> MERGE (user:User { name:{user_name} })', 'MERGE (tweet:Tweet {
> tweet_id:{tweet_id} })
#1 can you share your server config
you have to run this fist:
cd neo4j/community/licensecheck-config
$ mvn install
Am 01.02.2014 um 19:35 schrieb shinghing...@gmail.com:
> Hi,
>
> I have checkouted the embedded-example maven project from
>
> https://github.com/neo4j/neo4j/tree/master/community/embedded-examples
>
Yep, that's what it does in the non-streaming case.
afaik case 3 and 4 return a http 500
in streaming you don't know b/c you send the headers before each of the queries
is actually processed and their results come in even later than that, so no way
of updating http headers. that's why the strea
Hi,
I have checkouted the embedded-example maven project from
https://github.com/neo4j/neo4j/tree/master/community/embedded-examples
When I try to to compile it using "mvn compile" I got the following error.
INFO] --- licensing-maven-plugin:1.7.5:check (enforce-licensing-oss) @
*Question background*
We are building a graph (database) for twitter users and tweets (batched
updates for new data).
We store as graph nodes: each-user, each-tweet
We store as graph edges: tweet-tweet relationships, and user-user
relationships (derived, based on users who retweet or reply t
I guess that was 4 cases ;-)
On Saturday, February 1, 2014 10:23:49 AM UTC-5, brian wrote:
>
> Hi Michael,
>
> I can't give you the code, but I can probably work up a test case.
> Although it's actually pretty simple. Just create two nodes with a
> relationship between them. Then issue a Cyph
Hi Michael,
I can't give you the code, but I can probably work up a test case.
Although it's actually pretty simple. Just create two nodes with a
relationship between them. Then issue a Cypher query that would find one
of the nodes (it could just be a simple query on some property of one of
It was more of a exercise about learning what I can do and how with Cypher.
If you try the query with multiple years you could try 1999, 2000, 2004,
they should all trigger a different CASE.
The full query is on StackOverflow via the link, this is the query with
corrections:
//Date ranges in a
And I think optimizing for many years at once might be overkill
Sent from mobile device
Am 01.02.2014 um 11:48 schrieb Brennan Kinney :
> I've spent some time building a query with the intention of saving time,
> can't figure out what I've done that messed it up. The query is to build
> years/
Can you share your full query?
Thx
Sent from mobile device
Am 01.02.2014 um 11:48 schrieb Brennan Kinney :
> I've spent some time building a query with the intention of saving time,
> can't figure out what I've done that messed it up. The query is to build
> years/months/days nodes/relationsh
I've spent some time building a query with the intention of saving time,
can't figure out what I've done that messed it up. The query is to build
years/months/days nodes/relationships and uses MERGE/CREATE UNIQUE to avoid
duplicates. Seems to work fine if I only use a single year, when I tried 6
Thank you so much Michael! It works!
On Saturday, February 1, 2014 1:43:34 PM UTC+7, Michael Hunger wrote:
>
> SKIP offset LIMIT count
>
> Am 01.02.2014 um 07:12 schrieb Rio Eduardo
> >:
>
> According to http://docs.neo4j.org/chunked/milestone/query-limit.html,
> Limit just have 1 parameter
>
>
27 matches
Mail list logo
