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

docs: update incorrect batch size reference #919

Conversation

RahulLanjewar93
Copy link
Contributor

In current parse-server, I dont think there is a cap for how many objects can be updated/saved/destroyed in one go.
So maybe we should update this in docs.

Copy link
Member

@mtrezza mtrezza left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • What is the current batch size limit?
  • Is this the only place where this limit is mentioned in the docs?

@RahulLanjewar93
Copy link
Contributor Author

@RahulLanjewar93
Copy link
Contributor Author

RahulLanjewar93 commented Feb 2, 2023

Also, there is this PR on how to use transactions on client sdks while using the batch endpoint.
It's not merged yet and somewhere they did mention removing the batch size and putting everything in a single batch because it's causing issues.

@mtrezza
Copy link
Member

mtrezza commented Feb 3, 2023

If the current batch size is 20, not 50, should that be mentioned in the docs instead of removing the note altogether?

@RahulLanjewar93
Copy link
Contributor Author

@mtrezza the batch size is customizable in the JS SDK. The default is set to 20.

_includes/rest/objects.md Outdated Show resolved Hide resolved
Copy link
Member

@mtrezza mtrezza left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@mtrezza mtrezza changed the title docs: removed maximum 50 objects cap from batch endpoint docs: update incorrect batch size reference Feb 4, 2023
@mtrezza mtrezza merged commit 9b1660c into parse-community:gh-pages Feb 4, 2023
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

Successfully merging this pull request may close these issues.

2 participants