Doris Connection Parameters
Parameter |
Mandatory |
Description |
---|---|---|
Data Connection Type |
Yes |
Doris is selected by default and cannot be changed. |
Name |
Yes |
Name of the data connection to create. Data connection names can contain a maximum of 100 characters. They can contain only letters, digits, underscores (_), and hyphens (-). |
Description |
No |
A description which can help identify the data connection more easily. It can contain a maximum of 100 characters. |
Tag |
No |
Attribute of the data connection to create. Tags make management easier.
NOTE:
The tag name can contain only letters, digits, and underscores (_) and cannot start with an underscore (_) or contain more than 100 characters. |
Applicable Modules |
Yes |
Select the modules for which this connection is available.
NOTE:
|
Basic and Network Connectivity Configuration |
||
Doris Type |
Yes |
You can select MRS Doris or CloudTable Doris. |
MRS Cluster Name |
Yes |
This parameter is valid when Doris Type is set to MRS Doris. The Doris connection supports only MRS clusters of version 3.2.0 or later.
The name of the MRS cluster. Select an MRS cluster that Hive belongs to. Only MRS clusters are supported. A Hadoop cluster can be selected only after it is managed by MRS. All the MRS clusters with the same project ID and enterprise project are displayed.
NOTE:
If the connection fails after you select a cluster, check whether the MRS cluster can communicate with the CDM instance which functions as the agent. They can communicate with each other in the following scenarios:
NOTE:
If an agent is connected to multiple MRS clusters and one of the MRS clusters is deleted or abnormal, connections to the other MRS clusters will be affected. Therefore, you are advised to connect an agent to only one MRS cluster. |
Frontend IP |
Yes |
IP address of the frontend node in the Doris cluster. Use commas (,) to separate multiple IP addresses, for example, 127.0.0.1,127.0.0.2. To obtain them, perform the following operations:
|
MySQL protocol port |
Yes |
Port used by the Doris FE to query connections through the MySQL protocol. The default port is 9030. To obtain it, perform the following operations:
|
KMS Key |
Yes |
KMS key used to encrypt and decrypt data source authentication information. Select a default or custom key.
NOTE:
|
Agent |
Yes |
MRS is not a fully managed service and cannot be directly connected to DataArts Studio. A CDM cluster can provide an agent for DataArts Studio to communicate with non-fully-managed services. Therefore, you need to select a CDM cluster when creating an MRS data connection. If no CDM cluster is available, create one first by referring to Creating a CDM Cluster. As a network proxy, the CDM cluster must be able to communicate with the MRS cluster. To ensure network connectivity, the CDM cluster must be in the same region and AZ and use the same VPC and subnet as the MRS cluster. The security group rule must also allow the CDM cluster to communicate with the MRS cluster.
NOTE:
|
Enable Https |
No |
Whether to enable SSL encrypted transmission for Doris. This function is enabled by default. Disable it if SSL is disabled at the source. If HTTPS is enabled for the Doris cluster, this parameter is set to true. The default value is true. |
Data Source Driver Configuration |
||
Driver Name |
Yes |
Driver name. Currently, the MySQL JDBC driver is supported. The driver name is com.mysql.jdbc.Driver. |
Driver Source |
Yes |
Select the source of the driver file. |
Driver File Path |
Yes |
This parameter is mandatory when Driver file source is set to OBS path. Path of the driver file in the OBS bucket. You need to download the .jar driver file from the corresponding official website and upload it to the OBS bucket. MySQL driver: Obtain the driver from https://downloads.mysql.com/archives/c-j/. Version 5.1.48 or later is recommended. If the version is earlier than 5.1.48, error "The db user or password invalid" will be reported.
NOTE:
|
Driver File |
Yes |
This parameter is mandatory when Driver Source is set to Local file. Select a driver version that adapts to the database type. |
Data Source Authentication and Other Function Configuration |
||
Username |
Yes |
Username of the MRS or CloudTable cluster. If a new MRS user is used for connection, you need to log in to Manager and change the initial password. To create a data connection for an MRS security cluster, do not use user admin. The admin user is the default management page user and cannot be used as the authentication user of the security cluster. You can create an MRS user with a permanent password by referring to Creating a Kerberos Authentication User for an MRS Security Cluster. When creating an MRS data connection, set Username and Password to the new MRS username and password.
NOTE:
|
Password |
Yes |
It can also be the password for accessing the MRS or CloudTable cluster. |
Data Integration Configuration |
||
FE Port |
Yes |
HTTP port number of the FE in the Doris cluster. The default port number is 8030. If HTTPS is enabled, the default port number is 8050, which is used to write data using streamLoad. |
Database Name |
Yes |
Name of the database to be connected |
Fetch Size |
No |
Number of rows obtained by each request The default value is 1,000. |
Commit Size |
No |
Number of rows submitted in a batch. The default value is 10,000. |
Link Attributes |
No |
Click Add and set the attribute name and value. The value contains a maximum of 512 characters. You can click Delete to delete attributes. The following are examples:
|
Reference Sign |
No |
Reference sign, for example, ". Database enclosure character. For some databases, the value is case sensitive. Leave this parameter blank if no enclosure character is required. |
Check Stream Load Connectivity |
No |
Whether to check Doris stream load connectivity. To write data using stream load, ensure that stream load connectivity is normal. |
Creating a Kerberos Authentication User for an MRS Security Cluster
To create a data connection for an MRS security cluster, do not use user admin. The admin user is the default management page user and cannot be used as the authentication user of the security cluster. To create an MRS user, perform the following steps:
For clusters of MRS 3.x:
- Log in to MRS Manager as user admin.
- Choose System > Permission > Security Policy > Password Policy. Click Add Password Policy and add a policy under which the password never expires.
- Set Password Policy Name to neverexp.
- Set Password Validity Period (Days) to 0, indicating that the password never expires.
- Set Password Expiration Notification (Days) to 0.
- Retain the default values for other parameters.
- Choose Create to add a dedicated human-machine user as the Kerberos authentication user and set the password policy to neverexp. Select the user group superGroup for the user, and assign all roles to the user.
- For clusters of MRS 3.1.0 or later, the user must at least have permissions of the Manager_viewer role to create data connections in Management Center. To perform database, table, and data operations on components, the user must also have user group permissions of the components.
- For clusters earlier than MRS 3.1.0, the user must have permissions of the Manager_administrator or System_administrator role to create data connections in Management Center.
- A user with only the Manager_tenant or Manager_auditor permission cannot create connections.
. On the page displayed, click - Log in to Manager as the new user and change the initial password. Otherwise, the connection fails to be created.
- Synchronize IAM users.
- Log in to the MRS console.
- Choose Clusters > Active Clusters, select a running cluster, and click its name to go to its details page.
- In the Basic Information area of the Dashboard page, click Synchronize on the right side of IAM User Sync to synchronize IAM users.
- If the status is Synchronized, skip this step.
- When the policy of the user group to which the IAM user belongs changes from MRS ReadOnlyAccess to MRS CommonOperations, MRS FullAccess, or MRS Administrator, wait for 5 minutes until the new policy takes effect after the synchronization is complete because the SSSD (System Security Services Daemon) cache of cluster nodes needs time to be updated. Then, submit a job. Otherwise, the job may fail to be submitted.
- When the policy of the user group to which the IAM user belongs changes from MRS CommonOperations, MRS FullAccess, or MRS Administrator to MRS ReadOnlyAccess, wait for 5 minutes until the new policy takes effect after the synchronization is complete because the SSSD cache of cluster nodes needs time to be updated.
For clusters of MRS 2.x or earlier:
- Log in to the MRS Manager as user admin.
- On FusionInsight Manager, choose System Settings and click Configure Password Policy to modify the password policy.
- Set Password Validity Period (Days) to 0, indicating that the password never expires.
- Set Password Expiration Notification (Days) to 0.
- Retain the default values for other parameters.
- Choose
- For clusters of MRS 2.x or earlier, the user must have permissions of the Manager_administrator or System_administrator role to create data connections in Management Center.
- A user with only the Manager_tenant or Manager_auditor permission cannot create connections.
. On the page displayed, add a dedicated human-machine user as the Kerberos authentication user. Select the user group superGroup for the user, and assign all roles to the user.
- Log in to MRS Manager as the new user and change the initial password. Otherwise, the connection fails to be created.
- Synchronize IAM users.
- Log in to the MRS console.
- Choose Clusters > Active Clusters, select a running cluster, and click its name to go to its details page.
- In the Basic Information area of the Dashboard page, click Synchronize on the right side of IAM User Sync to synchronize IAM users.
- If the status is Synchronized, skip this step.
- When the policy of the user group to which the IAM user belongs changes from MRS ReadOnlyAccess to MRS CommonOperations, MRS FullAccess, or MRS Administrator, wait for 5 minutes until the new policy takes effect after the synchronization is complete because the SSSD (System Security Services Daemon) cache of cluster nodes needs time to be updated. Then, submit a job. Otherwise, the job may fail to be submitted.
- When the policy of the user group to which the IAM user belongs changes from MRS CommonOperations, MRS FullAccess, or MRS Administrator to MRS ReadOnlyAccess, wait for 5 minutes until the new policy takes effect after the synchronization is complete because the SSSD cache of cluster nodes needs time to be updated.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot