Add a parquet payload option to the hosted client - #359
Open
jmkuebler wants to merge 1 commit into
Open
Conversation
|
|
jmkuebler
force-pushed
the
hosted-parquet-payload
branch
from
August 21, 2026 12:52
2e91aea to
7ad8abe
Compare
JSON encoding dominates request time on large tables, and parquet also carries missing values, which strict JSON cannot. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
jmkuebler
force-pushed
the
hosted-parquet-payload
branch
from
August 21, 2026 12:59
7ad8abe to
1a2eee0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
JSON encoding dominates request time on large tables. For example on a large data of 100k rows and 50 features, the JSON path is around 1.6x slower. Parquet encoding already present for the main client https://github.com/PriorLabs/tabpfn-client/blob/main/src/tabpfn_client/client.py#L147
Change Description
Try to be precise. You can additionally add comments to your PR, this might help the reviewer a lot.
If you used new dependencies: Did you add them to
requirements.txt?Who did you ping on Mattermost to review your PR? Please ping that person again whenever you are ready for another review.
Breaking changes
If you made any breaking changes, please update the version number.
Breaking changes are totally fine, we just need to make sure to keep the users informed and the server in sync.
Does this PR break the API? If so, what is the corresponding server commit?
Does this PR break the user interface? If so, why?
Please do not mark comments/conversations as resolved unless you are the assigned reviewer. This helps maintain clarity during the review process.