Sure. First, the Log4jAppender will be deprecated. Log4j2 already provides a Flume appender [1]. Second, since we use almost exclusively the SLF4j API in Flume, the code will only slightly change. The major difference is with the configuration files which have changed from 1.x to 2.x [2].
[1] https://logging.apache.org/log4j/2.x/manual/appenders.html#FlumeAppender [2] https://logging.apache.org/log4j/2.x/manual/migration.html. On Thu, Oct 20, 2016 at 11:44 AM, Attila Simon <[email protected]> wrote: > Hi Lior, > > Could you please explain a bit what will break? > > Cheers, > Attila > > On Tuesday, 18 October 2016, Lior Zeno <[email protected]> wrote: > > > Hi All, > > > > Log4j (v1) has been EOL'ed over a year now ( > > https://blogs.apache.org/foundation/entry/apache_ > logging_services_project_ > > announces) > > and is no longer officially supported. > > > > I propose we migrate to Log4j 2. We can begin with using the Log4j 1.x > > bridge, and then incrementally move the whole codebase. > > > > Since this is a breaking change, I think we should schedule this to Flume > > 2.0.0. > > > > Thoughts? > > > > Thanks > > > > > -- > > *Attila Simon* > Software Engineer > Email: [email protected] > > [image: Cloudera Inc.] >
