You are viewing a plain text version of this content. The canonical link for it is here.

Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2020/07/08 02:33:16 UTC

[GitHub] [arrow] BryanCutler commented on pull request #7619: ARROW-9300: [Java] Separate Netty Memory to its own module

BryanCutler commented on pull request #7619:
URL: https://github.com/apache/arrow/pull/7619#issuecomment-655244616


   I agree that the recommended allocator should still be the netty one for now, so I guess it wouldn't be good to bundle the unsafe allocator as a possible default. I'm good with raising an error then if a default allocator is not on the classpath, as long as it's clear to the user what they need to do. Right now it looks like the error is:
   ```
   java.lang.RuntimeException: No DefaultAllocationManager found on classpath. Can't allocate Arrow buffers.
   ```
   @rymurr would you mind adding something to the message like "it is recommended to add `arrow-memory-netty` or `arrow-memory-unsafe` as a dependency to provide a `DefaultAllocatorManager"?


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org