[jira] [Created] (KAFKA-20163) MM2: Add log.message.timestamp.before.max.ms and log.message.timestamp.after.max.ms to default config.properties.exclude

[Federico Valeri (Jira)]

Federico Valeri created KAFKA-20163:
---------------------------------------

             Summary: MM2: Add log.message.timestamp.before.max.ms and 
log.message.timestamp.after.max.ms to default config.properties.exclude
                 Key: KAFKA-20163
                 URL: https://issues.apache.org/jira/browse/KAFKA-20163
             Project: Kafka
          Issue Type: Bug
          Components: mirrormaker
    Affects Versions: 4.1.1, 4.0.1, 3.9.1, 3.8.1, 3.7.2, 3.6.2
            Reporter: Federico Valeri
            Assignee: Federico Valeri


The default value of config.properties.exclude in MirrorMaker 2 currently 
includes:

{code}
follower.replication.throttled.replicas,
leader.replication.throttled.replicas,
message.timestamp.difference.max.ms,
message.timestamp.type,
unclean.leader.election.enable,
min.insync.replicas
{code}

After KIP-937 Improve+Message+Timestamp+Validation (Kafka 3.6.0), the config 
message.timestamp.difference.max.ms was deprecated (and removed in 4.0), and 
two new configs were introduced as replacements:

{code}
log.message.timestamp.before.max.ms
log.message.timestamp.after.max.ms
{code}

These two new configs should be added to the default config.properties.exclude 
list, since they serve the same purpose as the already-excluded 
message.timestamp.difference.max.ms and are broker-level configs that should 
not be replicated across clusters.

Additionally, the documentation for this config is hard to read because it 
includes \ in front of every . character. This should be improved for 
readability.




--
This message was sent by Atlassian Jira
(v8.20.10#820010)