xieyi888 opened a new issue, #4090:
URL: https://github.com/apache/incubator-streampark/issues/4090

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/incubator-streampark/issues?q=is%3Aissue+label%3A%22bug%22)
 and found no similar issues.
   
   
   ### Java Version
   
   1.8
   
   ### Scala Version
   
   2.11.x
   
   ### StreamPark Version
   
   dev
   
   ### Flink Version
   
   1.16.2
   
   ### deploy mode
   
   yarn-application
   
   ### What happened
   
   1. create resource and upload jar
   jar name: verify-sloth-1.0-SNAPSHOT.jar
   
![image](https://github.com/user-attachments/assets/d2246587-e22b-4118-a954-760d76474a6a)
   
   
   2. create job depend on the resource
   
![image](https://github.com/user-attachments/assets/5cc75bd8-ba06-4873-ae6e-895bc9dc4fd3)
   
   
   
   3. update the job,and upload jar during  update job
   the upload jar's name is verify-sloth-2.4-SNAPSHOT.jar.  which is different 
from the jar from resource
   
![image](https://github.com/user-attachments/assets/0f45afd7-a95f-44f9-82e5-aa14e33c6044)
   
   the job resource is in temp dir, and not upload to 
Workspace.local().APP_UPLOADS()
   ```
   [root@*** /]# ll /disk1/eadop/streampark/temp/verify-sloth-2.4-SNAPSHOT.jar
   -rw------- 1 ****  **** 16029391 Sep 14 17:54 
/disk1/eadop/streampark/temp/verify-sloth-2.4-SNAPSHOT.jar
   ```
   
   
   
   4. release job fail
   
![image](https://github.com/user-attachments/assets/18553ad7-fb71-4e5e-a26a-01d2ae75b4c0)
   
   
   
   
   
   ### Error Exception
   
   _No response_
   
   ### Screenshots
   
   
![image](https://github.com/user-attachments/assets/471e59b0-9dcc-49b2-b5a8-5b30228d5b15)
   
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!(您是否要贡献这个PR?)
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


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

Reply via email to