Skip to content

Missing documentation: PATCH replaces chunks + 1MB gateway limit blocks large document ingestion #85

Closed

Description

@ni-dz

Issue description

Description:

While working with the Vector API for larger-scale ingestion, I encountered behavior that is currently not clearly documented and may lead to confusion during implementation.

It would be great if this could be clarified in the documentation to improve usability and developer experience.

Observed issues:

  • There appears to be a ~1MB request size limit (API gateway), which results in 413 Payload Too Large errors for larger uploads.
  • The PATCH /documents endpoint replaces existing chunks instead of appending them, making incremental uploads to a single document impossible.

Why this is confusing:

  • The documentation states a limit of 200,000 chunks per document, which suggests that incremental ingestion should be supported.
  • The PATCH endpoint is described as updating chunks, but it is not clearly stated that existing chunks are fully overwritten.
  • The gateway request size limitation is not mentioned in the documentation.

Current workaround:

  • Splitting data into multiple documents (or collections)
  • Using metadata or collection-based filters during retrieval

Suggested improvements:

  • Document the ~1MB request size limit and its implications
  • Clarify that PATCH replaces chunks and does not support appending
  • Provide recommended ingestion patterns / best practices for large datasets
  • Clarify how the 200k chunk limit can realistically be achieved (e.g., via Pipeline API, if applicable)

Affected pages:

Feedback Type (Optional)

content gaps

Page Title on SAP Help Portal (prefilled)

Update a Document

Page URL on SAP Help Portal (prefilled)

https://help.sap.com/docs/sap-ai-core/generative-ai/update-document-adaa7cc44d334d89baf1ef666ac3158c?locale=en-US

Activity

  1. self-assigned this
    on Apr 27, 2026
  2. karu-0711 commented on Apr 27, 2026

    @karu-0711
    Contributor

    Hi @ni-dz . Thank you for your feedback! We’ll look into it and come back to you if we have any questions.

  3. Niveth-T commented on Jun 1, 2026

    @Niveth-T

    @ni-dz Thankyou for your contribution.

    We have updated the content and will be published in the near future.

  4. sap-doc-bot commented on Jun 1, 2026

    @sap-doc-bot

    Thank you for your valuable feedback contribution, @ni-dz! So that we can recognize your contribution in the SAP Community, please check your SAP Community user ID (this is a number). To do so, navigate to your personal settings page, open the menu below your user picture in the upper right corner, and choose My content. Copy the user ID from the URL and share it with us in a reply to this comment. Make sure you just include the number in the reply.

    Example URL: https://community.sap.com/t5/user/viewprofilepage/user-id/53

    User ID: 53

    Please note that we are currently refactoring our profile and badge system on the SAP Community, and will start assigning badges again when that's complete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

contributionValuable Contributionfollow-up-with/devClarification with development needed.type/claritySomething was unclear in the documentation.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions