[jira] [Updated] (NIFI-12855) Add more information to provenance events to facilitate full graph traversal

2024-03-13 Thread Matt Burgess (Jira)


 [ 
https://issues.apache.org/jira/browse/NIFI-12855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Burgess updated NIFI-12855:

Description: 
Although NiFi has a capability in the UI to issue and display lineage queries 
for provenance events, it is not a complete graph that can be traversed if for 
example provenance events were stored in a graph database. The following 
features should be added:

- A reference in a provenance event to any parent events ("previousEventIds")
- Add methods to GraphClientService to generate queries/statements in popular 
graph languages such as Tinkerpop/Gremlin, Cypher, and SQL
- Add ArcadeDB service as reference implementation for SQL generation

  was:
Although NiFi has a capability in the UI to issue and display lineage queries 
for provenance events, it is not a complete graph that can be traversed if for 
example provenance events were stored in a graph database. The following 
features should be added:

- A reference in a provenance event to any parent events ("previousEventIds")
- Add methods to GraphClientService to generate queries/statements in popular 
graph languages such as Tinkerpop/Gremlin, Cypher, and SQL
- Add explicit references to the relationship to which the FlowFile was 
transferred
- Add ArcadeDB service as reference implementation for SQL generation


> Add more information to provenance events to facilitate full graph traversal
> 
>
> Key: NIFI-12855
> URL: https://issues.apache.org/jira/browse/NIFI-12855
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Matt Burgess
>Assignee: Matt Burgess
>Priority: Major
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Although NiFi has a capability in the UI to issue and display lineage queries 
> for provenance events, it is not a complete graph that can be traversed if 
> for example provenance events were stored in a graph database. The following 
> features should be added:
> - A reference in a provenance event to any parent events ("previousEventIds")
> - Add methods to GraphClientService to generate queries/statements in popular 
> graph languages such as Tinkerpop/Gremlin, Cypher, and SQL
> - Add ArcadeDB service as reference implementation for SQL generation



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (NIFI-12855) Add more information to provenance events to facilitate full graph traversal

2024-03-05 Thread Matt Burgess (Jira)


 [ 
https://issues.apache.org/jira/browse/NIFI-12855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Burgess updated NIFI-12855:

Status: Patch Available  (was: In Progress)

> Add more information to provenance events to facilitate full graph traversal
> 
>
> Key: NIFI-12855
> URL: https://issues.apache.org/jira/browse/NIFI-12855
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Reporter: Matt Burgess
>Assignee: Matt Burgess
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Although NiFi has a capability in the UI to issue and display lineage queries 
> for provenance events, it is not a complete graph that can be traversed if 
> for example provenance events were stored in a graph database. The following 
> features should be added:
> - A reference in a provenance event to any parent events ("previousEventIds")
> - Add methods to GraphClientService to generate queries/statements in popular 
> graph languages such as Tinkerpop/Gremlin, Cypher, and SQL
> - Add explicit references to the relationship to which the FlowFile was 
> transferred
> - Add ArcadeDB service as reference implementation for SQL generation



--
This message was sent by Atlassian Jira
(v8.20.10#820010)