zhztheplayer commented on PR #33744: URL: https://github.com/apache/arrow/pull/33744#issuecomment-1387323433
> What is the purpose? I don't think we want this. Manual reference counting of Arrow Java library can become very tricky, even becomes the bottle neck of daily development's efficiency in codes of complicated Java systems that relies on Arrow. This is just one way to make Arrow just be usable somehow in that case. Or a more complete solution I can come up with is to include: 1. A clean-up feature for allocator like this 2. A mechanism to let buffer instances be managed by GC by leveraging e.g. Java weak ref or cleaner toolkit. I understand performance should be considered emphatically in Arrow, however it's true that we must rely on smarter strategies of memory management, more or less, in software development including the development around Arrow. I would suggest we provide such a smarter way to Java developers to let them choose between using manual and using auto. All of the current restrictions including the strong leak-checking can be preserved when user chooses the legacy manual way. Would you think this topic is worth discussion? I am indeed not hurry to get this patch merged until the best solution is shaped. Thanks. -- 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: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
