We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
The IPC writer typically tries to avoid writing unreferenced data, e.g. re-encoding offsets for StringArray, ListArray, etc... see write_array_data.
write_array_data
Currently the IPC writer writes view data types as is, potentially including significant unreferenced data.
Describe the solution you'd like
I think by default the IPC writer should at least invoke the GC API, and potentially deduplicate them. We could potentially make this configurable.
Describe alternatives you've considered
Additional context
Potentially some overlap with
interleave
StringViewArray
FYI @alamb @XiangpengHao
The text was updated successfully, but these errors were encountered:
StringView
I agree this would be a good feature
Sorry, something went wrong.
No branches or pull requests
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
The IPC writer typically tries to avoid writing unreferenced data, e.g. re-encoding offsets for StringArray, ListArray, etc... see
write_array_data
.Currently the IPC writer writes view data types as is, potentially including significant unreferenced data.
Describe the solution you'd like
I think by default the IPC writer should at least invoke the GC API, and potentially deduplicate them. We could potentially make this configurable.
Describe alternatives you've considered
Additional context
Potentially some overlap with
interleave
kernel with deep copy buffers forStringViewArray
#7184FYI @alamb @XiangpengHao
The text was updated successfully, but these errors were encountered: