-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug][DataSource] delete the password and test again, it is successful without password #9428
Closed
3 tasks done
Comments
Thank you for your feedback, we have received your issue, Please wait patiently for a reply.
|
The image upload failed, please try again. |
wqxs
added a commit
to wqxs/dolphinscheduler
that referenced
this issue
Apr 16, 2022
…cessful without password bug (apache#9428) * fix bug: After the test data source is successful, delete the password, re-test, or success * Modify the method of generating DatasourceUniqueId
wqxs
added a commit
to wqxs/dolphinscheduler
that referenced
this issue
Apr 16, 2022
…cessful without password bug (apache#9428) * fix bug: After the test data source is successful, delete the password, re-test, or success * Modify the method of generating DatasourceUniqueId
Tianqi-Dotes
pushed a commit
to Tianqi-Dotes/dolphinscheduler
that referenced
this issue
Jun 16, 2022
…cessful without password bug (apache#9428) (apache#9531) * fix bug: After the test data source is successful, delete the password, re-test, or success * Modify the method of generating DatasourceUniqueId
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Search before asking
What happened
In the data source function module, I select the postgresql type data source. After the test is successful, I delete the password for the test, or it is successful.
What you expected to happen
How to reproduce
Fill in the correct data source connection information first, after the test is successful, delete the password, and then test
Anything else
The reason for the problem is because: the DataSourceClient created by dbType, user and jdbcUrl as the key when getting the DatasourceUniqueId in the 55th line of the DataSourceClientProvider, so the first DataSourceClient is found in the second test, So there will be cases where the test can be successful without a password
Version
2.0.5
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: