This is an automated email from the ASF dual-hosted git repository.
hansva pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-hop.git
The following commit(s) were added to refs/heads/master by this push:
new 4fabfd0 [DOC] fix variable NEO4J_LOGGING_CONNECTION
4fabfd0 is described below
commit 4fabfd05436387885fc535fa5244fc59414b46f7
Author: Hans Van Akelyen <[email protected]>
AuthorDate: Mon Jun 21 10:22:02 2021 +0200
[DOC] fix variable NEO4J_LOGGING_CONNECTION
---
docs/hop-user-manual/modules/ROOT/pages/technology/neo4j/index.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/docs/hop-user-manual/modules/ROOT/pages/technology/neo4j/index.adoc
b/docs/hop-user-manual/modules/ROOT/pages/technology/neo4j/index.adoc
index 45a7d38..fd66e27 100644
--- a/docs/hop-user-manual/modules/ROOT/pages/technology/neo4j/index.adoc
+++ b/docs/hop-user-manual/modules/ROOT/pages/technology/neo4j/index.adoc
@@ -30,7 +30,7 @@ Hop supports Neo4j through the following metadata objects
== Perspective: Execution lineage
You can use Neo4j to store logging and execution lineage of your workflows and
pipelines.
-The way you do this is simply by setting the variable NEO_LOGGING_CONNECTION
to the name of the Neo4j Connection where you want the logging and lineage to
be written to.
+The way you do this is simply by setting the variable
`NEO4J_LOGGING_CONNECTION` to the name of the Neo4j Connection where you want
the logging and lineage to be written to.
The Neo4j plugin offers a separate perspective to query this logging and
lineage information. For example, it allows you to quickly jump to the place
where an error occurred. This neat trick is performed by asking the database
to find the shortest path between and execution node where an error occurred
and without children and the "grand parent" node. The path you get is the
exact path that was followed from for example the "grand parent" workflow to
the exact transform where an error [...]
