[Bug] [Setting Center] dinky was down when set Resource mode to oss

[bulolo]

Search before asking

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

What happened

What you expected to happen

will not down when set to oss

How to reproduce

only to change it on web

Anything else

No response

Version

1.2.0

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

Hello @bulolo, this issue is about web, so I assign it to @Zzm0809. If you have any questions, you can comment and reply.

你好 @bulolo, 这个 issue 是关于 web 的，所以我把它分配给了 @Zzm0809。如有任何问题，可以评论回复。

[aiwenmo]

Please have a try in Dinky1.2.1

[bulolo]

Please have a try in Dinky1.2.1

i am using 1.2.1,sorry i close it ,how to reopen it

[bulolo]

当在不知情的时候按了oss，会导致整个部署的dinky直接挂彩，并且启动不起来，我认为需要一个保护措施

[aiwenmo]

I agree with you.

[bulolo]

I agree with you.

otherwise, the name "oss" should change to "s3" better

[jiangwwwei]

这个问题是由于你开启了HistoryServer，它会加载Resource的配置。当Resource中的配置不正确时，HistoryServer抛oss相关的异常会把dinky也停止。
此外，oss依赖的是aws的sdk，Historyserver依赖的是 flink-s3-presto ,这两个对路径前的"/"处理是不一样的。可以看我提的这个问题#4088

可以考虑暂时关闭HistoryServer，等以后版本修复这个问题

This issue occurs because you have enabled the HistoryServer, which loads the configuration of the Resource. When the configuration in the Resource is incorrect, the HistoryServer throws an exception related to OSS, which also stops Dinky. Additionally, OSS depends on the AWS SDK, while HistoryServer depends on flink-s3-presto, and these two handle the leading "/" in the path differently.
You can refer to the issue I raised #4088 for more details. As a temporary solution, you can consider disabling the HistoryServer until this issue is fixed in a future version.