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

ASF GitHub Bot commented on FLINK-3967:
---------------------------------------

Github user StephanEwen commented on the issue:

    https://github.com/apache/flink/pull/2031
  
    Hi @mans2singh !
    
    This looks like a good piece of work, and ReThinkDB is an interesting 
technology!
    An Apache-compatible licence is also good.
    
    We are facing a bit of a maintenance issue right now, though, with a large 
number of new projects. There are so many possible DBs and connectors, and it 
is tough for the community to maintain them all. For that reason, I would 
suggest to stage such contributions of new and interesting connectors.
    
    Could you put this into an standalone GitHub project for now? We would link 
this repository from the Apache Flink website and that way make it visible to 
the Flink community.
    When we see that we get frequent requests for a ReThinkDB, we would like to 
move this to the core Flink code base.
    
    Following this idea, we would end up with frequently used connectors in the 
core Flink repository, and a larger number of connectors in third party 
community repositories. I think that would help the stability of the project 
and all connectors.
    
    Stephan


> Provide RethinkDB Sink for Flink
> --------------------------------
>
>                 Key: FLINK-3967
>                 URL: https://issues.apache.org/jira/browse/FLINK-3967
>             Project: Flink
>          Issue Type: New Feature
>          Components: Streaming, Streaming Connectors
>    Affects Versions: 1.0.3
>         Environment: All
>            Reporter: Mans Singh
>            Assignee: Mans Singh
>            Priority: Minor
>              Labels: features
>             Fix For: 1.1.0
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Provide Sink to stream data from flink to rethink db.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to