[jira] [Commented] (FLINK-2941) Implement a neo4j - Flink/Gelly connector

["Vasia Kalavri (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15175434#comment-15175434 ] 

Vasia Kalavri commented on FLINK-2941:
--------------------------------------

Hey [~mju],
thanks for working on this! I'm very happy we have working input and output formats for Neo4j :D
Regarding the licenses, afaik we cannot have a GPL dependency in Flink. So, I see two solutions here:
(1) we add the Neo4j connector to flink-batch-connectors without tests. Examples don't depend on anything GPL licensed, right?
(2) we keep this as an external flink package.

I'm personally in favor of (1), but I would like to hear other people's opinions. It seems that there are other batch connectors without tests btw, e.g. hcatalog and hbase.

> 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)