idelpivnitskiy commented on PR #36211: URL: https://github.com/apache/arrow/pull/36211#issuecomment-1625888920
Thanks for response @lidavidm, I understand your general release cadence, but would like to highlight that this incompatibility does not allow upgrading Netty version for anything else in the same classpath. It will be great for the project if Arrow can find a way to either backport it to older versions (maybe `MethodHandler`s with runtime Netty version check can help), or find a way to stop using **internal** Netty API completely (preferred approach). In the meanwhile, are there any known downsides or issues for users switching from `arrow-memory-netty` to `arrow-memory-unsafe`? I couldn't find much information about side-effects. Assuming that they are interchangeable. -- 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]
