-
Notifications
You must be signed in to change notification settings - Fork 53
Avoid closing/freeing struct-like object instances on import #765
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Type: enhancement
New feature or request
Comments
pepijnve
added a commit
to datadobi/arrow-java
that referenced
this issue
May 23, 2025
pepijnve
added a commit
to datadobi/arrow-java
that referenced
this issue
May 23, 2025
…orted BaseStruct objects
pepijnve
added a commit
to datadobi/arrow-java
that referenced
this issue
May 27, 2025
…orted BaseStruct objects
pepijnve
added a commit
to datadobi/arrow-java
that referenced
this issue
May 27, 2025
…orted BaseStruct objects
pepijnve
added a commit
to datadobi/arrow-java
that referenced
this issue
May 27, 2025
…orted BaseStruct objects
pepijnve
added a commit
to datadobi/arrow-java
that referenced
this issue
May 27, 2025
…orted BaseStruct objects
pepijnve
added a commit
to datadobi/arrow-java
that referenced
this issue
May 27, 2025
…orted BaseStruct objects
lidavidm
pushed a commit
that referenced
this issue
May 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the enhancement requested
Currently the various import methods in
org.apache.arrow.c.Data
callclose
on theBaseStruct
arguments they receive as parameter. This prevents callers from reusing these objects multiple times. Since the caller needs to allocate these objects themselves, it seems like it would be more consistent to also expect the caller to free them. This works well in combination with try-with-resources.See related discussion #763.
The text was updated successfully, but these errors were encountered: