Github user aalexandrov commented on the pull request:

    https://github.com/apache/flink/pull/605#issuecomment-127558961
  
    @StephanEwen To be honest I'm kind of puzzled and somewhat annoyed that a 
PR that
    
    1) adds a feature that has been on the list for at least 2 years,
    2) has been tested and evaluated thoroughly, and
    3) has been lying around since April and was rebased at least three times
    
    is still open. 
    
    I was also not aware that there is a strict maintainer policy for 
`flink-contrib` commits. IMHO this is a good place to expose non-critical / 
exploratory / unstable features that might be of benefit for multiple users to 
the project. If these turn out the be useful for enough people, I'm sure there 
will be incentive to maintain them. Otherwise there is always the option to 
deprecate and cleanup recent additions to the contrib prior to the next release 
if nobody picked up on them. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to