Skip to content

exception / error handling in the data flow #109

Description

@KrishnaPG

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) ??

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions