Gerard Klijs

I mostly wanted to be sure since it was based on your initial commit. I'm closing this one in favor of the other.I

@woile just a single `schema-id` header won't do since both the key and the value could require a schema id for serialization. As the maintainer of one of the clients...

@gustavomonarin please expand why you think this. If you use schema registry, the clients are already taking care of removing those bytes at the beginning. If you don't use schema...

@albrechtflo-hg So don't use Schema Registry if you can't use a schema registry client for what you are doing. I don't see how this issue will help a lot, except...

You can also use the 'reduce the complexity when you don't need it' to keep things like they are with the challenges mentioned by Robert. If you only care about...

If this issue is open, anything pro or con is worthwhile. It goes in all sorts of other directions. It seems the advantage of moving things to headers is to...

Hi Jon, If it's something which is possible with the Java serializers, and not with this library, it should be considered a big. For now, I don't really know the...

I reread the issue and it's clear now. It would require both changes to this crate, and the implementation of avro for rust. Currently it's [fixed to not allow hyphens](https://github.com/apache/avro/blob/1652294d5691a895c392e34a2d57dae9701815c2/lang/rust/avro/src/schema.rs#L44)....

@martin-g, you are right that the spec doesn't allow it. But once it's supported by avro-rs, I don't see any harm in allowing it. The default will be to keep...

In that case, let's give him some time to reply. If that is what he meant, we can close this.