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

Set explicit input and output limits #183

Open
erwinvaneyk opened this issue Aug 6, 2018 · 1 comment
Open

Set explicit input and output limits #183

erwinvaneyk opened this issue Aug 6, 2018 · 1 comment

Comments

@erwinvaneyk
Copy link
Member

Currently Workflows does not have explicit input and output size limits (for Fission funtions). However, implicitly there are (for example: NATS has a 10 MB message limit), which causes unanticipated behavior---as the user is not aware of these limits.

To fix this, Workflows should have explicit message limits, and return an error immediately when the inputs or outputs exceed the limit.

cc @thenamly

@ghost
Copy link

ghost commented Aug 8, 2018

  • Default limit of NATS is 1 MB
  • Google pub/sub: 10 MB
  • Azure: 1 MB
  • ...

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

No branches or pull requests

1 participant