cybersam
2020-12-09 06:32:03
A MERGE clause will create its entire pattern if any part of it does not already exist. So, for a MERGE clause to work reasonably, the pattern used with it must only specify the minimum data necessary to uniquely identify a node (or a relationship).
For instance, assuming ARTICLE nodes are supposed to have unique id properties, then you should replace your CREATE clause:
CREATE (a:ARTICLE {id:$id, title:$title, img_url:$img_url, link:$link, sentence:$sentence, published:$published})
with something like this:
MERGE (a:ARTICLE {id:$id})
SET a += {title:$title, img_url:$img_url, link:$link, sentence:$sentence, published:$published}
In the above example, the SET clause will always overwrite the non-id properties. If you want to set those properties only when the node is created, you can use ON CREATE before the SET clause.
热门帖子
9
Thank you, I saw that I have NaN values in some columns of the article dataframe. I replaced them by 'no content' and MERGE seems to work now. I think it was it but I don't understand why it is a problem?
I also do NER on articles and when I do NER on new scraping same NER nodes are created. I don't understand why
You have not shown enough information or code (e.g., how are you generating the parameters to pass to the Cypher code, and what your actual CYpher code now looks like, etc.). Also, what does "NER" mean? And what are the actual error messages you are getting? Etc.