@alicloud/adb20211201 1.3.3 → 1.3.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/client.d.ts CHANGED
@@ -1,3 +1,4 @@
1
+ /// <reference types="node" />
1
2
  /**
2
3
  *
3
4
  */
@@ -173,6 +174,25 @@ export declare class LogAnalyzeResult extends $tea.Model {
173
174
  [key: string]: any;
174
175
  });
175
176
  }
177
+ export declare class OperatorNode extends $tea.Model {
178
+ children?: OperatorNode[];
179
+ id?: number;
180
+ levelWidth?: number;
181
+ nodeDepth?: number;
182
+ nodeName?: string;
183
+ nodeWidth?: number;
184
+ parentId?: number;
185
+ stats?: OperatorNodeStats;
186
+ static names(): {
187
+ [key: string]: string;
188
+ };
189
+ static types(): {
190
+ [key: string]: any;
191
+ };
192
+ constructor(map?: {
193
+ [key: string]: any;
194
+ });
195
+ }
176
196
  export declare class SerDeInfoModel extends $tea.Model {
177
197
  name?: string;
178
198
  parameters?: {
@@ -245,6 +265,19 @@ export declare class SparkAttemptInfo extends $tea.Model {
245
265
  [key: string]: any;
246
266
  });
247
267
  }
268
+ export declare class SparkOperatorInfo extends $tea.Model {
269
+ metricValue?: number;
270
+ operatorName?: Buffer;
271
+ static names(): {
272
+ [key: string]: string;
273
+ };
274
+ static types(): {
275
+ [key: string]: any;
276
+ };
277
+ constructor(map?: {
278
+ [key: string]: any;
279
+ });
280
+ }
248
281
  export declare class SparkSession extends $tea.Model {
249
282
  active?: string;
250
283
  aliyunUid?: number;
@@ -3099,6 +3132,7 @@ export declare class DescribeTablesResponse extends $tea.Model {
3099
3132
  }
3100
3133
  export declare class DescribeUserQuotaRequest extends $tea.Model {
3101
3134
  DBClusterId?: string;
3135
+ regionId?: string;
3102
3136
  static names(): {
3103
3137
  [key: string]: string;
3104
3138
  };
@@ -5507,6 +5541,22 @@ export declare class FiltersTermiatedTimeRange extends $tea.Model {
5507
5541
  [key: string]: any;
5508
5542
  });
5509
5543
  }
