It's been about 6 weeks since I started the discussion, with no questions.
I'm going to start a vote.
Thanks, and best regards!
Randall
On Thu, Mar 18, 2021 at 8:24 AM Dongjin Lee wrote:
> Great! If this KIP is merged first, I will update the PR accordingly.
>
> Thanks,
> Dongjin
>
> On Thu, M
Great! If this KIP is merged first, I will update the PR accordingly.
Thanks,
Dongjin
On Thu, Mar 18, 2021, 10:04 PM Randall Hauch wrote:
> Thanks, Dongjin.
>
> We still have some time before this KIP might be approved, so I don’t want
> to block any work on KIP-653. It’s fine for the KIP-653 P
Thanks, Dongjin.
We still have some time before this KIP might be approved, so I don’t want
to block any work on KIP-653. It’s fine for the KIP-653 PR to be merged
first. I’ll just have to update my PR when this KIP passes.
On Thu, Mar 18, 2021 at 1:30 AM Dongjin Lee wrote:
> Hi Randall,
>
> I
Hi Randall,
I am +1 for this proposal. Sure, changing this setting manually is so
annoying. I think this proposal should be applied as soon as possible.
However, I have a question: as you already know, the upgrade to Log4j2[^1]
was already passed but not merged yet. Which one would be the right w
Hello all,
I'd like to propose KIP-721 to change Connect's Log4J configuration that we
ship with AK. This KIP will enable by default Connect's valuable connector
log contexts, which was added as part of KIP-449 to include connector- and
task-specific information to every log message output by the
