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

[FEAT] Add recommendations when a 413 error is returned #177

Open
AzulGarza opened this issue Nov 15, 2023 · 2 comments
Open

[FEAT] Add recommendations when a 413 error is returned #177

AzulGarza opened this issue Nov 15, 2023 · 2 comments
Assignees
@marcopeix
Labels
feature

Comments

@AzulGarza
Copy link
Member

AzulGarza commented Nov 15, 2023 •
edited
Loading

Related to size of data. It should suggest using num_partitions. See #176.
@elephaint
Copy link
Contributor

@marcopeix @AzulGarza #418 is the same?

@AzulGarza
Copy link
Member Author

hey @elephaint! yes, it is the same. an interesting fix would be to chatch the error inside the sdk, and give the recommendation. adding @jmoralez to the loop to see if we can include something similar in v2 (that version will have less problems with data size, but maybe we can think about it.)

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

@marcopeix marcopeix

Labels
feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@AzulGarza @marcopeix @elephaint