Hi everyone,

we are planing to put our aggregations result into an external data
base. To handle a connection failure to that external resource properly
we currently store the result onto the hdfs and sync it to the db after
that by a second pig script using the db's manufacturers pig data
storage. We do that because we hardly can effort to redo all the
aggregations in case of an error at the very end of the aggregation. 

If we could do something like to define a fallback data storage (e.g. to
the hdfs) that will be used in case of an connection issue we could drop
that entire second step an save a lot of effort. 
Is there anything like this?

Kind Regards 

Markus

Reply via email to