FYI, I have been using Log4j 2 in my Flume deployments for over a year, despite whatever Flume or its dependencies are using for an API. Having Flume come preconfigured for Log4j 2 would be nice. It will take some work to convert the code to use the Log4j 2 API. At a minimum all the log4j imports have to be modified. You only have to modify the actual logging statements if you want to take advantage of the API improvements.
Ralph > On Oct 20, 2016, at 1:44 AM, Attila Simon <s...@cloudera.com> wrote: > > Hi Lior, > > Could you please explain a bit what will break? > > Cheers, > Attila > > On Tuesday, 18 October 2016, Lior Zeno <liorz...@gmail.com> 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: s...@cloudera.com > > [image: Cloudera Inc.]
