erratic-pattern commented on issue #5731: URL: https://github.com/apache/arrow-rs/issues/5731#issuecomment-2123014839
An additional remark on the 1st point above (Have a clear rationale for or against `Any` wrapping of message types), I don't see a clear justification for or against `Any` wrapping from a technical standpoint. I think we just need to choose one and stick with it across the spec. My preference would be no `Any` wrapping because it is simpler. However, I think the best choice would be whichever change results in the smallest amount of breaking code in the current implementations. We should look at *all* clients across *all* messages types and see what they are currently doing, then choose the `Any` wrapping behavior that results in the fewest changes. Depending on what clients currently do, this could be a much larger and more breaking change than just changing one particular message type. But, for example, if only one client is the odd one out in terms of `Any` wrapping semantics, we can avoid a lot of breakage by simply changing that one client to match the behavior of the others. But to do that we need a clear picture of what each client is doing across all message types. -- 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]
