Hi All, Posting for visibility.
In PR [1955] I propose to avoid serializing null property values to clients. This change does have some risk of breaking existing clients, but the risk is minimal IMHO. Only clients that rely on observing explicit records for null properties are affected. This should not normally be problematic, because when processing JSON, absent properties are normally treated the same way as null properties. The benefit of this approach is significant, though. It enables introducing new optional fields to API objects without affecting existing clients. Unless the optional field is configured, old clients will not "see" the new property name and will be able to process JSON data without code changes. WDYT? [1955] https://github.com/apache/polaris/pull/1955 Thanks, Dmitri.