Github user tsliwowicz commented on the pull request:
https://github.com/apache/spark/pull/4998#issuecomment-78868836
@srowen this is in essence the same as the ability to control hadoop
version only through classpath manipulation. Since there are many flavors, its
being done by using different profiles. While Spark may choose to leave the
default log4j support for 1.2, the only way to fully switch to log4j 2 is via
changing the classpath. Using the same logic that was applied by the spark
designer for hadoop, @liorchaga created the profile for log4j 2. Adding a build
profile does not complicate things because the default (that is not specifying
the profile) means the build stays the same. Only those who need it, will use
the profile. Same as for various hadoop versions.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
