[
https://issues.apache.org/jira/browse/AIRFLOW-5920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008881#comment-17008881
]
Timothy Findlay commented on AIRFLOW-5920:
------------------------------------------
This feature deserves more thought than passing interest.
At a minimum the Neo4j organisation should be engaged to approve use of the
trademark.
They should also provide resources to support development and mainteance of
this functionality within Apache Airflow.
The re-work at this stage is not worth pursuing. A fresh fork/PR can be started
by interested parties if there is sufficient demand.
> Add support to execute OpenCypher query against Neo4j
> -----------------------------------------------------
>
> Key: AIRFLOW-5920
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5920
> Project: Apache Airflow
> Issue Type: New Feature
> Components: hooks, operators
> Affects Versions: 1.10.7
> Reporter: Timothy Findlay
> Priority: Major
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> As a DAG developer
> I want to create DAG tasks to execute OpenCypher queries against a graph
> database
> So that the output can be used elsewhere in a DAG / business
> UPDATE:
> Feedback through the development effort has highlighted some considerations:
> * AIP-21 and any other future plans for the Apache Airflow project need to
> be taken into consideration
> * A complete featrue set should be implemented considering all use cases:
> ** Export to common formats
> ** Importing data from common formats
> ** DML queries to manipulate the graph
> * A suitable connection definition should be implmented for Neo4J (not JDBC)
> ** Connection should support bolt and bolt+routing protocols
> ** Connection pooling should be managed by the hook to ensure correct
> transation bounaries within the session
> * A detailed failure mode analysis should also be submitted including:
> ** Failed connection handling
> ** Query execution handling
> ** Transaction handling for multiple queries
> ** Data integrity checking (import/export validation)
> * Considerations to ensure export does not fill the local disk
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
