Skip to content

[EXP]: Move hight level feather functionality to ipc - #56

Draft
rok wants to merge 2 commits into
mainfrom
move_hight_level_feather_functionality_to_ipc
Draft

[EXP]: Move hight level feather functionality to ipc#56
rok wants to merge 2 commits into
mainfrom
move_hight_level_feather_functionality_to_ipc

Conversation

@rok

@rok rok commented Aug 4, 2026

Copy link
Copy Markdown
Owner

This is for discussion purposes

@github-actions

github-actions Bot commented Aug 4, 2026

Copy link
Copy Markdown

Thanks for opening a pull request!

This pull request has been automatically converted to a draft because its title doesn't match Arrow's required format.

If this is not a minor PR. Could you open an issue for this pull request on GitHub? https://github.com/apache/arrow/issues/new/choose

Opening GitHub issues ahead of time contributes to the Openness of the Apache Arrow project.

Then could you also rename the pull request title in the following format?

GH-${GITHUB_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}

or

MINOR: [${COMPONENT}] ${SUMMARY}

After updating the title, you can mark the pull request as ready for review.

See also:

@rok
rok force-pushed the move_hight_level_feather_functionality_to_ipc branch 4 times, most recently from 4e1b0ce to 25b78ea Compare August 4, 2026 20:40
@rok
rok force-pushed the move_hight_level_feather_functionality_to_ipc branch from 25b78ea to 2a53b64 Compare August 5, 2026 16:55
Keep the public IPC reader limited to Arrow IPC files and retain Feather V1 handling in the compatibility module. Finalize the new API with keyword-only options, max_chunksize validation, and an uncompressed default while preserving Feather V2 behavior. Defer broad Feather API deprecation until the replacement has shipped.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant