rdifrango

Replaced by #220

@JonasKunz now that #220 is merged we should go ahead and close this one as it supersedes it.

The note on those converters as it only goes from log4j.properties to log4j.xml and not logback.xml . Now logback does have an online converter which can be found here: https://logback.qos.ch/translator/...

+1

Here's how I integrated it into Flask, it's simply adding the handler to `app.logger` which Flask exposes: ``` # Add an ECS formatter to the Handler handler = logging.StreamHandler() handler.setFormatter(ecs_logging.StdlibFormatter())...

Thanks @cowtowncoder. It's interesting that we've been successfully using AVRO 1.11.2 so it must be some edge cases that we aren't currently hitting.

> 2.18.0-rc1 now released: @rdifrango not sure if it's easy to do, but it'd be great to see if upgrade would work with 2.18, for eventual 2.18.0 release I just...

> @rdifrango rats. Ok. That may also explain why upgrade was to `1.11.3` not `1.12.0`. Quite possibly...and I'll grant that the move to `1.12.0` is not backwards compatible.

> It seems odd for Avro library to nominally follow SemVer but... seemingly not? (although as a library maintainer I understand how difficult backwards-compatibility is). > > But would be...

> @rdifrango I guess damage is done, API compatibility broken b/w versions. So not sure how much value there would be. (not sure how `commons-validator` is related -- is that...