Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[DI] Drop snapshot if JSON payload is too large #4818

Merged
merged 3 commits into from
Oct 30, 2024
Merged

[DI] Drop snapshot if JSON payload is too large #4818

merged 3 commits into from
Oct 30, 2024
+115 −6

Commits on Oct 29, 2024

  1. [DI] Drop snapshot if JSON payload is too large 

    The log track has a 1MB limit of the JSON payload. The client is not
notified if the payload is too large, but it is simply never indexed.

This is a very crude approach. In the future a more sophsticated
algorithm will be implemented that reduces the size of the snapshot
instead of removing it completely.
    @watson
    watson committed Oct 29, 2024
    Configuration menu
    Copy the full SHA
    3bd65c3 View commit details
    Browse the repository at this point in the history

  2. Address review comments

    @watson
    watson committed Oct 29, 2024
    Configuration menu
    Copy the full SHA
    1d824e5 View commit details
    Browse the repository at this point in the history

  3. Code cleanup

    @watson
    watson committed Oct 29, 2024
    Configuration menu
    Copy the full SHA
    3ef1ead View commit details
    Browse the repository at this point in the history