Uploaded image for project: 'Flume'
  1. Flume
  2. FLUME-411

Events sent down each branch of a FanOut sink should be independent

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: v0.9.3
    • Component/s: None
    • Labels:
      None

      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

          Activity

          Hide
          jmhsieh Jonathan Hsieh added a comment -

          I think this is the root cause for FLUME-265.

          Show
          jmhsieh Jonathan Hsieh added a comment - I think this is the root cause for FLUME-265 .
          Hide
          jmhsieh Jonathan Hsieh added a comment -
          Show
          jmhsieh Jonathan Hsieh added a comment - review : https://review.cloudera.org/r/1316/
          Hide
          jmhsieh Jonathan Hsieh added a comment -

          committed

          Show
          jmhsieh Jonathan Hsieh added a comment - committed

            People

            • Assignee:
              jmhsieh Jonathan Hsieh
              Reporter:
              jmhsieh Jonathan Hsieh
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development