Provided config to have camus fail if it sees any errors

Move it to logger would be better.  Camus used to have the problem the log4j messages are not logged when running inside Azkaban, we fixed that problem and haven't cleaned up the code to replace System.out (or System.err) with log4j logging.

________________________________
From: Bryan Baugher [notifications@github.com]
Sent: Tuesday, September 02, 2014 9:48 AM
To: linkedin/camus
Subject: Re: [camus] Provided config to have camus fail if it sees any errors (#109)


In camus-etl-kafka/src/main/java/com/linkedin/camus/etl/kafka/CamusJob.java:

> @@ -332,8 +333,13 @@ public int compare(FileStatus f1, FileStatus f2) {
>               // Send Tracking counts to Kafka
>               sendTrackingCounts(job, fs, newExecutionOutput);
>
> -             // Print any potentail errors encountered
> -             printErrors(fs, newExecutionOutput);
> +        Map<EtlKey, ExceptionWritable> errors = readErrors(fs, newExecutionOutput);
> +
> +             // Print any potential errors encountered
> +        for(Entry<EtlKey, ExceptionWritable> entry : errors.entrySet()) {
> +            System.err.println(entry.getKey().toString());


This is how Camus behaves currently. Although I would agree moving this to logger would probably be better

—
Reply to this email directly or view it on GitHub<https://github.com/linkedin/camus/pull/109/files#r16999354>.