[
https://issues.apache.org/jira/browse/SPARK-48291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gengliang Wang resolved SPARK-48291.
------------------------------------
Fix Version/s: 4.0.0
Resolution: Fixed
Issue resolved by pull request 46600
[https://github.com/apache/spark/pull/46600]
> Rename Java Logger as SparkLogger
> ----------------------------------
>
> Key: SPARK-48291
> URL: https://issues.apache.org/jira/browse/SPARK-48291
> Project: Spark
> Issue Type: Sub-task
> Components: Spark Core
> Affects Versions: 4.0.0
> Reporter: Gengliang Wang
> Assignee: Gengliang Wang
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
>
> Two new classes org.apache.spark.internal.Logger and
> org.apache.spark.internal.LoggerFactory were introduced from
> [https://github.com/apache/spark/pull/46301|https://github.com/apache/spark/pull/46301,]
> Given that {{Logger}} is a widely recognized interface in Log4j, it may lead
> to confusion to have a class with the same name. To avoid this and clarify
> its purpose within the Spark framework, I propose renaming
> {{org.apache.spark.internal.Logger}} to
> {{{}org.apache.spark.internal.SparkLogger{}}}. Similarly, to maintain
> consistency, {{org.apache.spark.internal.LoggerFactory}} should be renamed to
> {{{}org.apache.spark.internal.SparkLoggerFactory{}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
