Github user haoch commented on the issue:
    @StephanEwen thanks for the comments, I think it's both ok to keep this in 
the core or as an separated project, but the concern is it maybe better for 
community development to centralize qualified libraries togather. As an 
alternative solution for too test stability and dead code, may it possible to 
create another code repository say "flink-library"?
    **BTW: here are the answers to your questions one by one:**
    > How complete is the implementation?
    Siddhi is a rich-featured CEP and has its own community, and maybe almost 
the only open source CEP solutions compatible with Apache License. And this 
library `flink-siddhi` is mainly focused on bring siddhi's capability to flink 
users seamlessly by:
    - Integrate Siddhi CEP runtime with flink lifecycle
    - Schema and DataStream source mapping
    - State management and fault-tolerant.
    So I think it would be extremely light-weight but useful, and the current 
implementation should be almost completed. 
    > Would you be up for maintaining this code?
    Sure, first of all, personally I am very willing to keep continuously 
contributing to Flink project in any way.  
    And also we used siddhi with distributed streaming system a lot in 
production, and currently considering to support flink as well under 
consideration of better state management and window supporting. So I would 
continuously maintain the code if merged, it not, I would maintain at as well to make sure it's workable.
    > Are you building this as an experiment, or building a production use case 
based on Siddhi on Flink?
    We use siddhi with streaming environment in production a lot, currently 
supports storm and spark streaming, and also consider extending to Flink.

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 or file a JIRA ticket
with INFRA.

Reply via email to