Update from code changes: document remote ingest request size tuning - #314
Merged
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Tighten the bulk ingest tuning section without dropping information: - Split the multi-clause intro sentence and make the causal link to the timeout error explicit. - Move "whichever comes first" out of a table cell into prose, since it describes both variables rather than one. - Replace the follow-up paragraph, which restated the "What it controls" column and repeated the 1 GiB example shown in the bash block, with a single sentence covering which knob addresses which symptom. - Note that the env vars are the only way to tune this from Python and TypeScript; both bindings hardcode the ClientConfig fields to None. - Correct the closing line: the server stages parts under the shared upload id and merges them atomically, rather than committing each part. - Swap the Info callout for the Enterprise badge used elsewhere. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
Summary
Documents two new environment variables that let you cap the size and duration of individual insert requests when bulk-loading into a remote LanceDB Enterprise table, so large ingests do not exceed the client read timeout.
Changes
performance.mdxcoveringLANCE_CLIENT_MAX_BYTES_PER_REQUEST(default 8 GiB) andLANCE_CLIENT_MAX_REQUEST_DURATION(default half the read timeout), including when to lower each and an exampleexportblock.Context
The remote write path now splits each partition into multiple
insertparts uploaded under one upload id, so a single request no longer needs to stay open for the full partition. The two env vars are auto-picked up by the Python and TypeScript clients and are the user-facing knobs for avoidingoperation timed outerrors on very large ingests. Triggering PR: lancedb/lancedb#3630