Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/4998#issuecomment-80947530
Yeah that's what I am hoping might work, to remove log4j 1.2 and replace
with log4j 2 + 1.2-to-2 bridge, and also use the slfj4-to-log4j2 bridge, and
update Spark itself to use log4j 2. The idea is that apps that expect to find
log4j 1.2 still find its API.
It's still somewhat problematic if user logging config stops working. Is it
not backwards-compatible / accepts the old format too? I am also worried this
somehow interacts badly with classloaders, but it stands a chance of working.
But if it works well I mean that the main build would do this, not a
profile.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
