SchemaInfoImpl includes timestamp when using "equals". Should this be?

[jsteggink]

Hi,

We are running into in issue using the pulsar-spark connector where it complains about incompatible schemas. The reason why it it's incompatible is because it says the timestamp field doesn't match. However, since schemas are generated automatically, we can't influence the timestamp.

Why is the timestamp useful when comparing schemas? The name of the schema is excluded in the equals function. Shouldn't the timestamp also be excluded?

pulsar/pulsar-common/src/main/java/org/apache/pulsar/client/impl/schema/SchemaInfoImpl.java

Line 64 in 9bb3a21

private long timestamp;

Best,
Jeroen