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

exception / error handling in the data flow #109

Open
KrishnaPG opened this issue Apr 12, 2016 · 0 comments
Open

exception / error handling in the data flow #109

KrishnaPG opened this issue Apr 12, 2016 · 0 comments

Comments

@KrishnaPG
Copy link

Not sure if this is the right repo or should be posted elsewhere, but we have this below question:

How to deal with errors that could arise out of any one component in the flow pipeline?

For example, say read elastic

  • we would like to handle the errors in a peaceful manner (instead of breaking / halting the whole pipeline). For example, can we catch 'server not found / dns errors / network errors etc' and log them into a file with timestamp (and follow the regular code flow in case no error happens) ??
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