From cfadd96505e529715e65be7813170d6cac94465c Mon Sep 17 00:00:00 2001 From: proposalbot Date: Wed, 17 Jan 2024 12:27:39 +0000 Subject: [PATCH] Changes to ddm_umn from docs/doc-exports#1019 (reverting ddm umn to state before Reviewed-by: Wagner, Fabian Co-authored-by: proposalbot Co-committed-by: proposalbot --- .../step_4_log_in_to_the_ddm_schema.rst | 23 ------------------- .../usage_constraints/data_nodes.rst | 2 +- 2 files changed, 1 insertion(+), 24 deletions(-) diff --git a/umn/source/getting_started/step_4_log_in_to_the_ddm_schema.rst b/umn/source/getting_started/step_4_log_in_to_the_ddm_schema.rst index c38b3b8..b82ad5e 100644 --- a/umn/source/getting_started/step_4_log_in_to_the_ddm_schema.rst +++ b/umn/source/getting_started/step_4_log_in_to_the_ddm_schema.rst @@ -39,8 +39,6 @@ For details about method 2, see :ref:`Using the MySQL CLI to Log In to a Schema For details about method 3, see :ref:`Using a JDBC Driver to Log In to a Schema `. -For details about method 4, see :ref:`Logging In to a DDM Instance on the DDM Console `. - .. note:: #. For security purposes, select an ECS in the same VPC as your DDM instance. @@ -183,24 +181,3 @@ Using a JDBC Driver to Log In to a Schema - **loadBalancePingTimeout**: indicates the time in milliseconds that the connection will wait for a response to a ping operation when you set **loadBalanceValidateConnectionOnSwapServer** to **true**. - **retriesAllDown**: indicates the maximum number of connection attempts before an exception is thrown when a valid host is searched. SQLException will be returned if the threshold of retries is reached with no valid connections obtained. - **connectTimeout**: indicates the maximum amount of time in milliseconds that the JDBC driver is willing to wait to set up a socket connection. **0** indicates that the connection does not time out. This parameter is available to JDK-1.4 or later versions. The default value is **0**. - -.. _ddm_02_0005__section144072633313: - -Logging In to a DDM Instance on the DDM Console ------------------------------------------------ - -#. Log in to the DDM console. - -#. In the navigation pane, choose **Instances**. - -#. In the instance list, locate the required instance and click **Log In** in the **Operation** column. - - On the displayed page, enter the required username and password. - -#. On the displayed page, enter username and password of the DDM account. - -#. Click **Test Connection**. - -#. (Optional) Enable **Collect Metadata Periodically** and **Show Executed SQL Statements**. - -#. Ensure that all settings are correct and click **Log In**. diff --git a/umn/source/service_overview/usage_constraints/data_nodes.rst b/umn/source/service_overview/usage_constraints/data_nodes.rst index 3fd3294..7934908 100644 --- a/umn/source/service_overview/usage_constraints/data_nodes.rst +++ b/umn/source/service_overview/usage_constraints/data_nodes.rst @@ -17,4 +17,4 @@ Constraints on data nodes are as follows: - If you are using MySQL 8.0, select **Case insensitive** for **Table Name** when you create a MySQL instance. - Modifying configurations of a data node may result in an exception in using your DDM instance. After the modification, click **Synchronize Data Node Information** on the **Data Nodes** page to synchronize changes from the data node to DDM. -- Character set GBK is not allowed for data nodes. +- DDM data nodes do not support GBK character sets.