steven-aerts commented on pull request #880:
URL: https://github.com/apache/avro/pull/880#issuecomment-638046889
Hi @zeshuai007 ,
If I understand you well, you are saying that in the example given above.
The reader schema and the writer schema are compliant with the specification.
But the intermediate schema, where the writer schema is rewritten to match
the reader schema, is not. I was not aware that this needed to be the case.
I also think there are examples which currently work which also generate an
invalid intermediate schema.
For example, take the following writer schema: `[int, float]` and read it
with the reader schema `[float]`.
Then you also see that the intermediate schema has two fields of the same
type which is not allowed for a normal schema, but it does and should exist in
the intermediate schema.
So this is why I thought we could do it like that, as I saw the above logic
as a precedence.
But maybe I am missing something?
Thanks,
Steven
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
