zhongjiajie commented on issue #8862: URL: https://github.com/apache/dolphinscheduler/issues/8862#issuecomment-1074861077
> In the process of modification, I found that 'projectMapper.queryByName(projectName)' was used in 'dolphinscheduler-python/src/main/java/org/apache/dolphinscheduler/server/PythonGatewayServer.java', and I learned the concept of work flow user through 'pydolphinscheduler/src/pydolphinscheduler/core/default_config.yaml'. It was then discovered that user 1's project could be authorized to user 2. > > If user 1 has an ETL project, and user 2 has an ETL project, and grants user 1's ETL project to user 2, then user 2's project list will have two ETL projects, one from user 1 and one from user 2. The problem is that the PyDolphinScheduler module queries projectCode by projectName and it may not be clear to the PydolphinScheduler user which user the project is from. It may be neither default.user.name nor default.workflow.user in 'pydolphinscheduler/src/pydolphinscheduler/core/default_config.yaml'. So it makes sense that the projectName global is unique in the PyDolphinScheduler module. Hi @Hou-Shuaishuai, It should not be a problem for pydolphinscheduler, At least we could grant projects to a specific user in web UI. For now pydolphinscheduler will raise error when one user have more than one project with same name. But if our web UI find out how to handle this situation, pydolphinscheduler could also do it. -- 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]
