[Bug] [DataSource] Add hive datasource failed

[caiiansheng]

Search before asking

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

What happened

logs:

config:

PS: Kerberos is not enabled in my cluster

What you expected to happen

add new hive datasource success.

How to reproduce

add new hive datasource success.

Anything else

The bug occurred in 2.01 release, and there was no problem with 2.0 release.

Version

2.0.1

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]

Hi:

• Thank you for your feedback, we have received your issue, Please wait patiently for a reply.
• In order for us to understand your request as soon as possible, please provide detailed information、version or pictures.
• If you haven't received a reply for a long time, you can subscribe to the developer's email，Mail subscription steps reference https://dolphinscheduler.apache.org/en-us/community/development/subscribe.html ,Then write the issue URL in the email content and send question to [email protected].

[SbloodyS]

It will be fixed in 2.0.2-release.

An alternative way to solve this problem is remove java.security.krb5.conf.path in conf/common.properties.

[zhongjiajie]

It will be fixed in 2.0.2-release.

An alternative way to solve this problem is remove java.security.krb5.conf.path in conf/common.properties.

One more question, does it fix in dev branch ? @SbloodyS

[zhongjiajie]

If fix in dev, I would close this issue

[caiiansheng]

@SbloodyS ,hi ：
I tried to remove "java.security.krb5.conf.path" as you said, but there was an error:

1. If set ”{auth=noSasl}“
   
   logs:
   
2. If don't set ”{auth=noSasl}“

and logs:

[SbloodyS]

@zhongjiajie Yes.It has been fixed in dev. PR: #7393

@caiiansheng Hive datasource's other params did not work. It will be fixed in 2.0.2-release. Related issue: #7485

[zhongjiajie]

Duplicate to #7392 and already fix in #7393. Will release in 2.0.2 and also fix in dev. You could reopen this issue when you have an additional problem.

BTW, thanks @SbloodyS for the clarification.