[INLONG-9972][Sort] Pulsar connector support authentication when connecting to Pulsar cluster #9973
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
According to https://pulsar.apache.org/docs/next/security-jwt/
Some pulsar cluster have authentication opened in some cases, the sort connector should support authentication
Modifications
Added two parameter used in authentication
1、pulsar client auth plugin class name, e.g. org.apache.pulsar.client.impl.auth.AuthenticationToken
2、pulsar client auth params, the value should be compatible with the clientAuthPluginClassName, see also in
https://pulsar.apache.org/docs/next/security-jwt/
Verifying this change
Tested in pulsar cluster with authentication and the ExtractNode teste in PulsarSqlParserTest