[ 
https://issues.apache.org/jira/browse/SPARK-33934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

angerszhu updated SPARK-33934:
------------------------------
    Description: 
In Hive script transform, we can use `USING xxx.py` but in Spark we will got 
error 
{code:java}
Job aborted due to stage failure: Task 17 in stage 530.0 failed 4 times, most 
recent failure: Lost task 17.3 in stage 530.0 (TID 38639, host, executor 339): 
org.apache.spark.SparkException: Subprocess exited with status 127. Error: 
/bin/bash: xxx.py: can't find the command
{code}

  was:
In Hive script transform, we can use `USING xxx/py` but in Spark we will got 
error 
{code:java}
Job aborted due to stage failure: Task 17 in stage 530.0 failed 4 times, most 
recent failure: Lost task 17.3 in stage 530.0 (TID 38639, host, executor 339): 
org.apache.spark.SparkException: Subprocess exited with status 127. Error: 
/bin/bash: xxx.py: can't find the command
{code}


> Support automatically identify the Python file and execute it
> -------------------------------------------------------------
>
>                 Key: SPARK-33934
>                 URL: https://issues.apache.org/jira/browse/SPARK-33934
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 3.2.0
>            Reporter: angerszhu
>            Priority: Major
>
> In Hive script transform, we can use `USING xxx.py` but in Spark we will got 
> error 
> {code:java}
> Job aborted due to stage failure: Task 17 in stage 530.0 failed 4 times, most 
> recent failure: Lost task 17.3 in stage 530.0 (TID 38639, host, executor 
> 339): org.apache.spark.SparkException: Subprocess exited with status 127. 
> Error: /bin/bash: xxx.py: can't find the command
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to