[
https://issues.apache.org/jira/browse/KAFKA-12574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315142#comment-17315142
]
A. Sophie Blee-Goldman commented on KAFKA-12574:
------------------------------------------------
> This is well documented in
> https://kafka.apache.org/27/documentation/streams/upgrade-guide
Ah, you're right. I must have been on an older version of the docs -- I find
Google often takes me to 2.4 docs for some reason. We need better SEO :/ (I
filed a ticket for this already a while back)
Also not sure how I forgot about EosBetaUpgradeIntegrationTest after spending
so much time trying to help fix it -- sorry for doubting our test coverage and
docs.
Regarding the proposal, I thin users would find it very odd if we moved on to
eos-v2 and then suddenly deprecated it and went back to just "eos" -- makes it
seem like there was a problem with eos-v2. I would be fine with just staying on
eos-v2 though. For one thing it leaves the door open to further developments in
eos that need to be gated by a config, eg eos-v3, if we ever have need for that
again.
> Deprecate eos-alpha
> -------------------
>
> Key: KAFKA-12574
> URL: https://issues.apache.org/jira/browse/KAFKA-12574
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: A. Sophie Blee-Goldman
> Priority: Blocker
> Labels: needs-kip
> Fix For: 3.0.0
>
>
> In KIP-447 we introduced a new thread-producer which is capable of
> exactly-once semantics across multiple tasks. The new mode of EOS, called
> eos-beta, is intended to eventually be the preferred processing mode for EOS
> as it improves the performance and scaling of partitions/tasks. The only
> downside is that it requires brokers to be on version 2.5+ in order to
> understand the latest APIs that are necessary for this thread-producer.
> We should consider deprecating the eos-alpha config, ie
> StreamsConfig.EXACTLY_ONCE, to encourage new. & existing EOS users to migrate
> to the new-and-improved processing mode, and upgrade their brokers if
> necessary.
> Eventually we would like to be able to remove the eos-alpha code paths from
> Streams as this will help to simplify the logic and reduce the processing
> mode branching. But since this will break client-broker compatibility, and
> 2.5 is still a relatively recent version, we probably can't actually remove
> eos-alpha in the near future
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
