When error is thrown from sink the event type logged out does not match error causing event type

[cross311]

Have a cookie cutter service that is using protobuf off of Kafka. I only have handlers for X and Y. The Kafka topic has type X, Y and Z.

I was getting an error because the params were not matching up with the store procedure (it actually did not exist, another bug #110 ). When it logged out the error it listed type Z was the issue... I have zero handlers for Z and def did not do a publish with type Z. it was actually on type Y that caused the issue... seems like it was just the lats in the batch of messages coming in or something.

[sklose]

this is actually a general issue for all sinks that can handle batches - the error message always contains the last msg from the batch ... i'll update the ticket title to reflect that.