I second that, murphy law ... New releases or patch can break the correct event format, manual mistakes too and so on
> Le 16 oct. 2014 à 17:54, Paul Chavez <[email protected]> a écrit : > > Human error is most common reason in my experience. Whether it is a > configuration error or fault in app development, I was just relaying a method > to make your flume infrastructure more resilient. Regarding corrupted events, > now that I think of it those have always been within the event payload and we > have never actually seen corrupted headers. > >> On Oct 16, 2014, at 8:24 AM, "Jean-Philippe Caruana" <[email protected]> >> wrote: >> >> Le 15/10/2014 17:57, Paul Chavez a écrit : >>> Yes, that will work fine. From experience, I can say definitely account for >>> the possibility of the 'tenant' and 'data_type' headers being corrupted or >>> missing outright. >> >> How come they are missing or corrupted ? >> If my app is the only source for these events, I suppose we will code it >> without missing headers >> >> Can you elaborate ? >> >> Thanks >> >> -- >> Jean-Philippe Caruana >> http://www.barreverte.fr >>
