[
https://issues.apache.org/jira/browse/KAFKA-16388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-16388.
Fix Version/s: 3.8.0
Resolution: Fixed
> add production-ready test of 3.3 - 3.6
PoAn Yang created KAFKA-16413:
-
Summary: Add tests for FileLock
Key: KAFKA-16413
URL: https://issues.apache.org/jira/browse/KAFKA-16413
Project: Kafka
Issue Type: Test
Reporter: PoAn
[
https://issues.apache.org/jira/browse/KAFKA-16314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanskar Jhajharia resolved KAFKA-16314.
---
Fix Version/s: 3.8.0
Reviewer: Justine Olshan
Resolution: Fixed
Yes Luke,
I am also in favour of creating producer snapshot at run time if
foundEmpty as this would only be required for topics migrated from < 2.8
version. This will not break the existing contract with the plugin. Yes,
metrics do not make sense here as of now.
Greg, @Kamal Chandraprakash WDYT
Hi Arpit,
I'm in favor of creating an empty producer snapshot since it's only for
topics <= v2.8.
About the metric, I don't know what we expect users to know.
I think we can implement with the empty producer snapshot method, without
the metric.
And add them if users are requested it.
WDYT?
Thank
