I tried it both on the browser AND from neo4j nodejs client. When it
doesn't work, it doesn't work on both of them.
My os is ubuntu 12.04.
Like I said, sometimes it doesn't work, so i do 'neo4j restart' and then it
works...
On Mon, Jun 30, 2014 at 9:42 PM, Mattias Persson
wrote:
> This could
This could be a browser issue actually. I tried running your query directly
via a Cypher ExecutionEngine, and no matter how many times I tried, it
always gave me the 860 results back.
On Tue, Jun 24, 2014 at 10:20 AM, shai katzir wrote:
> It's getting a little weird.
> I run the next query :
>
It's getting a little weird.
I run the next query :
*match (pr:Property {name: "BLACK"})*
*match (pr)--(it)*
*return pr,it*
where "pr:Property {name: "BLACK"} " is a "densed node".
Some times I get 0 results for this query in the browser, and then I
restart the graph server and I get ~900 result
Hi Shai,
I got access to your store and using the backed up nodestore and
relationshipstore in upgrade_backup, I compared contents of the upgraded
(2.1.2) store to that of the 2.0.3 store.
What I found found was that all nodes, properties and relationships are
exactly the same. I dumped nodes,
Of course I have backup, and it was only a test, but not a successful one.
It's hard to say what data is lost.
I think that the dense nodes (the ones that I know have a lot of incoming
relationships) lost all their relationships. That is also correspond to the
nature of the version update.
בתא
