izemlyanskiy commented on pull request #1584: URL: https://github.com/apache/avro/pull/1584#issuecomment-1083642357
Cool, I'm glad to see this PR is not stalled and more people are involved. :+1: Could anyone answer my previous question about `ResolvingDecoder#resolve`? I think we face here 2 problems: * the first is BigDecimal by default is decoded as a string, but the decimal logical type does not support string conversion, thus we have inconsistency. * the second is some kind of new way how to make schema migration if you just need to change the encoding type. With my changes, you can introduce a new logical type for a field that would support an old format and a new format. At the method `ResolvingDecoder#resolve` I told above, we can check if the type conversion is valid or not, or we can do the same during the `ResolvingAction`. I think it's a sort of debate like runtime vs compile-time resolution. That's why I'd like to hear community comments on this. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
