[
https://issues.apache.org/jira/browse/KAFKA-19376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17959709#comment-17959709
]
Lucas Brutschy commented on KAFKA-19376:
----------------------------------------
* Online migration
there is no explicit way to detect that a user is attempting a migration. We
will log an error message though once the client tries to join the group.
* Topology Updates
Similar as above. Topology update just means the application is started as
usual, but with a changed topology. We will detect this and log an error.
* High Availability Assignor
This is the default, and usually the only option. So there is no configuration
to error out on
> Throw an error message if any unsupported feature is used with KIP-1071
> -----------------------------------------------------------------------
>
> Key: KAFKA-19376
> URL: https://issues.apache.org/jira/browse/KAFKA-19376
> Project: Kafka
> Issue Type: Sub-task
> Components: streams
> Reporter: Lucas Brutschy
> Assignee: Lucas Brutschy
> Priority: Major
>
> We should be mindful of ours users and let them know early if they are using
> an unsupported feature in 4.1.
> Unsupported features:
> - Regular expressions
> - Warm-up replicas (high availability assignor)
> - Static membership
> - Standby replicas enabled through local config
> - Named topologies (already checked)
> - Non-default kafka-client supplier
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
