No, please don't add a `log4j-cassandra4` module. We haven't seen a single sign that it is actually being used, putting aside whether the size of that user base justifies an official Log4j module or not. If it would be up to me, I would even drop the Cassandra support in `main`. I suppose moving Cassandra support to a separate module and letting it rot there is the only solution all PMC members agree on.
On Mon, Jul 17, 2023 at 4:59 PM Piotr P. Karwasz <piotr.karw...@gmail.com> wrote: > Hi all, > > As Dependabot often reminds us[1], Cassandra has a new 4.x major > version and version 3.x will reach end-of-life at the end of the > year[2]. > The appender is either perfect or rarely used: the last SO question > about it is 2 years old[3] and the last issue from last year[4]. > > Should we create a `log4j-cassandra4` module for the next 2.x release? > Personally I would wait until we create an `l-l-cassandra` repo and > migrate the appender there, but I can probably update the code to work > with version 4.x. > > Piotr > > [1] https://github.com/apache/logging-log4j2/pull/1540 > [2] > https://cassandra.apache.org/_/blog/Apache-Cassandra-3.0.x-and-3.11.x-End-of-Life-Announcement.html > [3] > https://stackoverflow.com/search?tab=newest&q=(%5blog4j%5d%20or%20%5blog4j2%5d)%20and%20cassandra&searchOn=3 > [4] https://issues.apache.org/jira/browse/LOG4J2-3553 >
