Skip to content
This repository has been archived by the owner on Nov 29, 2017. It is now read-only.

Best error handling #29

Open
tyx opened this issue Feb 25, 2014 · 2 comments
Open

Best error handling #29

tyx opened this issue Feb 25, 2014 · 2 comments

Comments

@tyx
Copy link
Contributor

tyx commented Feb 25, 2014

When an ETL operation throws an exception, it should not interrupt all stuff but only the message concerned.

@tyx
Copy link
Contributor Author

tyx commented Feb 25, 2014

Attention !!!!

Dans les extractors si on attrape les exceptions, le count ne sera pas fait ! On rentre alors dans une boucle infini !

Il faut mettre un statut sur les message "terminated" qu'on ne propagera pas.

@tyx
Copy link
Contributor Author

tyx commented Jul 4, 2014

We should introduced 2 types of exception.

First one, as described in first msg to not interrupt process.
Second one, to interrupt the process with a kind message.

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

No branches or pull requests

1 participant