[
https://issues.apache.org/jira/browse/KAFKA-13291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhihao Wang updated KAFKA-13291:
--------------------------------
Description:
Application Evolvement is an open problem in streaming processing. We present a
*stateful blue/green deployment* to address it. To our knowledge, this is the
first general way to handle streaming application evolvement.
Here is the design doc:
[https://docs.google.com/document/d/1QCnhtrgcMRUWCw_SO7vmfj6dyzbdjIAxWkJzKK4d508|https://docs.google.com/document/d/1QCnhtrgcMRUWCw_SO7vmfj6dyzbdjIAxWkJzKK4d508/edit?usp=sharing]
The design requires a daemon job to keep syncing between two Kafka topics with
the semantics mentioned in doc. Please review the document and to see if Kafka
community can support such a daemon job.
P.S. [A related ticket |https://issues.apache.org/jira/browse/FLINK-24257]is
also sent to Flink community for suggestions.
was:
Application Evolvement is an open problem in streaming processing. We present a
*stateful blue/green deployment* to address it. To our knowledge, this is the
first general way to handle streaming application evolvement.
Here is the design doc:
[https://docs.google.com/document/d/1QCnhtrgcMRUWCw_SO7vmfj6dyzbdjIAxWkJzKK4d508|https://docs.google.com/document/d/1QCnhtrgcMRUWCw_SO7vmfj6dyzbdjIAxWkJzKK4d508/edit?usp=sharing]
The design requires a daemon job to keep syncing between two Kafka topics with
the semantics mentioned in doc. Please review the document and to see if Kafka
community can support such a daemon job.
> Using Stateful Blue/Green Deployment to handle Application Evolvement
> ---------------------------------------------------------------------
>
> Key: KAFKA-13291
> URL: https://issues.apache.org/jira/browse/KAFKA-13291
> Project: Kafka
> Issue Type: Improvement
> Reporter: Zhihao Wang
> Priority: Major
>
> Application Evolvement is an open problem in streaming processing. We present
> a *stateful blue/green deployment* to address it. To our knowledge, this is
> the first general way to handle streaming application evolvement.
> Here is the design doc:
> [https://docs.google.com/document/d/1QCnhtrgcMRUWCw_SO7vmfj6dyzbdjIAxWkJzKK4d508|https://docs.google.com/document/d/1QCnhtrgcMRUWCw_SO7vmfj6dyzbdjIAxWkJzKK4d508/edit?usp=sharing]
>
> The design requires a daemon job to keep syncing between two Kafka topics
> with the semantics mentioned in doc. Please review the document and to see if
> Kafka community can support such a daemon job.
>
> P.S. [A related ticket |https://issues.apache.org/jira/browse/FLINK-24257]is
> also sent to Flink community for suggestions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
