WweiL opened a new pull request, #42594:
URL: https://github.com/apache/spark/pull/42594

   <!--
   Thanks for sending a pull request!  Here are some tips for you:
     1. If this is your first time, please read our contributor guidelines: 
https://spark.apache.org/contributing.html
     2. Ensure you have added or run the appropriate tests for your PR: 
https://spark.apache.org/developer-tools.html
     3. If the PR is unfinished, add '[WIP]' in your PR title, e.g., 
'[WIP][SPARK-XXXX] Your PR title ...'.
     4. Be sure to keep the PR description updated to reflect all changes.
     5. Please write your PR title to summarize what this PR proposes.
     6. If possible, provide a concise example to reproduce the issue for a 
faster review.
     7. If you want to add a new configuration, please read the guideline first 
for naming configurations in
        
'core/src/main/scala/org/apache/spark/internal/config/ConfigEntry.scala'.
     8. If you want to add or modify an error type or message, please read the 
guideline first in
        'core/src/main/resources/error/README.md'.
   -->
   
   ### What changes were proposed in this pull request?
   <!--
   Please clarify what changes you are proposing. The purpose of this section 
is to outline the changes and how this PR fixes the issue. 
   If possible, please consider writing useful notes for better and faster 
reviews in your PR. See the examples below.
     1. If you refactor some codes with changing classes, showing the class 
hierarchy will help reviewers.
     2. If you fix some SQL features, you can provide some references of other 
DBMSes.
     3. If there is design documentation, please add the link.
     4. If there is a discussion in the mailing list, please add the link.
   -->
   Add a new error with detailed message when a user tries to access spark 
session and dataframe created using local spark session, in streaming spark 
connect `foreach`, `foreachBatch` and `StreamingQueryListener`.
   
   ### Why are the changes needed?
   <!--
   Please clarify why the changes are needed. For instance,
     1. If you propose a new API, clarify the use case for a new API.
     2. If you fix a bug, you can clarify why it is a bug.
   -->
   Better error logging for the breaking change introduced in streaming spark 
connect.
   
   ### Does this PR introduce _any_ user-facing change?
   <!--
   Note that it means *any* user-facing change including all aspects such as 
the documentation fix.
   If yes, please clarify the previous behavior and the change this PR proposes 
- provide the console output, description and/or an example to show the 
behavior difference if possible.
   If possible, please also clarify if this is a user-facing change compared to 
the released Spark versions or within the unreleased branches such as master.
   If no, write 'No'.
   -->
   Yes, before users can only see this non-informative error when they access a 
local spark session in their streaming connect related functions:
   ```
   Traceback (most recent call last):
     File "/home/wei.liu/oss-spark/python/pyspark/serializers.py", line 459, in 
dumps
       return cloudpickle.dumps(obj, pickle_protocol)
     File 
"/home/wei.liu/oss-spark/python/pyspark/cloudpickle/cloudpickle_fast.py", line 
73, in dumps
       cp.dump(obj)
     File 
"/home/wei.liu/oss-spark/python/pyspark/cloudpickle/cloudpickle_fast.py", line 
632, in dump
       return Pickler.dump(self, obj)
   TypeError: cannot pickle '_thread._local' object
   
   During handling of the above exception, another exception occurred:
   
   Traceback (most recent call last):
     File 
"/home/wei.liu/oss-spark/python/pyspark/sql/connect/streaming/readwriter.py", 
line 508, in foreachBatch
       self._write_proto.foreach_batch.python_function.command = 
CloudPickleSerializer().dumps(
     File "/home/wei.liu/oss-spark/python/pyspark/serializers.py", line 469, in 
dumps
       raise pickle.PicklingError(msg)
   _pickle.PicklingError: Could not serialize object: TypeError: cannot pickle 
'_thread._local' object
   ```
   
   Now it is replaced with:
   ```
   pyspark.errors.exceptions.base.PySparkRuntimeError: 
[STREAMING_CONNECT_SERIALIZATION_ERROR] Cannot serialize the function 
`foreachBatch`. If you accessed the spark session, or a dataframe defined 
outside of the function, please be aware that they are not allowed in Spark 
Connect. For foreachBatch, please access the spark session using 
`df.sparkSession`, where `df` is the first parameter in your foreachBatch 
function. For StreamingQueryListener, please access the spark session using 
`self.spark`
   ```
   
   ### How was this patch tested?
   <!--
   If tests were added, say they were added here. Please make sure to add some 
test cases that check the changes thoroughly including negative and positive 
cases if possible.
   If it was tested in a way different from regular unit tests, please clarify 
how you tested step by step, ideally copy and paste-able, so that other 
reviewers can test and check, and descendants can verify in the future.
   If tests were not added, please describe why they were not added and/or why 
it was difficult to add.
   If benchmark tests were added, please run the benchmarks in GitHub Actions 
for the consistent environment, and the instructions could accord to: 
https://spark.apache.org/developer-tools.html#github-workflow-benchmarks.
   -->
   Add unit tests
   
   ### Was this patch authored or co-authored using generative AI tooling?
   <!--
   If generative AI tooling has been used in the process of authoring this 
patch, please include the
   phrase: 'Generated-by: ' followed by the name of the tool and its version.
   If no, write 'No'.
   Please refer to the [ASF Generative Tooling 
Guidance](https://www.apache.org/legal/generative-tooling.html) for details.
   -->
   No


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to