julie
julie copied to clipboard
kafka-ops
--dryRun should detect incompatible schemas
This bug/enhancement is more of a general question.
Registering a schema works perfectly well. When an updated schema becomes/is made incompatible and another run is attempted, the --dryRun option does not detect this.
Without --dryRun, the danger is that topics configs ARE updated, while the incompatible schema throws the following just error message:
Schema being registered is incompatible with an earlier schema for subject "context.company.env.source.projectB.bar.avro-value
Now we have an intermediate state in which the cluster is not as described by any descriptor.yaml.
To reproduce, just use the basic example https://github.com/kafka-ops/julie/blob/master/example/descriptor-with-schemas.yaml and change one of the schema's.
Did I miss something or is this indeed the inevitable behavior?
@LeonardoBonacci right now the dry run does not detect anything regarding schemas, but this is clearly an area of improvement for this component. I have linked both issues.