JingsongLi commented on PR #7077: URL: https://github.com/apache/paimon/pull/7077#issuecomment-3782698103
> > I checked the current implementation and it seems to be correct. Our Avro format has a very strange mapping relationship, the mapping on the Java side is reversed compared to standard... > > If that’s indeed the case, here’s my understanding: > > * I fully agree with your earlier point: "Whatever Java does, Python should align with. We need to ensure compatibility." This is a principle we must follow for ecosystem consistency. > * We can address the non-standard mapping in a separate future PR, similar to how Flink handled it: introduce a new config like `avro.timestamp_mapping.legacy` (defaulting to true) to preserve backward compatibility, while allowing users to opt into the standard-compliant behavior when ready. > What do you think? I agree with you about "avro.timestamp_mapping.legacy", we can introduce it in next PR for both Java and Python. -- 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]
