Kafka topic configuration properties do not affect the production instance

 Fidelity has observed that Kafka topic configuration properties from the Nuxeo config file do not have any impact on the production instance. Once a topic is created, it never gets adjusted to new settings. As a result, a manual ticket needs to be issued to Nuxeo to either recreate the topic (which involves a loss of data) or find a way to adjust the Kafka topic settings without data loss. I’m not entirely sure of the step-by-step process to reproduce this issue, but Hemanth from the Fidelity team explained it to me. They expressed frustration as it took them a considerable amount of time to identify and address the problem.”

Muppala Narayana, Hemanth <Hemanth.MuppalaNarayana@fmr.com>

<extension target="org.nuxeo.runtime.stream.service" point="streamProcessor">
    <streamProcessor name="fidRetentionStart" class="fidelity.ctg.csp.action.TimeBasedRetentionStartAction"
                     defaultConcurrency="${nuxeo.bulk.action.fidRetentionStart.defaultConcurrency:=1}"
                     defaultPartitions="${nuxeo.bulk.action.fidRetentionStart.defaultPartitions:=1}">
        <!-- continue on failure, because failure to start retention doesn't give us an inconsistent state -->
        <policy name="default" maxRetries="20" delay="1s" maxDelay="60s" continueOnFailure="true" />
    </streamProcessor>
</extension>