[
https://issues.apache.org/jira/browse/KAFKA-14408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-14408.
-------------------------------------
Resolution: Won't Fix
I don't think we should do this – it would produce way too many logs, what not
only slows down tests, but is also a problem with regard to storage.
Also, the bug did not crash Kafka Streams, as the logging framework did catch
the NPE and effectively swallowed it. So while annoying, it really only
affected the produced logs, but did not have any actually production impact.
> Consider enabling DEBUG log level on tests for Streams
> ------------------------------------------------------
>
> Key: KAFKA-14408
> URL: https://issues.apache.org/jira/browse/KAFKA-14408
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Jorge Esteban Quilcate Otoya
> Priority: Major
>
> Ideally logging should not trigger any side effect, though we have found that
> it did for https://issues.apache.org/jira/browse/KAFKA-14325.
> This ticket is to request if we should consider enabling higher logging
> levels (currently INFO) during tests to validate these paths.
> There may be some additional costs on log file sizes and verbosity, so it's
> open to discuss if this is worth it or not, and whether to expand this to
> other components as well.
> Additional discussion:
> https://github.com/apache/kafka/pull/12859#discussion_r1027007714
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
