@alicloud/dataworks-public20200518 4.4.5 → 4.4.6

package/dist/client.d.ts

@@ -12422,16 +12422,8 @@ export declare class GetBaselineKeyPathResponseBodyDataRuns extends $tea.Model {
     beginRunningTime?: number;
     beginWaitResTime?: number;
     beginWaitTimeTime?: number;
-    bizdate?: number;
-    cycTime?: number;
     endCast?: number;
     finishTime?: number;
-    inGroupId?: number;
-    instanceId?: number;
-    nodeId?: number;
-    nodeName?: string;
-    owner?: string;
-    projectId?: number;
     status?: string;
     static names(): {
         [key: string]: string;
@@ -12447,7 +12439,7 @@ export declare class GetBaselineKeyPathResponseBodyDataTopics extends $tea.Model
     addTime?: number;
     instanceId?: number;
     topicId?: number;
-    topicName?: number;
+    topicName?: string;
     static names(): {
         [key: string]: string;
     };
@@ -19090,7 +19082,20 @@ export default class Client extends OpenApi {
       * @return UpdateConnectionResponse
      */
     updateConnection(request: UpdateConnectionRequest): Promise<UpdateConnectionResponse>;
+    /**
+      * DataWorks allows you to specify a default global configuration only for the processing rules of DDL messages in synchronization solutions. After you configure the **processing rules of DDL messages** in synchronization solutions, the configuration is used as the default global configuration and applies to all real-time synchronization nodes in the solutions. You can modify the **processing rules of DDL messages** based on your business requirements. For more information about how to configure a synchronization solution, see [Synchronization solutions](~~199008~~).
+      *
+      * @param request UpdateDIProjectConfigRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return UpdateDIProjectConfigResponse
+     */
     updateDIProjectConfigWithOptions(request: UpdateDIProjectConfigRequest, runtime: $Util.RuntimeOptions): Promise<UpdateDIProjectConfigResponse>;
+    /**
+      * DataWorks allows you to specify a default global configuration only for the processing rules of DDL messages in synchronization solutions. After you configure the **processing rules of DDL messages** in synchronization solutions, the configuration is used as the default global configuration and applies to all real-time synchronization nodes in the solutions. You can modify the **processing rules of DDL messages** based on your business requirements. For more information about how to configure a synchronization solution, see [Synchronization solutions](~~199008~~).
+      *
+      * @param request UpdateDIProjectConfigRequest
+      * @return UpdateDIProjectConfigResponse
+     */
     updateDIProjectConfig(request: UpdateDIProjectConfigRequest): Promise<UpdateDIProjectConfigResponse>;
     updateDISyncTaskWithOptions(request: UpdateDISyncTaskRequest, runtime: $Util.RuntimeOptions): Promise<UpdateDISyncTaskResponse>;
     updateDISyncTask(request: UpdateDISyncTaskRequest): Promise<UpdateDISyncTaskResponse>;

package/dist/client.js

@@ -17534,16 +17534,8 @@ class GetBaselineKeyPathResponseBodyDataRuns extends $tea.Model {
             beginRunningTime: 'BeginRunningTime',
             beginWaitResTime: 'BeginWaitResTime',
             beginWaitTimeTime: 'BeginWaitTimeTime',
-            bizdate: 'Bizdate',
-            cycTime: 'CycTime',
             endCast: 'EndCast',
             finishTime: 'FinishTime',
-            inGroupId: 'InGroupId',
-            instanceId: 'InstanceId',
-            nodeId: 'NodeId',
-            nodeName: 'NodeName',
-            owner: 'Owner',
-            projectId: 'ProjectId',
             status: 'Status',
         };
     }
@@ -17554,16 +17546,8 @@ class GetBaselineKeyPathResponseBodyDataRuns extends $tea.Model {
             beginRunningTime: 'number',
             beginWaitResTime: 'number',
             beginWaitTimeTime: 'number',
-            bizdate: 'number',
-            cycTime: 'number',
             endCast: 'number',
             finishTime: 'number',
-            inGroupId: 'number',
-            instanceId: 'number',
-            nodeId: 'number',
-            nodeName: 'string',
-            owner: 'string',
-            projectId: 'number',
             status: 'string',
         };
     }
@@ -17586,7 +17570,7 @@ class GetBaselineKeyPathResponseBodyDataTopics extends $tea.Model {
             addTime: 'number',
             instanceId: 'number',
             topicId: 'number',
-            topicName: 'number',
+            topicName: 'string',
         };
     }
 }
@@ -35133,6 +35117,13 @@ class Client extends openapi_client_1.default {
         let runtime = new $Util.RuntimeOptions({});
         return await this.updateConnectionWithOptions(request, runtime);
     }
+    /**
+      * DataWorks allows you to specify a default global configuration only for the processing rules of DDL messages in synchronization solutions. After you configure the **processing rules of DDL messages** in synchronization solutions, the configuration is used as the default global configuration and applies to all real-time synchronization nodes in the solutions. You can modify the **processing rules of DDL messages** based on your business requirements. For more information about how to configure a synchronization solution, see [Synchronization solutions](~~199008~~).
+      *
+      * @param request UpdateDIProjectConfigRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return UpdateDIProjectConfigResponse
+     */
     async updateDIProjectConfigWithOptions(request, runtime) {
         tea_util_1.default.validateModel(request);
         let query = {};
@@ -35164,6 +35155,12 @@ class Client extends openapi_client_1.default {
         });
         return $tea.cast(await this.callApi(params, req, runtime), new UpdateDIProjectConfigResponse({}));
     }
+    /**
+      * DataWorks allows you to specify a default global configuration only for the processing rules of DDL messages in synchronization solutions. After you configure the **processing rules of DDL messages** in synchronization solutions, the configuration is used as the default global configuration and applies to all real-time synchronization nodes in the solutions. You can modify the **processing rules of DDL messages** based on your business requirements. For more information about how to configure a synchronization solution, see [Synchronization solutions](~~199008~~).
+      *
+      * @param request UpdateDIProjectConfigRequest
+      * @return UpdateDIProjectConfigResponse
+     */
     async updateDIProjectConfig(request) {
         let runtime = new $Util.RuntimeOptions({});
         return await this.updateDIProjectConfigWithOptions(request, runtime);