You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@livy.apache.org by "Praneet Sharma (Jira)" <ji...@apache.org> on 2022/05/02 22:17:00 UTC

[jira] [Updated] (LIVY-888) AddJar or AddFile call on a duplicate file should not result in failure for Livy session

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

Praneet Sharma updated LIVY-888:
--------------------------------
    Description: Currently, when addFile or addJar is used to upload a file or a jar which was already uploaded, it results in IOException. On the other hand, the spark-submit behavior is to ignore adding duplicate jars/files and logging appropriate warning message. The same should be done for addFile and addJar APIs in Livy.  (was: Currently, when addFile or addJar is used to upload a file or a jar which was already uploaded, it should +not+ result in IOException. This is because the spark-submit behavior is to ignore adding duplicate jars/files and logging appropriate warning message. The same should be done for addFile and addJar APIs in Livy.)

> AddJar or AddFile call on a duplicate file should not result in failure for Livy session
> ----------------------------------------------------------------------------------------
>
>                 Key: LIVY-888
>                 URL: https://issues.apache.org/jira/browse/LIVY-888
>             Project: Livy
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 0.7.0
>            Reporter: Praneet Sharma
>            Priority: Major
>
> Currently, when addFile or addJar is used to upload a file or a jar which was already uploaded, it results in IOException. On the other hand, the spark-submit behavior is to ignore adding duplicate jars/files and logging appropriate warning message. The same should be done for addFile and addJar APIs in Livy.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)