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

   <!--
   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
        'common/utils/src/main/resources/error/README.md'.
   -->
   
   ### What changes were proposed in this pull request?
   
   Before:
   ```
   2025-09-26 15:29:54: Failed to resolve flow: 
'spark_catalog.default.rental_bike_trips'.
   Error: [TABLE_OR_VIEW_NOT_FOUND] The table or view 
`spark_catalog`.`default`.`rental_bike_trips_raws` cannot be found. Verify the 
spelling and correctness of the schema and catalog.
   If you did not qualify the name with a schema, verify the current_schema() 
output, or qualify the name with the correct schema and catalog.
   To tolerate the error on drop use DROP VIEW IF EXISTS or DROP TABLE IF 
EXISTS. SQLSTATE: 42P01;
   'UnresolvedRelation [spark_catalog, default, rental_bike_trips_raws], [], 
true
   
   Traceback (most recent call last):
     File "/Users/sandy.ryza/oss/python/pyspark/pipelines/cli.py", line 358, in 
<module>
       run(
     File "/Users/sandy.ryza/oss/python/pyspark/pipelines/cli.py", line 285, in 
run
       handle_pipeline_events(result_iter)
     File 
"/Users/sandy.ryza/oss/python/pyspark/pipelines/spark_connect_pipeline.py", 
line 53, in handle_pipeline_events
       for result in iter:
     File "/Users/sandy.ryza/oss/python/pyspark/sql/connect/client/core.py", 
line 1169, in execute_command_as_iterator
       for response in self._execute_and_fetch_as_iterator(req, observations or 
{}):
     File "/Users/sandy.ryza/oss/python/pyspark/sql/connect/client/core.py", 
line 1559, in _execute_and_fetch_as_iterator
       self._handle_error(error)
     File "/Users/sandy.ryza/oss/python/pyspark/sql/connect/client/core.py", 
line 1833, in _handle_error
       self._handle_rpc_error(error)
     File "/Users/sandy.ryza/oss/python/pyspark/sql/connect/client/core.py", 
line 1904, in _handle_rpc_error
       raise convert_exception(
   pyspark.errors.exceptions.connect.AnalysisException:
   Failed to resolve flows in the pipeline.
   
   A flow can fail to resolve because the flow itself contains errors or 
because it reads
   from an upstream flow which failed to resolve.
   
   Flows with errors: spark_catalog.default.rental_bike_trips
   Flows that failed due to upstream errors:
   
   To view the exceptions that were raised while resolving these flows, look 
for flow
   failures that precede this log.
   
   JVM stacktrace:
   org.apache.spark.sql.pipelines.graph.UnresolvedPipelineException
        at 
org.apache.spark.sql.pipelines.graph.GraphValidations.validateSuccessfulFlowAnalysis(GraphValidations.scala:284)
        at 
org.apache.spark.sql.pipelines.graph.GraphValidations.validateSuccessfulFlowAnalysis$(GraphValidations.scala:247)
        at 
org.apache.spark.sql.pipelines.graph.DataflowGraph.validateSuccessfulFlowAnalysis(DataflowGraph.scala:33)
        at 
org.apache.spark.sql.pipelines.graph.DataflowGraph.$anonfun$validationFailure$1(DataflowGraph.scala:186)
        at scala.util.Try$.apply(Try.scala:217)
        at 
org.apache.spark.sql.pipelines.graph.DataflowGraph.validationFailure$lzycompute(DataflowGraph.scala:185)
        at 
org.apache.spark.sql.pipelines.graph.DataflowGraph.validationFailure(DataflowGraph.scala:185)
        at 
org.apache.spark.sql.pipelines.graph.DataflowGraph.validate(DataflowGraph.scala:173)
        at 
org.apache.spark.sql.pipelines.graph.PipelineExecution.resolveGraph(PipelineExecution.scala:109)
        at 
org.apache.spark.sql.pipelines.graph.PipelineExecution.startPipeline(PipelineExecution.scala:48)
        at 
org.apache.spark.sql.pipelines.graph.PipelineExecution.runPipeline(PipelineExecution.scala:63)
        at 
org.apache.spark.sql.connect.pipelines.PipelinesHandler$.startRun(PipelinesHandler.scala:294)
        at 
org.apache.spark.sql.connect.pipelines.PipelinesHandler$.handlePipelinesCommand(PipelinesHandler.scala:93)
        at 
org.apache.spark.sql.connect.planner.SparkConnectPlanner.handlePipelineCommand(SparkConnectPlanner.scala:2727)
        at 
org.apache.spark.sql.connect.planner.SparkConnectPlanner.process(SparkConnectPlanner.scala:2697)
        at 
org.apache.spark.sql.connect.execution.ExecuteThreadRunner.handleCommand(ExecuteThreadRunner.scala:322)
        at 
org.apache.spark.sql.connect.execution.ExecuteThreadRunner.$anonfun$executeInternal$1(ExecuteThreadRunner.scala:224)
        at 
org.apache.spark.sql.connect.execution.ExecuteThreadRunner.$anonfun$executeInternal$1$adapted(ExecuteThreadRunner.scala:196)
        at 
org.apache.spark.sql.connect.service.SessionHolder.$anonfun$withSession$2(SessionHolder.scala:349)
        at org.apache.spark.sql.SparkSession.withActive(SparkSession.scala:804)
        at 
org.apache.spark.sql.connect.service.SessionHolder.$anonfun$withSession$1(SessionHolder.scala:349)
        at 
org.apache.spark.JobArtifactSet$.withActiveJobArtifactState(JobArtifactSet.scala:94)
        at 
org.apache.spark.sql.artifact.ArtifactManager.$anonfun$withResources$1(ArtifactManager.scala:112)
        at org.apache.spark.util.Utils$.withContextClassLoader(Utils.scala:187)
        at 
org.apache.spark.sql.artifact.ArtifactManager.withClassLoaderIfNeeded(ArtifactManager.scala:102)
        at 
org.apache.spark.sql.artifact.ArtifactManager.withResources(ArtifactManager.scala:111)
        at 
org.apache.spark.sql.connect.service.SessionHolder.withSession(SessionHolder.scala:348)
        at 
org.apache.spark.sql.connect.execution.ExecuteThreadRunner.executeInternal(ExecuteThreadRunner.scala:196)
        at 
org.apache.spark.sql.connect.execution.ExecuteThreadRunner.org$apache$spark$sql$connect$execution$ExecuteThreadRunner$$execute(ExecuteThreadRunner.scala:125)
        at 
org.apache.spark.sql.connect.execution.ExecuteThreadRunner$ExecutionThread.run(ExecuteThreadRunner.scala:347)
   25/09/26 08:29:54 INFO ShutdownHookManager: Shutdown hook called
   ```
   
   After:
   
   ```
   2025-09-26 15:27:33: Failed to resolve flow: 
'spark_catalog.default.rental_bike_trips'.
   Error: [TABLE_OR_VIEW_NOT_FOUND] The table or view 
`spark_catalog`.`default`.`rental_bike_trips_raws` cannot be found. Verify the 
spelling and correctness of the schema and catalog.
   If you did not qualify the name with a schema, verify the current_schema() 
output, or qualify the name with the correct schema and catalog.
   To tolerate the error on drop use DROP VIEW IF EXISTS or DROP TABLE IF 
EXISTS. SQLSTATE: 42P01;
   'UnresolvedRelation [spark_catalog, default, rental_bike_trips_raws], [], 
true
   
   Traceback (most recent call last):
     File "/Users/sandy.ryza/oss/python/pyspark/pipelines/cli.py", line 360, in 
<module>
       run(
     File "/Users/sandy.ryza/oss/python/pyspark/pipelines/cli.py", line 287, in 
run
       handle_pipeline_events(result_iter)
     File 
"/Users/sandy.ryza/oss/python/pyspark/pipelines/spark_connect_pipeline.py", 
line 53, in handle_pipeline_events
       for result in iter:
     File "/Users/sandy.ryza/oss/python/pyspark/sql/connect/client/core.py", 
line 1169, in execute_command_as_iterator
       for response in self._execute_and_fetch_as_iterator(req, observations or 
{}):
     File "/Users/sandy.ryza/oss/python/pyspark/sql/connect/client/core.py", 
line 1559, in _execute_and_fetch_as_iterator
       self._handle_error(error)
     File "/Users/sandy.ryza/oss/python/pyspark/sql/connect/client/core.py", 
line 1833, in _handle_error
       self._handle_rpc_error(error)
     File "/Users/sandy.ryza/oss/python/pyspark/sql/connect/client/core.py", 
line 1904, in _handle_rpc_error
       raise convert_exception(
   pyspark.errors.exceptions.connect.AnalysisException:
   Failed to resolve flows in the pipeline.
   
   A flow can fail to resolve because the flow itself contains errors or 
because it reads
   from an upstream flow which failed to resolve.
   
   Flows with errors: spark_catalog.default.rental_bike_trips
   Flows that failed due to upstream errors:
   
   To view the exceptions that were raised while resolving these flows, look 
for flow
   failures that precede this log.
   25/09/26 08:27:34 INFO ShutdownHookManager: Shutdown hook called
   25/09/26 08:27:34 INFO ShutdownHookManager: Deleting directory 
/private/var/folders/1v/dqhbgmt10vl6v3tdlwvvx90r0000gp/T/localPyFiles-039afc43-9f5c-4a6f-ac7b-2437496ac7de
   25/09/26 08:27:34 INFO ShutdownHookManager: Deleting directory 
/private/var/folders/1v/dqhbgmt10vl6v3tdlwvvx90r0000gp/T/spark-c67d94d5-4110-4268-af67-430b3ae82133
   ```
   
   ### 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.
   -->
   
   
   ### Does this PR introduce _any_ user-facing change?
   <!--
   Note that it means *any* user-facing change including all aspects such as 
new features, bug fixes, or other behavior changes. Documentation-only updates 
are not considered user-facing changes.
   
   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'.
   -->
   
   
   ### 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.
   -->
   
   
   ### 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.
   -->
   


-- 
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