blocks|key|977815|text|最好使用自己的唯一标识符，而不是节点id。因为您不能依赖ID.nodeid基本上是地址节点在文件中有节点记录。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|977816|您可以向csv文件中添加唯一的id并将其导入数据库。|977817|或者可以使用GraphAware+UUID模块动态创建UUID+-+https://github.com/graphaware/neo4j-uuid。|offset|length|977818|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/graphaware/neo4j-uuid^0|0|0|Y|14|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

It's better to use your own unique identifier instead of node id. Because you can't to rely on ID. Node id is basically address where node is in file with nodes records.

You can add unique id to your csv file and import it into database.

Or you can use GraphAware UUID module for creating UUID on the fly - <a href="https://github.com/graphaware/neo4j-uuid" rel="nofollow">https://github.com/graphaware/neo4j-uuid</a>

blocks|key|1583404|text|注意:如果Af关系没有任何属性，实际上可能不需要创建它，因为您可以轻松地将Ap关系从a遍历到n。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1583405|如果确实需要创建Af关系，则可以通过强制Cypher同时使用两种索引来提高性能。|1583406|在查询中使用配置文件+(与2个索引一起使用)，我看到Cypher计划器(我尝试了两种规划师类型)使用SchemaIndex操作符(它利用索引)，只使用索引中的one。为了强制Cypher同时使用和索引，您可以使用USING+INDEX子句，如下所示：|BOLD|1583407|LOAD+CSV+FROM+'file:///path/to/file'+AS+line
MATCH+(n:Organization+{+rc:'2051061'+})
USING+INDEX+n:Organization(rc)
MATCH+(n)-[:Ap]->(a:Person+{+numDc:+toint(line[1])})
USING+INDEX+a:Person(numDc)
CREATE+(a)-[:Af]->(n);|code-block|syntax|javascript|1583408|性能应该大大提高。|1583409|entityMap|0|LINK|mutability|MUTABLE|url|http://neo4j.com/docs/2.3.0/how-do-i-profile-a-query.html|1|http://neo4j.com/docs/stable/how-are-queries-executed.html^0|5|2|11|2|16|1|1A|1|0|8|2|0|1E|B|2Y|B|27|3|2P|1|6|4|0|14|7|1|0|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@$9|12|A|13|B|C]|$9|14|A|15|B|C]|$9|16|A|17|B|C]|$9|18|A|19|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1A|8|@$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|1D|8|@$9|1E|A|1F|B|C]|$9|1G|A|1H|B|C]|$9|1I|A|1J|B|J]|$9|1K|A|1L|B|J]]|D|@$9|1M|A|1N|1|1O]|$9|1P|A|1Q|1|1R]]|E|$]]|$1|K|3|L|5|M|7|1S|8|@]|D|@]|E|$N|O]]|$1|P|3|Q|5|6|7|1T|8|@]|D|@]|E|$]]|$1|R|3|-4|5|6|7|1U|8|@]|D|@]|E|$]]]|S|$T|$5|U|V|W|E|$X|Y]]|Z|$5|U|V|W|E|$X|10]]]]

Note: You may not actually need to create an <code>Af</code> relationship if it does not have any properties, since you can easily traverse an <code>Ap</code> relationship "backwards" from <code>a</code> to <code>n</code>.

If you really do need to create an <code>Af</code> relationship, you can improve your performance by forcing Cypher to use both of your indexes.

Using <a href="http://neo4j.com/docs/2.3.0/how-do-i-profile-a-query.html" rel="nofollow">PROFILE</a> on your query (with the 2 indexes), I see that the Cypher planner (I tried <a href="http://neo4j.com/docs/stable/how-are-queries-executed.html" rel="nofollow">both planner types</a>) uses the <code>SchemaIndex</code> operator (which takes advantage of an index) with only one of your indexes. In order to force Cypher to use both indexes, you can use the <code>USING INDEX</code> clause, like this:

<pre><code>LOAD CSV FROM 'file:///path/to/file' AS line
MATCH (n:Organization { rc:'2051061' })
USING INDEX n:Organization(rc)
MATCH (n)-[:Ap]-&gt;(a:Person { numDc: toint(line[1])})
USING INDEX a:Person(numDc)
CREATE (a)-[:Af]-&gt;(n);
</code></pre>

The performance should be much improved.

I'm trying to speed up this query:

<pre><code>LOAD CSV FROM 'file:///path/to/file' AS line
MATCH (n:Organization{rc:'2051061'})-[:Ap]-&gt;(a:Person{numDc: toint(line[1])})
CREATE (a)-[:Af]-&gt;(n)
</code></pre>

The CSV has about 100k rows, the relationship <code>(n:Organization)-[:Ap]-&gt;(a:Person)</code> is unique between different a/b pairs. The number of nodes with label <code>:Organization</code> is 50, and those with <code>:Person</code> is 200k.

So basically I take a value in the csv and check if a :Person who has a relation <code>:Ap</code> with the :Organization with the given rc (2051061) has that value as <code>numDc</code> and then I add another relation between the Person and the organization.

My query runs too slow, I even added indexes to <code>:Person(numDc)</code> and <code>Organization(rc)</code>.

So I think since I'm matching the organization for every row It may be the problem.

How can I get instant match to that node if I do know it's &lt; id >.

Thanks in advance.

How to get instant match to a node, If i know it's < id >

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我试图加速这个查询：LOAD CSV FROM 'file:///path/to/file' AS lineMATCH (n:Organization{rc:'2051061'})-[:Ap]->(a:Person{numDc: toint(line[1])})CREATE (a)-[:Af]->(n)CSV有大约10...

问如果我知道节点是< id >，那么如何立即匹配它
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如果我知道节点是< id >，那么如何立即匹配它EN