Hi all,
While checking out the module descriptors of `3.x` I have some
propositions of improvements to `log4j-jdbc` that I would like to run
by you before creating the appropriate Github issues:
1. The `log4j-jdbc` module depends on the optional presence of
`log4j-jndi`. Maybe we should split JND
Great questions and I will address each one, hopefully later today.
Gary
On Mon, Oct 16, 2023, 7:38 AM Piotr P. Karwasz
wrote:
> Hi all,
>
> While checking out the module descriptors of `3.x` I have some
> propositions of improvements to `log4j-jdbc` that I would like to run
> by you before cre
> On Oct 16, 2023, at 6:38 AM, Piotr P. Karwasz wrote:
>
> 2. There are two ways to map event data to columns: ColumnConfig and
> ColumnMapping. It is unclear to me which way is the recommended one.
> Since we can perform breaking changes in 3.x, could we remove one of
> these methods?
I added
Below...
On Mon, Oct 16, 2023 at 7:38 AM Piotr P. Karwasz
wrote:
>
> Hi all,
>
> While checking out the module descriptors of `3.x` I have some
> propositions of improvements to `log4j-jdbc` that I would like to run
> by you before creating the appropriate Github issues:
>
> 1. The `log4j-jdbc` m
Hi Gary,
On Mon, 16 Oct 2023 at 23:45, Gary Gregory wrote:
> > 4. The appender itself is quite wasteful in the number of connections
> > it uses (one per log message). IIRC JDBC connections are not
> > thread-safe, but can be used from multiple threads if synchronization
> > is provided. `Abstrac
