This processor is designed to execute queries in either the Cypher query language or the Tinkerpop Gremlin DSL. It delegates most of the logic to a configured client service that handles the interaction with the remote data source. All of the output is written out as JSON data.
cypher, neo4j, graph, network, insert, update, delete, put, get, node, relationship, connection, executor, gremlin, tinkerpop
In the list below, the names of required properties appear in bold. Any other properties (not in bold) are considered optional. The table also indicates any default values, and whether a property supports the NiFi Expression Language.
| Display Name | API Name | Default Value | Allowable Values | Description |
|---|---|---|---|---|
| Client Service | graph-client-service | Controller Service API: GraphClientService Implementations: Neo4JCypherClientService TinkerpopClientService | The graph client service for connecting to the graph database. | |
| Graph Query | graph-query | Specifies the graph query. If it is left blank, the processor will attempt to get the query from body. Supports Expression Language: true (will be evaluated using flow file attributes and Environment variables) |
| Name | Description |
|---|---|
| success | Successful FlowFiles are routed to this relationship |
| failure | Failed FlowFiles are routed to this relationship |
| original | If there is an input flowfile, the original input flowfile will be written to this relationship if the operation succeeds. |
| Name | Description |
|---|---|
| graph.error.message | GraphDB error message |
| graph.labels.added | Number of labels added |
| graph.nodes.created | Number of nodes created |
| graph.nodes.deleted | Number of nodes deleted |
| graph.properties.set | Number of properties set |
| graph.relations.created | Number of relationships created |
| graph.relations.deleted | Number of relationships deleted |
| graph.rows.returned | Number of rows returned |
| query.took | The amount of time in milliseconds that the querytook to execute. |