Github user dongjoon-hyun commented on the issue:

    https://github.com/apache/spark/pull/16579
  
    The root cause is not inside a newly added code.
    ```
    org.apache.spark.sql.SQLQuerySuite.SET -v test      43 ms   1
    org.apache.spark.sql.SQLQuerySuite.`SET -v` commands should return a list 
sorted by key
    ```
    
    The current `set -v` implementation seems to have issue according to the 
error message. I'll make another PR to clarify that.
    ```
    org.apache.spark.SparkException: Job aborted due to stage failure: Task 0 
in stage 480.0 failed 1 times, most recent failure: Lost task 0.0 in stage 
480.0 (TID 1470, localhost, executor driver): java.lang.NullPointerException  
at 
org.apache.spark.sql.catalyst.expressions.GeneratedClass$GeneratedIterator.processNext(Unknown
 Source)  at 
org.apache.spark.sql.execution.BufferedRowIterator.hasNext(BufferedRowIterator.java:43)
  at 
org.apache.spark.sql.execution.WholeStageCodegenExec$$anonfun$8$$anon$1.hasNext(WholeStageCodegenExec.scala:377)
  at 
org.apache.spark.sql.execution.SparkPlan$$anonfun$2.apply(SparkPlan.scala:231)  
at 
org.apache.spark.sql.execution.SparkPlan$$anonfun$2.apply(SparkPlan.scala:225)  
at 
org.apache.spark.rdd.RDD$$anonfun$mapPartitionsInternal$1$$anonfun$apply$25.apply(RDD.scala:826)
  at 
org.apache.spark.rdd.RDD$$anonfun$mapPartitionsInternal$1$$anonfun$apply$25.apply(RDD.scala:826)
  at org.apache.spark.rdd.MapPartitionsRDD.compute(MapPartitionsRDD.scala:38)  
at org
 .apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:323)  at 
org.apache.spark.rdd.RDD.iterator(RDD.scala:287)  at 
org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:88)  at 
org.apache.spark.scheduler.Task.run(Task.scala:114)  at 
org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:313)  at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
 at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
 at java.lang.Thread.run(Thread.java:745)  Driver stacktrace:
    ```


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

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

Reply via email to