@alicloud/adb20211201 1.3.4 → 1.3.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@alicloud/adb20211201",
-  "version": "1.3.4",
+  "version": "1.3.5",
   "description": "",
   "main": "dist/client.js",
   "scripts": {

package/src/client.ts

@@ -373,6 +373,46 @@ export class LogAnalyzeResult extends $tea.Model {
   }
 }
 
+export class OperatorNode extends $tea.Model {
+  children?: OperatorNode[];
+  id?: number;
+  levelWidth?: number;
+  nodeDepth?: number;
+  nodeName?: string;
+  nodeWidth?: number;
+  parentId?: number;
+  stats?: OperatorNodeStats;
+  static names(): { [key: string]: string } {
+    return {
+      children: 'children',
+      id: 'id',
+      levelWidth: 'levelWidth',
+      nodeDepth: 'nodeDepth',
+      nodeName: 'nodeName',
+      nodeWidth: 'nodeWidth',
+      parentId: 'parentId',
+      stats: 'stats',
+    };
+  }
+
+  static types(): { [key: string]: any } {
+    return {
+      children: { 'type': 'array', 'itemType': OperatorNode },
+      id: 'number',
+      levelWidth: 'number',
+      nodeDepth: 'number',
+      nodeName: 'string',
+      nodeWidth: 'number',
+      parentId: 'number',
+      stats: OperatorNodeStats,
+    };
+  }
+
+  constructor(map?: { [key: string]: any }) {
+    super(map);
+  }
+}
+
 export class SerDeInfoModel extends $tea.Model {
   name?: string;
   parameters?: { [key: string]: string };
@@ -515,6 +555,28 @@ export class SparkAttemptInfo extends $tea.Model {
   }
 }
 
+export class SparkOperatorInfo extends $tea.Model {
+  metricValue?: number;
+  operatorName?: Buffer;
+  static names(): { [key: string]: string } {
+    return {
+      metricValue: 'MetricValue',
+      operatorName: 'OperatorName',
+    };
+  }
+
+  static types(): { [key: string]: any } {
+    return {
+      metricValue: 'number',
+      operatorName: 'Buffer',
+    };
+  }
+
+  constructor(map?: { [key: string]: any }) {
+    super(map);
+  }
+}
+
 export class SparkSession extends $tea.Model {
   active?: string;
   aliyunUid?: number;
@@ -9721,6 +9783,37 @@ export class FiltersTermiatedTimeRange extends $tea.Model {
   }
 }
 
+export class OperatorNodeStats extends $tea.Model {
+  bytes?: number;
+  outputRows?: number;
+  parameters?: string;
+  peakMemory?: number;
+  timeCost?: number;
+  static names(): { [key: string]: string } {
+    return {
+      bytes: 'bytes',
+      outputRows: 'outputRows',
+      parameters: 'parameters',
+      peakMemory: 'peakMemory',
+      timeCost: 'timeCost',
+    };
+  }
+
+  static types(): { [key: string]: any } {
+    return {
+      bytes: 'number',
+      outputRows: 'number',
+      parameters: 'string',
+      peakMemory: 'number',
+      timeCost: 'number',
+    };
+  }
+
+  constructor(map?: { [key: string]: any }) {
+    super(map);
+  }
+}
+
 export class CreateDBClusterRequestTag extends $tea.Model {
   key?: string;
   value?: string;
@@ -16579,9 +16672,12 @@ export default class Client extends OpenApi {
   }
 
   /**
-    * *   During a scaling event, you are not allowed to execute the `SUBMIT JOB` statement to submit asynchronous tasks. If your business requires asynchronous tasks, perform scaling during appropriate periods.
-    * *   When cluster specifications are scaled up or down, data in the cluster is migrated for redistribution. The amount of time required for data migration is proportional to the volume of data. During a scale-up or scale-down event, the services provided by the cluster are not interrupted. During a scale-down event, data migration can take up to dozens of hours to complete. Proceed with caution especially when your cluster contains a large amount of data.
+    * ### [](#)
+    * *   During a scaling event, you are not allowed to execute the `SUBMIT JOB` statement to submit asynchronous jobs. If your business requires asynchronous jobs, perform scaling during appropriate periods.
+    * *   When cluster specifications are scaled up or down, data in the cluster is migrated for redistribution. The amount of time that is required for data migration is proportional to the volume of data. During a scaling event, the services provided by the cluster are not interrupted. During a scale-down event, data migration can take up to dozens of hours to complete. Proceed with caution especially when your cluster contains a large amount of data.
     * *   If the cluster has a built-in dataset loaded, make sure that the cluster has reserved storage resources of at least 24 AnalyticDB compute units (ACUs). Otherwise, the built-in dataset cannot be used.
+    * *   When the scaling process is about to end, your service may encounter transient connections. We recommend that you scale your cluster during off-peak hours or make sure that your application is configured to automatically reconnect to your cluster.
+    * *   You can change an AnalyticDB for MySQL cluster from Data Warehouse Edition (V3.0) to Data Lakehouse Edition (V3.0), but not the other way around. For more information, see Change a cluster from Data Warehouse Edition to Data Lakehouse Edition.
     *
     * @param request ModifyDBClusterRequest
     * @param runtime runtime options for this request RuntimeOptions
@@ -16640,9 +16736,12 @@ export default class Client extends OpenApi {
   }
 
   /**
-    * *   During a scaling event, you are not allowed to execute the `SUBMIT JOB` statement to submit asynchronous tasks. If your business requires asynchronous tasks, perform scaling during appropriate periods.
-    * *   When cluster specifications are scaled up or down, data in the cluster is migrated for redistribution. The amount of time required for data migration is proportional to the volume of data. During a scale-up or scale-down event, the services provided by the cluster are not interrupted. During a scale-down event, data migration can take up to dozens of hours to complete. Proceed with caution especially when your cluster contains a large amount of data.
+    * ### [](#)
+    * *   During a scaling event, you are not allowed to execute the `SUBMIT JOB` statement to submit asynchronous jobs. If your business requires asynchronous jobs, perform scaling during appropriate periods.
+    * *   When cluster specifications are scaled up or down, data in the cluster is migrated for redistribution. The amount of time that is required for data migration is proportional to the volume of data. During a scaling event, the services provided by the cluster are not interrupted. During a scale-down event, data migration can take up to dozens of hours to complete. Proceed with caution especially when your cluster contains a large amount of data.
     * *   If the cluster has a built-in dataset loaded, make sure that the cluster has reserved storage resources of at least 24 AnalyticDB compute units (ACUs). Otherwise, the built-in dataset cannot be used.
+    * *   When the scaling process is about to end, your service may encounter transient connections. We recommend that you scale your cluster during off-peak hours or make sure that your application is configured to automatically reconnect to your cluster.
+    * *   You can change an AnalyticDB for MySQL cluster from Data Warehouse Edition (V3.0) to Data Lakehouse Edition (V3.0), but not the other way around. For more information, see Change a cluster from Data Warehouse Edition to Data Lakehouse Edition.
     *
     * @param request ModifyDBClusterRequest
     * @return ModifyDBClusterResponse