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.

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

Needed strategy for large contents: Failed with "Response size too big. Maximum allowed response size: 7340032B" #709

Open
Swissbite opened this issue Jan 19, 2024 · 1 comment

Comments

@Swissbite
Copy link

While running against a larger and more complex dataset, checking out the source and debugging what the error really is /main/src/engine/utils/render-error-output.ts#L36-L37, I figured out that it has issues with larger datasets.

@Swissbite
Copy link
Author

Update: I think, the config / configuration is done wrong.

Axios seems to resolve the select parameter for the cdn the following way in a query parameter:

  • ?select%5B0%5D=sys.id&select%5B1%5D=sys.updatedAt&select%5B2%5D=sys.contentType.sys.id&limit=1000&skip=0

This have several flaws and issues:

  • Syntax from contentful documentation: ?select=sys.id,sys.updatedAt,sys.contentType.sys.id&limit=1000&skip=0.
  • Max level of select deepness: 2. The above query would return another 400, with the message Selected properties must be at most 2 levels deep, the path is deeper than two levels.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant