[jira] [Resolved] (FLUME-112) Think of ways to reuse transformation logic in source/sink/decorator as a Map or Reduce task in Hadoop MapReduce

["Alexander Lorenz-Alten (Resolved) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLUME-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Lorenz-Alten resolved FLUME-112.
------------------------------------------

    Resolution: Won't Fix

deprecated, flumeNG (1.0x)
                
> Think of ways to reuse transformation logic in source/sink/decorator as a Map or Reduce task in Hadoop MapReduce
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: FLUME-112
>                 URL: https://issues.apache.org/jira/browse/FLUME-112
>             Project: Flume
>          Issue Type: New Feature
>          Components: Sinks+Sources
>    Affects Versions: v0.9.4
>            Reporter: Disabled imported user
>
> It has come up on the mailing list that while Flume is great for formatting new data that's coming into HDFS, a lot of time there is old data sitting around that you'd like to make magically match the format that the new data is getting written in. It's not a pressing feature, but opening a ticket now to see if we can come up with some clever ways to bundle up Flume logic and reuse it in a Map or Reduce task.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira