Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/2433#issuecomment-63606245
@tdas if people are doing major dependency re-writes of Spark to replace
it's logging subsystem, IMO, they should be willing to tolerate a runtime error
if they try to call this. I've only seen this in the case of embedded Spark
applications where the user controls all the code anyways.
Holden what about enumerating the logging levels per @davies suggestion?
This seems like a good idea. Module that suggestion, this looks good to me.
---
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]
