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
>&
> >>>>>
> >>>>> [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,
/2.x/manual/migration.html.
>>>>>
>>>>> On Thu, Oct 20, 2016 at 11:44 AM, Attila Simon <s...@cloudera.com> wrote:
>>>>>
>>>>>> Hi Lior,
>>>>>>
>>>>>> Could you please ex
t;>
>>>>> Hi Lior,
>>>>>
>>>>> Could you please explain a bit what will break?
>>>>>
>>>>> Cheers,
>>>>> Attila
>>>>>
>>>>> On Tuesday, 18 Oc
plain a bit what will break?
>>>>
>>>> Cheers,
>>>> Attila
>>>>
>>>> On Tuesday, 18 October 2016, Lior Zeno <liorz...@gmail.com> wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>>
lt;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:
>>&g
t;
>>>> 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 supporte
t; 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
nounces)
> > 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 F
oject_
> 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.
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
11 matches
Mail list logo