zhztheplayer commented on code in PR #14506: URL: https://github.com/apache/arrow/pull/14506#discussion_r1019457524
########## java/memory/memory-netty/src/test/java/org/apache/arrow/memory/TestForeignAllocation.java: ########## @@ -0,0 +1,72 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one or more + * contributor license agreements. See the NOTICE file distributed with + * this work for additional information regarding copyright ownership. + * The ASF licenses this file to You under the Apache License, Version 2.0 + * (the "License"); you may not use this file except in compliance with + * the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ + +package org.apache.arrow.memory; + +import static org.junit.Assert.assertEquals; +import static org.junit.Assert.assertTrue; + +import org.apache.arrow.memory.util.MemoryUtil; +import org.junit.After; +import org.junit.Before; +import org.junit.Test; + +public class TestForeignAllocation { + BufferAllocator allocator; + + @Before + public void before() { + allocator = new RootAllocator(); + } + + @After + public void after() { + allocator.close(); + } + + @Test + public void wrapForeignAllocation() { + final long bufferSize = 16; + UnsafeForeignAllocationManager allocationManager = new UnsafeForeignAllocationManager(allocator, bufferSize); + try { + assertEquals(0, allocator.getAllocatedMemory()); + ArrowBuf buf = allocator.wrapForeignAllocation(allocationManager); Review Comment: `new AllocationManager(allocator)` creates an zero ref count owning ledger. I guess that ledger may lead to unexpected behavior when user call `wrapForeignAllocation(...)` from another allocator. Maybe decoupling allocator from AllocationManager's constructor (not the manager itself) will be a solution. -- 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]
