det101 commented on issue #17244: URL: https://github.com/apache/dolphinscheduler/issues/17244#issuecomment-2968933766
> > If there is a situation where a higher-version dependency cannot support a lower-version cloud service, then users can only choose to run on JDK8/11. > > This needs to be discussed. [@zhongjiajie](https://github.com/zhongjiajie) [@ruanwenjun](https://github.com/ruanwenjun) [@Gallardot](https://github.com/Gallardot) [@caishunfeng](https://github.com/caishunfeng) > > > There should be no problem submitting through the command line (such as hive -e, spark-sql, hdfs commands). > > Yes. Command line operation will not be affected. What I mean is many dependencies in `pom.xml` don't support jdk17. If you upgrade, you need to change the code. How to ensure the compatibility after upgrading? We need full design detail of all dependencies that need to be upgraded. I learned about DataWorks, and it doesn't have the concept of projects. Its namespace is the workflow. In addition, its project space is physically isolated, which is reasonable on the public cloud. Can we balance the benefits and complexity of introducing namespaces on the project? And it is impossible to achieve physical isolation. There should be no public cloud model for using DS (of course, we have also modified the DS cloud, and the worker is opened on the user vpc, but there is no problem with the workspace for the time being). 我学习了下dataworks，他没有项目的概念，他的命名空间下面就是工作流。另外他的项目空间是做物理隔离的，这在公有云上是合理的； 我们在项目上面再引入命名空间能带来的收益和复杂度是否能平衡，而且也无法实现物理隔离，使用DS应该还没有公有云的模式（当然我们也把DS云上做了改造，worker在用户vpc上开，但还没有引工作空间暂时也没有问题） -- 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]
