docs(config): clarify metadata and conversion file size limits#61478
Merged
AndyScherzinger merged 1 commit intoJun 21, 2026
Merged
Conversation
- correct unit for metadata_max_filesize to match implementation (MiB) - wording/clarity including resource impact Signed-off-by: Josh <josh.t.richards@gmail.com>
joshtrichards
requested review from
ArtificialOwl,
enjeck,
solracsf,
st3iny and
susnux
joshtrichards
requested review from
icewind1991,
leftybournes and
salmart-dev
and removed request for
a team
Member
Author
|
/backport to stable34 |
4 tasks
solracsf
approved these changes
Jun 20, 2026
st3iny
approved these changes
Jun 20, 2026
joshtrichards
added
4. to release
AndyScherzinger
deleted the
jtr/docs-file-metadata-and-convert-size-limits
branch
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
4 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.
Summary
Changes:
metadata_max_filesizeto match implementation (MiB)PR #54951 corrected the implementation of
metadata_max_filesizeto use MiB-based sizing instead of MB. This update aligns the corresponding documentation with the implementation and expands the resource-usage wording to better reflect how file metadata generation behaves in practice.It also updates the similar
max_file_conversion_filesizeentry for the File Conversion provider feature. The unit was already correct there, but the docs now also notes the potential impact on resource usage and timeouts, based on discussion in #49922 (e.g. timeouts) and the implementations.Checklist
3. to review, feature component)stable32)AI (if applicable)