[Flight client] Allow disabling the creation of a child allocator

Open
#1,051 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
java
Domain
api

Research direction

Start at flight/flight-core/src/main/java/org/apache/arrow/flight/FlightClient.java around line 86 and trace FlightClient.Builder. Verify that the default still creates a child allocator while the new option can use the provided allocator directly. Done when both allocator modes are covered by the relevant Flight client tests.

Written by the indexing model from the issue text.

Description

Type: enhancement
Describe the enhancement requested

FlightClient always creates a child allocator. While this is good in the general case to track memory leaks, this prevents usage scenarios where vectors live longer than the Flight client.

What about adding a FlightClient.Builder#createChildAllocator(boolean) that would allow users to choose whether they want a child allocator (current behavior which will be the default) or directly use the provided one?

I can create a PR for this.

Dominant language
Java
Stars
95
Forks
154
Avg merge
2d 10h
Merged PRs (30d)
11

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/arrow-java

All issues in apache/arrow-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.