[FLUME-411] Events sent down each branch of a FanOut sink should be independent

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.9.3
• Assignee: Jonathan Hsieh
• Reporter: Jonathan Hsieh
• Created: 19/Dec/10 02:19
• Updated: 20/Dec/10 22:50
• Resolved: 20/Dec/10 22:50

Description

Currently, if an event is sent down two paths that annotate the event, because the same instance of the event is used, there may be an unexpected attribute overwrite exception.

Examples:

[

{value("foo","bar") => console} , {value("baz", "blah") => console} ]

This would output something like:

event {foo:bar}
event {foo:bar, baz:blah}

Notice that the foo attribute is on the second event!

For this example
[ {value("foo","bar") => console}

,

{value("foo", "failure") => console}

]

The first would succeed but the second branch would fail because foo is being overwritten!

Issue Links

• relates to: FLUME-265 FanOut Collector does not support multiple collectorSink attributes