[Feature] [1.2.0] The new storage path is optimized when the engine material is updated

[CCweixiao]

Search before asking

• I had searched in the issues and found no similar feature requirement.

Problem Description

wds.linkis.bml.hdfs.prefix
wds.linkis.bml.local.prefix
如果用户有修改了这两个配置，那么引擎物料文件需要更新时，获取到的旧物料文件路径可能不可用导致引擎物料无法完成更新。
If the user has modified these two configurations, when the engine material file needs to be updated, the obtained old material file path may not be available and the engine material cannot be updated.

Description

原有VersionServiceImpl类中的updateVersion方法内，生成新路径的逻辑是：
In the updateVersion method in the original VersionServiceImpl class, the logic for generating a new path is:

// create resource new path
String newVersion = params.get("newVersion").toString();
String path = versionDao.getResourcePath(resourceId) + "_" + newVersion;

对于生成后的path，如果bml prefix有改动，需要重新成功一个path。
For the generated path, if the bml prefix is changed, a new path needs to be succeeded.

Use case

No response

solutions

No response

Anything else

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

[github-actions]

😊 Welcome to the Apache Linkis (incubating) community!!
We are glad that you are contributing by opening this issue.

Please make sure to include all the relevant context.
We will be here shortly.

If you are interested in contributing to our website project, please let us know!
You can check out our contributing guide on
👉 How to Participate in Project Contribution.

WeChat Group:

Mailing Lists:

name	description	Subscribe	Unsubscribe	archive
dev@linkis.apache.org	community activity information	subscribe	unsubscribe	archive