Mixing
Neo4j How to call different properties for the same relationship
I'm using the new algo to calculate similarities, algo.similarity.jaccard and algo.similarity.overlap with the option WRITE, it means, in the relationship SIMILARITY I create properties sim_jaccard and sim_overlap.
The problem comes when I call these two properties, for example :
MATCH (u1:User)-[s:SIMILARITY]-> (u2:User)
WITH coalesce(s.sim_jaccard,0) AS sim_jaccard, coalesce(s.sim_overlap,0) AS sim_overlap
RETURN sim_jaccard, sim_overlap
LIMIT 25
I get:
sim_jaccard sim_overlap
0 0.8507462686567164
0 0.9253731343283582
0 0.8208955223880597
0 0.8955223880597015
I think that happens because properties id are different in the relationship:
SIMILARITY <id>: 3300778 sim_overlap: 1.0
SIMILARITY <id>: 2453827 sim_jaccard: 0.6268656716417911
I would like to have:
SIMILARITY <id>: 3300778 sim_overlap: 1.0, sim_jaccard: 0.6268656716417911
Any idea to solve that?
Thanks in advance.
neo4j properties relationship similarity
asked Nov 21 '18 at 13:10
mnfmnf
61
add a comment |
I'm using the new algo to calculate similarities, algo.similarity.jaccard and algo.similarity.overlap with the option WRITE, it means, in the relationship SIMILARITY I create properties sim_jaccard and sim_overlap.
The problem comes when I call these two properties, for example :
MATCH (u1:User)-[s:SIMILARITY]-> (u2:User)
WITH coalesce(s.sim_jaccard,0) AS sim_jaccard, coalesce(s.sim_overlap,0) AS sim_overlap
RETURN sim_jaccard, sim_overlap
LIMIT 25
I get:
sim_jaccard sim_overlap
0 0.8507462686567164
0 0.9253731343283582
0 0.8208955223880597
0 0.8955223880597015
I think that happens because properties id are different in the relationship:
SIMILARITY <id>: 3300778 sim_overlap: 1.0
SIMILARITY <id>: 2453827 sim_jaccard: 0.6268656716417911
I would like to have:
SIMILARITY <id>: 3300778 sim_overlap: 1.0, sim_jaccard: 0.6268656716417911
Any idea to solve that?
Thanks in advance.
neo4j properties relationship similarity
asked Nov 21 '18 at 13:10
mnfmnf
61
add a comment |
I'm using the new algo to calculate similarities, algo.similarity.jaccard and algo.similarity.overlap with the option WRITE, it means, in the relationship SIMILARITY I create properties sim_jaccard and sim_overlap.
The problem comes when I call these two properties, for example :
MATCH (u1:User)-[s:SIMILARITY]-> (u2:User)
WITH coalesce(s.sim_jaccard,0) AS sim_jaccard, coalesce(s.sim_overlap,0) AS sim_overlap
RETURN sim_jaccard, sim_overlap
LIMIT 25
I get:
sim_jaccard sim_overlap
0 0.8507462686567164
0 0.9253731343283582
0 0.8208955223880597
0 0.8955223880597015
I think that happens because properties id are different in the relationship:
SIMILARITY <id>: 3300778 sim_overlap: 1.0
SIMILARITY <id>: 2453827 sim_jaccard: 0.6268656716417911
I would like to have:
SIMILARITY <id>: 3300778 sim_overlap: 1.0, sim_jaccard: 0.6268656716417911
Any idea to solve that?
Thanks in advance.
neo4j properties relationship similarity
asked Nov 21 '18 at 13:10
mnfmnf
61
I'm using the new algo to calculate similarities, algo.similarity.jaccard and algo.similarity.overlap with the option WRITE, it means, in the relationship SIMILARITY I create properties sim_jaccard and sim_overlap.
The problem comes when I call these two properties, for example :
MATCH (u1:User)-[s:SIMILARITY]-> (u2:User)
WITH coalesce(s.sim_jaccard,0) AS sim_jaccard, coalesce(s.sim_overlap,0) AS sim_overlap
RETURN sim_jaccard, sim_overlap
LIMIT 25
I get:
sim_jaccard sim_overlap
0 0.8507462686567164
0 0.9253731343283582
0 0.8208955223880597
0 0.8955223880597015
I think that happens because properties id are different in the relationship:
SIMILARITY <id>: 3300778 sim_overlap: 1.0
SIMILARITY <id>: 2453827 sim_jaccard: 0.6268656716417911
I would like to have:
SIMILARITY <id>: 3300778 sim_overlap: 1.0, sim_jaccard: 0.6268656716417911
Any idea to solve that?
Thanks in advance.
neo4j properties relationship similarity
neo4j properties relationship similarity
asked Nov 21 '18 at 13:10
mnfmnf
61
asked Nov 21 '18 at 13:10
mnfmnf
61
edited Nov 26 '18 at 10:58
mnf
asked Nov 21 '18 at 13:10
mnfmnf
61
asked Nov 21 '18 at 13:10
mnfmnf
61
asked Nov 21 '18 at 13:10
mnfmnf
61
61
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
If you want to modify your graph so the relationships are combined into 1, then APOC Procedures has some refactor procs to merge relationships together (just use the combine value for the given properties).
If you just want your return to combine the values into a single line, then you can modify your query to sum the values for all rels between the two nodes:
MATCH (u1:User)-[s:SIMILARITY]-(u2:User)
WHERE id(u1) < id(u2)
WITH u1, u2, sum(coalesce(s.sim_jaccard,0)) AS sim_jaccard, sum(coalesce(s.sim_overlap,0)) AS sim_overlap
RETURN sim_jaccard, sim_overlap
LIMIT 25
For the approach where you need to MERGE nodes, you'll want to collect the relationships with respect to the end nodes before calling the procedure:
MATCH (u1:User)-[s:SIMILARITY]-(u2:User)
WHERE id(u1) < id(u2)
WITH u1, u2, collect(s) as rels
CALL apoc.refactor.mergeRelationships(rels, {properties:'combine'}) YIELD rel
RETURN count(rel)
sum(coalesce(s.sim_jaccard,0)) AS sim_jaccard, sum(coalesce(s.sim_overlap,0)) AS sim_overlap
RETURN sim_jaccard, sim_overlap
LIMIT 25
answered Nov 26 '18 at 12:40
InverseFalconInverseFalcon
19.2k31830
Yes, I need to merge relationships together, so apoc.refactor.mergeRelationships([rels],{config}) should solve my problem. Please, could you tell me what I'm doing wrong? : call apoc.refactor.mergeRelationships([MATCH (u1:User)-[s:SIMILARITY]->(u2:User)],{properties:'combine'}), because it doesn't work. Thanks!
– mnf
Nov 27 '18 at 14:58
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53412803%2fneo4j-how-to-call-different-properties-for-the-same-relationship%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you want to modify your graph so the relationships are combined into 1, then APOC Procedures has some refactor procs to merge relationships together (just use the combine value for the given properties).
If you just want your return to combine the values into a single line, then you can modify your query to sum the values for all rels between the two nodes:
MATCH (u1:User)-[s:SIMILARITY]-(u2:User)
WHERE id(u1) < id(u2)
WITH u1, u2, sum(coalesce(s.sim_jaccard,0)) AS sim_jaccard, sum(coalesce(s.sim_overlap,0)) AS sim_overlap
RETURN sim_jaccard, sim_overlap
LIMIT 25
For the approach where you need to MERGE nodes, you'll want to collect the relationships with respect to the end nodes before calling the procedure:
MATCH (u1:User)-[s:SIMILARITY]-(u2:User)
WHERE id(u1) < id(u2)
WITH u1, u2, collect(s) as rels
CALL apoc.refactor.mergeRelationships(rels, {properties:'combine'}) YIELD rel
RETURN count(rel)
sum(coalesce(s.sim_jaccard,0)) AS sim_jaccard, sum(coalesce(s.sim_overlap,0)) AS sim_overlap
RETURN sim_jaccard, sim_overlap
LIMIT 25
answered Nov 26 '18 at 12:40
InverseFalconInverseFalcon
19.2k31830
Yes, I need to merge relationships together, so apoc.refactor.mergeRelationships([rels],{config}) should solve my problem. Please, could you tell me what I'm doing wrong? : call apoc.refactor.mergeRelationships([MATCH (u1:User)-[s:SIMILARITY]->(u2:User)],{properties:'combine'}), because it doesn't work. Thanks!
– mnf
Nov 27 '18 at 14:58
add a comment |
If you want to modify your graph so the relationships are combined into 1, then APOC Procedures has some refactor procs to merge relationships together (just use the combine value for the given properties).
If you just want your return to combine the values into a single line, then you can modify your query to sum the values for all rels between the two nodes:
MATCH (u1:User)-[s:SIMILARITY]-(u2:User)
WHERE id(u1) < id(u2)
WITH u1, u2, sum(coalesce(s.sim_jaccard,0)) AS sim_jaccard, sum(coalesce(s.sim_overlap,0)) AS sim_overlap
RETURN sim_jaccard, sim_overlap
LIMIT 25
For the approach where you need to MERGE nodes, you'll want to collect the relationships with respect to the end nodes before calling the procedure:
MATCH (u1:User)-[s:SIMILARITY]-(u2:User)
WHERE id(u1) < id(u2)
WITH u1, u2, collect(s) as rels
CALL apoc.refactor.mergeRelationships(rels, {properties:'combine'}) YIELD rel
RETURN count(rel)
sum(coalesce(s.sim_jaccard,0)) AS sim_jaccard, sum(coalesce(s.sim_overlap,0)) AS sim_overlap
RETURN sim_jaccard, sim_overlap
LIMIT 25
answered Nov 26 '18 at 12:40
InverseFalconInverseFalcon
19.2k31830
Yes, I need to merge relationships together, so apoc.refactor.mergeRelationships([rels],{config}) should solve my problem. Please, could you tell me what I'm doing wrong? : call apoc.refactor.mergeRelationships([MATCH (u1:User)-[s:SIMILARITY]->(u2:User)],{properties:'combine'}), because it doesn't work. Thanks!
– mnf
Nov 27 '18 at 14:58
add a comment |
If you want to modify your graph so the relationships are combined into 1, then APOC Procedures has some refactor procs to merge relationships together (just use the combine value for the given properties).
If you just want your return to combine the values into a single line, then you can modify your query to sum the values for all rels between the two nodes:
MATCH (u1:User)-[s:SIMILARITY]-(u2:User)
WHERE id(u1) < id(u2)
WITH u1, u2, sum(coalesce(s.sim_jaccard,0)) AS sim_jaccard, sum(coalesce(s.sim_overlap,0)) AS sim_overlap
RETURN sim_jaccard, sim_overlap
LIMIT 25
For the approach where you need to MERGE nodes, you'll want to collect the relationships with respect to the end nodes before calling the procedure:
MATCH (u1:User)-[s:SIMILARITY]-(u2:User)
WHERE id(u1) < id(u2)
WITH u1, u2, collect(s) as rels
CALL apoc.refactor.mergeRelationships(rels, {properties:'combine'}) YIELD rel
RETURN count(rel)
sum(coalesce(s.sim_jaccard,0)) AS sim_jaccard, sum(coalesce(s.sim_overlap,0)) AS sim_overlap
RETURN sim_jaccard, sim_overlap
LIMIT 25
answered Nov 26 '18 at 12:40
InverseFalconInverseFalcon
19.2k31830
If you want to modify your graph so the relationships are combined into 1, then APOC Procedures has some refactor procs to merge relationships together (just use the combine value for the given properties).
If you just want your return to combine the values into a single line, then you can modify your query to sum the values for all rels between the two nodes:
MATCH (u1:User)-[s:SIMILARITY]-(u2:User)
WHERE id(u1) < id(u2)
WITH u1, u2, sum(coalesce(s.sim_jaccard,0)) AS sim_jaccard, sum(coalesce(s.sim_overlap,0)) AS sim_overlap
RETURN sim_jaccard, sim_overlap
LIMIT 25
For the approach where you need to MERGE nodes, you'll want to collect the relationships with respect to the end nodes before calling the procedure:
MATCH (u1:User)-[s:SIMILARITY]-(u2:User)
WHERE id(u1) < id(u2)
WITH u1, u2, collect(s) as rels
CALL apoc.refactor.mergeRelationships(rels, {properties:'combine'}) YIELD rel
RETURN count(rel)
sum(coalesce(s.sim_jaccard,0)) AS sim_jaccard, sum(coalesce(s.sim_overlap,0)) AS sim_overlap
RETURN sim_jaccard, sim_overlap
LIMIT 25
answered Nov 26 '18 at 12:40
InverseFalconInverseFalcon
19.2k31830
edited Nov 27 '18 at 20:30
answered Nov 26 '18 at 12:40
InverseFalconInverseFalcon
19.2k31830
answered Nov 26 '18 at 12:40
InverseFalconInverseFalcon
19.2k31830
answered Nov 26 '18 at 12:40
InverseFalconInverseFalcon
19.2k31830
19.2k31830
Yes, I need to merge relationships together, so apoc.refactor.mergeRelationships([rels],{config}) should solve my problem. Please, could you tell me what I'm doing wrong? : call apoc.refactor.mergeRelationships([MATCH (u1:User)-[s:SIMILARITY]->(u2:User)],{properties:'combine'}), because it doesn't work. Thanks!
– mnf
Nov 27 '18 at 14:58
add a comment |
Yes, I need to merge relationships together, so apoc.refactor.mergeRelationships([rels],{config}) should solve my problem. Please, could you tell me what I'm doing wrong? : call apoc.refactor.mergeRelationships([MATCH (u1:User)-[s:SIMILARITY]->(u2:User)],{properties:'combine'}), because it doesn't work. Thanks!
– mnf
Nov 27 '18 at 14:58
Yes, I need to merge relationships together, so apoc.refactor.mergeRelationships([rels],{config}) should solve my problem. Please, could you tell me what I'm doing wrong? : call apoc.refactor.mergeRelationships([MATCH (u1:User)-[s:SIMILARITY]->(u2:User)],{properties:'combine'}), because it doesn't work. Thanks!
– mnf
Nov 27 '18 at 14:58
Yes, I need to merge relationships together, so apoc.refactor.mergeRelationships([rels],{config}) should solve my problem. Please, could you tell me what I'm doing wrong? : call apoc.refactor.mergeRelationships([MATCH (u1:User)-[s:SIMILARITY]->(u2:User)],{properties:'combine'}), because it doesn't work. Thanks!
– mnf
Nov 27 '18 at 14:58
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53412803%2fneo4j-how-to-call-different-properties-for-the-same-relationship%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
