[
https://issues.apache.org/jira/browse/KAFKA-18209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18008000#comment-18008000
]
Ksolves India Limited commented on KAFKA-18209:
-----------------------------------------------
Hi [~mimaison], after review of [PR|https://github.com/apache/kafka/pull/18201]
To help us better align with your expectations for broader improvements, could
you please provide more specific guidance on:
* Which areas or classes do you think need further cleanup or restructuring?
* If there’s a subject matter expert for this module, could you suggest
someone we could discuss proposed changes with for deeper context?
> Cleanup __transaction_state config logic
> ----------------------------------------
>
> Key: KAFKA-18209
> URL: https://issues.apache.org/jira/browse/KAFKA-18209
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Mickael Maison
> Priority: Major
>
> The transaction state topic must have specific configurations. Currently
> these are spread across several classes. For example we have some fields in
> TransactionLog , and some in the
> TransactionStateManager.transactionTopicConfigs() method.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
