无法在APOC NLP中调用程序
我试图运行此代码＆amp;每次我遇到相同的错误。我尝试了Google API和Azure，但都返回类似的错误。
匹配（A：文章） 致电apoc.nlp.gcp.entities.graph（a，{ 钥匙：$ apikey， Nodeproperty：“身体”， writerelationshiptype：“实体” }）） 屈服图作为g 返回g;
错误消息： 未能调用过程apoc.nlp.gcp.entities.graph：引起：java.lang.nosuchmethoderror：
另外，我手动将apoc nlp jar包装添加到我的apoc插件文件夹中。任何解决方案都将不胜感激！
Im trying to run this code & every time I get the same error. I tried both google API and Azure but both return similar error.
MATCH (a:Article)
CALL apoc.nlp.gcp.entities.graph(a, {
key: $apiKey,
nodeProperty: "body",
writeRelationshipType: "ENTITY"
})
YIELD graph AS g
RETURN g;
Error msg:
Failed to invoke procedure apoc.nlp.gcp.entities.graph: Caused by: java.lang.NoSuchMethodError:
Plus, I manually added the APOC nlp jar package to my APOC plugin folder. Any solution would be appreciated!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
假设您已经在数据库的
插件目录中粘贴了JAR文件，请确保在数据库的conf目录中存在的配置文件中，以下设置在场：dbms.security.procedures.unrestricated = apoc。*执行此操作，则应使用库，也可以确保如果存在以下设置：
dbms：dbms 。
第一个设置基本上允许提到的过程完全访问数据库，并且仅在需要加载大型库的子集时才使用第二个属性。
另外，请确保直接在
插件目录中直接在可执行的JAR文件中，没有要求为apoc创建单独的目录。我正在使用neo4j 3.5，它对我有用。Assuming that you have pasted the JAR file in the
pluginsdirectory for your database, please make sure that in the configuration file present in theconfdirectory of your database, the following setting is present:dbms.security.procedures.unrestricted=apoc.*Once you do this, then your library should be available to use, also make sure that if the following setting is present:
dbms.security.procedures.whitelist=apoc.coll.*,apoc.load.*then
apoc.nlp.*is also part of it.The first setting basically allows the mentioned procedures full access to the database, and the second property is used only when you need to load a subset of a large library.
Also, make sure that the
Executable JAR fileis directly within thepluginsdirectory, there is no requirement of creating a separate directory forAPOC. I am using neo4j 3.5, and it works for me.修复了将Neo4J DB从4.4降级到4.0的问题！
Fixed the issue with downgrading the neo4j DB from 4.4 to 4.0!