5544
+ export declare class OperatorNodeStats extends $tea.Model {
5545
+ bytes?: number;
5546
+ outputRows?: number;
5547
+ parameters?: string;
5548
+ peakMemory?: number;
5549
+ timeCost?: number;
5550
+ static names(): {
5551
+ [key: string]: string;
5552
+ };
5553
+ static types(): {
5554
+ [key: string]: any;
5555
+ };
5556
+ constructor(map?: {
5557
+ [key: string]: any;
5558
+ });
5559
+ }
5510
5560
  export declare class CreateDBClusterRequestTag extends $tea.Model {
5511
5561
  key?: string;
5512
5562
  value?: string;
@@ -7189,9 +7239,12 @@ export default class Client extends OpenApi {
7189
7239
  modifyClusterConnectionStringWithOptions(request: ModifyClusterConnectionStringRequest, runtime: $Util.RuntimeOptions): Promise<ModifyClusterConnectionStringResponse>;
7190
7240
  modifyClusterConnectionString(request: ModifyClusterConnectionStringRequest): Promise<ModifyClusterConnectionStringResponse>;
7191
7241
  /**
7192
- * * 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.
7193
- * * 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.
7242
+ * ### [](#)
7243
+ * * 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.
7244
+ * * 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.
7194
7245
  * * 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.
7246
+ * * 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.
7247
+ * * 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.
7195
7248
  *
7196
7249
  * @param request ModifyDBClusterRequest
7197
7250
  * @param runtime runtime options for this request RuntimeOptions
@@ -7199,9 +7252,12 @@ export default class Client extends OpenApi {
7199
7252
  */
7200
7253
  modifyDBClusterWithOptions(request: ModifyDBClusterRequest, runtime: $Util.RuntimeOptions): Promise<ModifyDBClusterResponse>;
7201
7254
  /**
7202
- * * 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.
7203
- * * 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.
7255
+ * ### [](#)
7256
+ * * 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.
7257
+ * * 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.
7204
7258
  * * 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.
7259
+ * * 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.
7260
+ * * 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.
7205
7261
  *
7206
7262
  * @param request ModifyDBClusterRequest
7207
7263
  * @return ModifyDBClusterResponse
package/dist/client.js CHANGED
@@ -289,6 +289,36 @@ class LogAnalyzeResult extends $tea.Model {
289
289
  }
290
290
  }
291
291
  exports.LogAnalyzeResult = LogAnalyzeResult;
292
+ class OperatorNode extends $tea.Model {
293
+ constructor(map) {
294
+ super(map);
295
+ }
296
+ static names() {
297
+ return {
298
+ children: 'children',
299
+ id: 'id',
300
+ levelWidth: 'levelWidth',
301
+ nodeDepth: 'nodeDepth',
302
+ nodeName: 'nodeName',
303
+ nodeWidth: 'nodeWidth',
304
+ parentId: 'parentId',
305
+ stats: 'stats',
306
+ };
307
+ }
308
+ static types() {
309
+ return {
310
+ children: { 'type': 'array', 'itemType': OperatorNode },
311
+ id: 'number',
312
+ levelWidth: 'number',
313
+ nodeDepth: 'number',
314
+ nodeName: 'string',
315
+ nodeWidth: 'number',
316
+ parentId: 'number',
317
+ stats: OperatorNodeStats,
318
+ };
319
+ }
320
+ }
321
+ exports.OperatorNode = OperatorNode;
292
322
  class SerDeInfoModel extends $tea.Model {
293
323
  constructor(map) {
294
324
  super(map);
@@ -397,6 +427,24 @@ class SparkAttemptInfo extends $tea.Model {
397
427
  }
398
428
  }
399
429
  exports.SparkAttemptInfo = SparkAttemptInfo;
430
+ class SparkOperatorInfo extends $tea.Model {
431
+ constructor(map) {
432
+ super(map);
433
+ }
434
+ static names() {
435
+ return {
436
+ metricValue: 'MetricValue',
437
+ operatorName: 'OperatorName',
438
+ };
439
+ }
440
+ static types() {
441
+ return {
442
+ metricValue: 'number',
443
+ operatorName: 'Buffer',
444
+ };
445
+ }
446
+ }
447
+ exports.SparkOperatorInfo = SparkOperatorInfo;
400
448
  class SparkSession extends $tea.Model {
401
449
  constructor(map) {
402
450
  super(map);
@@ -4420,11 +4468,13 @@ class DescribeUserQuotaRequest extends $tea.Model {
4420
4468
  static names() {
4421
4469
  return {
4422
4470
  DBClusterId: 'DBClusterId',
4471
+ regionId: 'RegionId',
4423
4472
  };
4424
4473
  }
4425
4474
  static types() {
4426
4475
  return {
4427
4476
  DBClusterId: 'string',
4477
+ regionId: 'string',
4428
4478
  };
4429
4479
  }
4430
4480
  }
@@ -7689,6 +7739,30 @@ class FiltersTermiatedTimeRange extends $tea.Model {
7689
7739
  }
7690
7740
  }
7691
7741
  exports.FiltersTermiatedTimeRange = FiltersTermiatedTimeRange;
7742
+ class OperatorNodeStats extends $tea.Model {
7743
+ constructor(map) {
7744
+ super(map);
7745
+ }
7746
+ static names() {
7747
+ return {
7748
+ bytes: 'bytes',
7749
+ outputRows: 'outputRows',
7750
+ parameters: 'parameters',
7751
+ peakMemory: 'peakMemory',
7752
+ timeCost: 'timeCost',
7753
+ };
7754
+ }
7755
+ static types() {
7756
+ return {
7757
+ bytes: 'number',
7758
+ outputRows: 'number',
7759
+ parameters: 'string',
7760
+ peakMemory: 'number',
7761
+ timeCost: 'number',
7762
+ };
7763
+ }
7764
+ }
7765
+ exports.OperatorNodeStats = OperatorNodeStats;
7692
7766
  class CreateDBClusterRequestTag extends $tea.Model {
7693
7767
  constructor(map) {
7694
7768
  super(map);
@@ -13339,9 +13413,12 @@ class Client extends openapi_client_1.default {
13339
13413
  return await this.modifyClusterConnectionStringWithOptions(request, runtime);
13340
13414
  }
13341
13415
  /**
13342
- * * 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.
13343
- * * 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.
13416
+ * ### [](#)
13417
+ * * 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.
13418
+ * * 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.
13344
13419
  * * 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.
13420
+ * * 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.
13421
+ * * 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.
13345
13422
  *
13346
13423
  * @param request ModifyDBClusterRequest
13347
13424
  * @param runtime runtime options for this request RuntimeOptions
@@ -13391,9 +13468,12 @@ class Client extends openapi_client_1.default {
13391
13468
  return $tea.cast(await this.callApi(params, req, runtime), new ModifyDBClusterResponse({}));
13392
13469
  }
13393
13470
  /**
13394
- * * 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.
13395
- * * 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.
13471
+ * ### [](#)
13472
+ * * 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.
13473
+ * * 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.
13396
13474
  * * 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.
13475
+ * * 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.
13476
+ * * 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.
13397
13477
  *
13398
13478
  * @param request ModifyDBClusterRequest
13399
13479
  * @return ModifyDBClusterResponse