[
https://issues.apache.org/jira/browse/FLINK-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177593#comment-15177593
]
Robert Metzger commented on FLINK-2941:
---------------------------------------
I had a quick offline chat with [~StephanEwen] and [~vkalavri] about this. We
agreed that its legally too unclear whether we can add a test-scoped code into
our project or not (the licenses don't distinguish between runtime and test
bindings).
Having the connector code and the test separate would be an ugly approach.
Therefore, we propose to keep the code outside of Flink's main repository. You
could either host the code in your own GitHub repository and link it from here:
http://flink.apache.org/community.html#third-party-packages
We could also create a new repo here: https://github.com/project-flink and then
link it from the Flink website. In the "project-flink" project, I could also
help to set up deployment to maven central.
What do you think?
> Implement a neo4j - Flink/Gelly connector
> -----------------------------------------
>
> Key: FLINK-2941
> URL: https://issues.apache.org/jira/browse/FLINK-2941
> Project: Flink
> Issue Type: New Feature
> Components: Gelly
> Reporter: Vasia Kalavri
> Assignee: Martin Junghanns
> Labels: requires-design-doc
>
> By connecting Flink/Gelly with a graph database like neo4j we can facilitate
> interesting use-cases, like:
> - use neo4j as an input source, i.e. read the complete graph or a subgraph
> from a neo4j database, import it into Flink and run a graph analysis task
> with Gelly.
> - use neo4j as a sink, i.e. perform ETL on some data in Flink to create a
> graph and insert the graph in a neo4j database for further querying.
> We have started a discussion on possible implementations and have looked into
> similar projects, e.g. connecting neo4j to Spark. Some initial thoughts and
> experiences can be found in [this
> document|https://docs.google.com/document/d/13qT_e-y8aTNWQnD43jRBq1074Y1LggPNDsic_Obwc28/edit?usp=sharing].
> Please, feel free to comment and add ideas! I will also start a discussion
> in the mailing list with more concrete problems that we would like to get
> feedback on.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
