[
https://issues.apache.org/jira/browse/SPARK-50427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hyukjin Kwon resolved SPARK-50427.
----------------------------------
Fix Version/s: 4.0.0
Resolution: Fixed
Issue resolved by pull request 48802
[https://github.com/apache/spark/pull/48802]
> [CONNECT][PYTHON] Provide the ability to reconfigure the connect logger
> -----------------------------------------------------------------------
>
> Key: SPARK-50427
> URL: https://issues.apache.org/jira/browse/SPARK-50427
> Project: Spark
> Issue Type: Improvement
> Components: Connect, PySpark
> Affects Versions: 4.0.0
> Reporter: Niranjan Jayakar
> Assignee: Niranjan Jayakar
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
>
> We currently offer the mechanism to configure the connect-specific logger
> based on the environment variable SPARK_CONNECT_LOG_LEVEL.
> The logger is configured once at the the time of "module load". In some
> specific cases, some Python frameworks (eg. IPythonKernel) can modify the
> Python log level after the fact.
> There is no good way to restore the logger to restore its previous
> functionality to honour the environment variable configured.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
