Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/332#issuecomment-39696780
One solution is to have these older messages for compatibility (with
deprecation) but then also expose the underlying log directly to users and
convert spark's code to use the new version. The `Logging` trait in Spark is
public so it's likely downstream applications are using it.
It's too bad though - the whole reason `Logging` exists is to provide an
indirection layer so we don't have to depend on specific implementations but
that's exactly what will cause performance overhead in this case.
---
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.
---
