Hello! Sorry, I have troubles in order to subscribe to [email protected]. .. I apologize if my answer will not fall to the thread. (if someone could help me to sign up on https://lists.apache.org/[email protected] I'd be more than grateful)
The change introduces a new representation, which old implementations can > read raw, but cannot convert to a BigDecimal. Thus, the change is read > raw, but cannot convert to a BigDecimal. Thus, the change is notforwards > compatible. Please note that after my PR such changes become compatible back and forth (see this test <https://github.com/apache/avro/pull/1584/files#diff-b7c2ac2e5de5264e6507ec96c81ff2d585353b5d49f8e1e25ec876390c6f1524R50-R53> ) I think logical type is a very underestimated feature, because unlike many-many other serializer systems avro has the advantage of having reader and writer schemas and logical types can use this advantage. When a user just wants to change network representation of a value from A to B he can just create a logical type, make sure every system is aware about one and the type has conversion from/to A and B. That's it, no more breaking changes and it's pretty much straight forward logic: (sorry, I'm repeating myself because I think it's an important idea) 1. (The most important) This is the same field N, that means it's just different ways to represent the same information. 2. The logical type conversions are deterministic and don't lose any information during conversion from type to an instance and vice versa. As a life example, Imagine, I send a letter to a fiend, I put it in an envelope because it was a local post requirement. But if at some point a delivery company accepts only boxes they can open up the envelope, put my letter into a box and I'll be fine with that as long as my letter remains safe. In general, I don't care about any packaging method during the delivery if my letter reaches the addressee. Thank you very much for your interest in my issue, I'm glad to see such a great community which respects user's needs.
