通告

2018-07-13 18:19:20
张帜
188
最后编辑:张帜 于 2018-07-13 19:02:37
WARNING

Neo4j 3.2 has increased security for procedures and functions (aka sandboxing). Procedures that use internal APIs have to be allowed in $NEO4J_HOME/conf/neoj4.conf  with, e.g. dbms.security.procedures.unrestricted=apoc.trigger.*,apoc.meta.*  for security reasons (or apoc.*  for all).

If you want to use this via docker, you need to amend -e NEO4J_dbms_security_procedures_unrestricted=apoc.\\\*  to your docker run …  command. The three backslashes are necessary to prevent wildcard expansions.

NOTE

You can also whitelist procedures and functions in general to be loaded using: dbms.security.procedures.whitelist=apoc.coll.*,apoc.load.*

Neo4j 3.2 introduces user defined aggregation functions, we will use that feature in APOC in the future, e.g. for export, graph-algorithms and more, instead of passing in Cypher statements to procedures.

Please note that about 70 procedures have been turned from procedures into user defined functions. This includes, apoc.date.* apoc.number.*, apoc.coll.*, apoc.map.*  and some more packages. See, this  issue for a list.

NOTE
Go here for documentation for APOC for Neo4j version  3.0.x  3.1.x  3.2.x  3.3.x
apoc

Neo4j 3.0 introduced the concept of user defined procedures. Those are custom implementations of certain functionality, that can’t be (easily) expressed in Cypher itself. Those procedures are implemented in Java and can be easily deployed into your Neo4j instance, and then be called from Cypher directly.

The APOC library consists of many (about 300) procedures to help with many different tasks in areas like data integration, graph algorithms or data conversion.


发表评论
评论通过审核后显示。