@alicloud/dataworks-public20200518 4.4.1 → 4.4.2

package/dist/client.d.ts

@@ -764,8 +764,10 @@ export declare class CreateDataServiceApiRequest extends $tea.Model {
     protocols?: string;
     registrationDetails?: string;
     requestMethod?: number;
+    resourceGroupId?: number;
     responseContentType?: number;
     scriptDetails?: string;
+    sqlMode?: number;
     tenantId?: number;
     timeout?: number;
     visibleRange?: number;
@@ -9240,6 +9242,7 @@ export declare class ListTopicsResponse extends $tea.Model {
 export declare class MountDirectoryRequest extends $tea.Model {
     targetId?: string;
     targetType?: string;
+    targetUserId?: string;
     static names(): {
         [key: string]: string;
     };
@@ -10615,6 +10618,7 @@ export declare class TopTenErrorTimesInstanceResponse extends $tea.Model {
 export declare class UmountDirectoryRequest extends $tea.Model {
     targetId?: string;
     targetType?: string;
+    targetUserId?: string;
     static names(): {
         [key: string]: string;
     };
@@ -10936,6 +10940,7 @@ export declare class UpdateDataServiceApiRequest extends $tea.Model {
     protocols?: string;
     registrationDetails?: string;
     requestMethod?: number;
+    resourceGroupId?: number;
     responseContentType?: number;
     scriptDetails?: string;
     tenantId?: number;
@@ -14042,6 +14047,7 @@ export declare class GetMetaTableIntroWikiResponseBodyData extends $tea.Model {
 }
 export declare class GetMetaTableLineageResponseBodyDataDataEntityList extends $tea.Model {
     createTimestamp?: number;
+    databaseName?: string;
     tableGuid?: string;
     tableName?: string;
     static names(): {
@@ -14263,6 +14269,7 @@ export declare class GetNodeResponseBodyData extends $tea.Model {
     description?: string;
     dqcDescription?: string;
     dqcType?: number;
+    fileType?: number;
     nodeId?: number;
     nodeName?: string;
     ownerId?: string;
@@ -14273,6 +14280,7 @@ export declare class GetNodeResponseBodyData extends $tea.Model {
     relatedFlowId?: number;
     repeatInterval?: number;
     repeatability?: string;
+    resGroupIdentifier?: string;
     resGroupName?: string;
     schedulerType?: string;
     static names(): {
@@ -16592,6 +16600,7 @@ export declare class ListNodesResponseBodyDataNodes extends $tea.Model {
     description?: string;
     dqcDescription?: string;
     dqcType?: number;
+    fileType?: number;
     nodeId?: number;
     nodeName?: string;
     ownerId?: string;
@@ -16602,6 +16611,7 @@ export declare class ListNodesResponseBodyDataNodes extends $tea.Model {
     relatedFlowId?: number;
     repeatInterval?: number;
     repeatability?: boolean;
+    resGroupIdentifier?: string;
     resGroupName?: string;
     schedulerType?: string;
     static names(): {
@@ -17879,7 +17889,20 @@ export default class Client extends OpenApi {
     abolishDataServiceApi(request: AbolishDataServiceApiRequest): Promise<AbolishDataServiceApiResponse>;
     addMetaCollectionEntityWithOptions(request: AddMetaCollectionEntityRequest, runtime: $Util.RuntimeOptions): Promise<AddMetaCollectionEntityResponse>;
     addMetaCollectionEntity(request: AddMetaCollectionEntityRequest): Promise<AddMetaCollectionEntityResponse>;
+    /**
+      * For more information about how to add your Alibaba Cloud account or a RAM user as a member of a DataWorks workspace, see [Add a member to a DataWorks workspace](~~136941~~).
+      *
+      * @param request AddProjectMemberToRoleRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return AddProjectMemberToRoleResponse
+     */
     addProjectMemberToRoleWithOptions(request: AddProjectMemberToRoleRequest, runtime: $Util.RuntimeOptions): Promise<AddProjectMemberToRoleResponse>;
+    /**
+      * For more information about how to add your Alibaba Cloud account or a RAM user as a member of a DataWorks workspace, see [Add a member to a DataWorks workspace](~~136941~~).
+      *
+      * @param request AddProjectMemberToRoleRequest
+      * @return AddProjectMemberToRoleResponse
+     */
     addProjectMemberToRole(request: AddProjectMemberToRoleRequest): Promise<AddProjectMemberToRoleResponse>;
     addToMetaCategoryWithOptions(request: AddToMetaCategoryRequest, runtime: $Util.RuntimeOptions): Promise<AddToMetaCategoryResponse>;
     addToMetaCategory(request: AddToMetaCategoryRequest): Promise<AddToMetaCategoryResponse>;
@@ -17912,7 +17935,20 @@ export default class Client extends OpenApi {
       * @return CreateConnectionResponse
      */
     createConnection(request: CreateConnectionRequest): Promise<CreateConnectionResponse>;
+    /**
+      * DataWorks allows you to use only the CreateDISyncTask operation to create a batch synchronization node in Data Integration. To create a real-time synchronization node or a synchronization solution, you must first call the [GenerateDISyncTaskConfigForCreating](~~383463~~) operation to generate the ID of an asynchronous thread and call the [QueryDISyncTaskConfigProcessResult](~~383465~~) operation to obtain the asynchronously generated parameters based on the ID. Then, you can call the CreateDISyncTask operation and use the parameters as request parameters to create a real-time synchronization node or a synchronization solution in Data Integration.
+      *
+      * @param request CreateDISyncTaskRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return CreateDISyncTaskResponse
+     */
     createDISyncTaskWithOptions(request: CreateDISyncTaskRequest, runtime: $Util.RuntimeOptions): Promise<CreateDISyncTaskResponse>;
+    /**
+      * DataWorks allows you to use only the CreateDISyncTask operation to create a batch synchronization node in Data Integration. To create a real-time synchronization node or a synchronization solution, you must first call the [GenerateDISyncTaskConfigForCreating](~~383463~~) operation to generate the ID of an asynchronous thread and call the [QueryDISyncTaskConfigProcessResult](~~383465~~) operation to obtain the asynchronously generated parameters based on the ID. Then, you can call the CreateDISyncTask operation and use the parameters as request parameters to create a real-time synchronization node or a synchronization solution in Data Integration.
+      *
+      * @param request CreateDISyncTaskRequest
+      * @return CreateDISyncTaskResponse
+     */
     createDISyncTask(request: CreateDISyncTaskRequest): Promise<CreateDISyncTaskResponse>;
     /**
       * @deprecated
@@ -17960,7 +17996,48 @@ export default class Client extends OpenApi {
     createFile(request: CreateFileRequest): Promise<CreateFileResponse>;
     createFolderWithOptions(request: CreateFolderRequest, runtime: $Util.RuntimeOptions): Promise<CreateFolderResponse>;
     createFolder(request: CreateFolderRequest): Promise<CreateFolderResponse>;
+    /**
+      * The import package must be uploaded. Example of the upload method:
+      * Config config = new Config();
+      * config.setAccessKeyId(accessId);
+      * config.setAccessKeySecret(accessKey);
+      * config.setEndpoint(popEndpoint);
+      * config.setRegionId(regionId);
+      * Client client = new Client(config);
+      * CreateImportMigrationAdvanceRequest request = new CreateImportMigrationAdvanceRequest();
+      * request.setName("test_migration_api\\_" + System.currentTimeMillis());
+      * request.setProjectId(123456L);
+      * request.setPackageType("DATAWORKS_MODEL");
+      * request.setPackageFileObject(new FileInputStream("/home/admin/Downloads/test.zip"));
+      * RuntimeOptions runtime = new RuntimeOptions();
+      * CreateImportMigrationResponse response = client.createImportMigrationAdvance(request, runtime);
+      * ...
+      *
+      * @param request CreateImportMigrationRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return CreateImportMigrationResponse
+     */
     createImportMigrationWithOptions(request: CreateImportMigrationRequest, runtime: $Util.RuntimeOptions): Promise<CreateImportMigrationResponse>;
+    /**
+      * The import package must be uploaded. Example of the upload method:
+      * Config config = new Config();
+      * config.setAccessKeyId(accessId);
+      * config.setAccessKeySecret(accessKey);
+      * config.setEndpoint(popEndpoint);
+      * config.setRegionId(regionId);
+      * Client client = new Client(config);
+      * CreateImportMigrationAdvanceRequest request = new CreateImportMigrationAdvanceRequest();
+      * request.setName("test_migration_api\\_" + System.currentTimeMillis());
+      * request.setProjectId(123456L);
+      * request.setPackageType("DATAWORKS_MODEL");
+      * request.setPackageFileObject(new FileInputStream("/home/admin/Downloads/test.zip"));
+      * RuntimeOptions runtime = new RuntimeOptions();
+      * CreateImportMigrationResponse response = client.createImportMigrationAdvance(request, runtime);
+      * ...
+      *
+      * @param request CreateImportMigrationRequest
+      * @return CreateImportMigrationResponse
+     */
     createImportMigration(request: CreateImportMigrationRequest): Promise<CreateImportMigrationResponse>;
     createImportMigrationAdvance(request: CreateImportMigrationAdvanceRequest, runtime: $Util.RuntimeOptions): Promise<CreateImportMigrationResponse>;
     /**
@@ -17980,7 +18057,20 @@ export default class Client extends OpenApi {
     createManualDag(request: CreateManualDagRequest): Promise<CreateManualDagResponse>;
     createMetaCategoryWithOptions(request: CreateMetaCategoryRequest, runtime: $Util.RuntimeOptions): Promise<CreateMetaCategoryResponse>;
     createMetaCategory(request: CreateMetaCategoryRequest): Promise<CreateMetaCategoryResponse>;
+    /**
+      * Collections are classified into various types. The names of collections of the same type must be different.
+      *
+      * @param request CreateMetaCollectionRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return CreateMetaCollectionResponse
+     */
     createMetaCollectionWithOptions(request: CreateMetaCollectionRequest, runtime: $Util.RuntimeOptions): Promise<CreateMetaCollectionResponse>;
+    /**
+      * Collections are classified into various types. The names of collections of the same type must be different.
+      *
+      * @param request CreateMetaCollectionRequest
+      * @return CreateMetaCollectionResponse
+     */
     createMetaCollection(request: CreateMetaCollectionRequest): Promise<CreateMetaCollectionResponse>;
     createPermissionApplyOrderWithOptions(request: CreatePermissionApplyOrderRequest, runtime: $Util.RuntimeOptions): Promise<CreatePermissionApplyOrderResponse>;
     createPermissionApplyOrder(request: CreatePermissionApplyOrderRequest): Promise<CreatePermissionApplyOrderResponse>;
@@ -18047,7 +18137,20 @@ export default class Client extends OpenApi {
     deleteProjectMember(request: DeleteProjectMemberRequest): Promise<DeleteProjectMemberResponse>;
     deleteQualityEntityWithOptions(request: DeleteQualityEntityRequest, runtime: $Util.RuntimeOptions): Promise<DeleteQualityEntityResponse>;
     deleteQualityEntity(request: DeleteQualityEntityRequest): Promise<DeleteQualityEntityResponse>;
+    /**
+      * In Data Quality, you must configure monitoring rules based on a partition filter expression. Data Quality uses these rules to detect changes in source data and dirty data generated during the process of extract, transformation, load (ETL). Thereby, Data Quality automatically blocks the nodes that involve dirty data to stop dirty data from spreading downstream. This prevents nodes from producing unexpected dirty data that affects normal use and business decisions. You can go to the Manage Subscriptions page to add subscribers for a partition filter expression. When the monitoring rule described by the partition filter expression is triggered, the subscribers can receive notifications and troubleshoot errors in a timely manner. For more information, see [Configure monitoring rules for MaxCompute](~~73690~~).
+      *
+      * @param request DeleteQualityFollowerRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return DeleteQualityFollowerResponse
+     */
     deleteQualityFollowerWithOptions(request: DeleteQualityFollowerRequest, runtime: $Util.RuntimeOptions): Promise<DeleteQualityFollowerResponse>;
+    /**
+      * In Data Quality, you must configure monitoring rules based on a partition filter expression. Data Quality uses these rules to detect changes in source data and dirty data generated during the process of extract, transformation, load (ETL). Thereby, Data Quality automatically blocks the nodes that involve dirty data to stop dirty data from spreading downstream. This prevents nodes from producing unexpected dirty data that affects normal use and business decisions. You can go to the Manage Subscriptions page to add subscribers for a partition filter expression. When the monitoring rule described by the partition filter expression is triggered, the subscribers can receive notifications and troubleshoot errors in a timely manner. For more information, see [Configure monitoring rules for MaxCompute](~~73690~~).
+      *
+      * @param request DeleteQualityFollowerRequest
+      * @return DeleteQualityFollowerResponse
+     */
     deleteQualityFollower(request: DeleteQualityFollowerRequest): Promise<DeleteQualityFollowerResponse>;
     deleteQualityRelativeNodeWithOptions(request: DeleteQualityRelativeNodeRequest, runtime: $Util.RuntimeOptions): Promise<DeleteQualityRelativeNodeResponse>;
     deleteQualityRelativeNode(request: DeleteQualityRelativeNodeRequest): Promise<DeleteQualityRelativeNodeResponse>;
@@ -18071,9 +18174,37 @@ export default class Client extends OpenApi {
     establishRelationTableToBusiness(request: EstablishRelationTableToBusinessRequest): Promise<EstablishRelationTableToBusinessResponse>;
     exportDataSourcesWithOptions(request: ExportDataSourcesRequest, runtime: $Util.RuntimeOptions): Promise<ExportDataSourcesResponse>;
     exportDataSources(request: ExportDataSourcesRequest): Promise<ExportDataSourcesResponse>;
+    /**
+      * DataWorks allows you to use only the [CreateDISyncTask](~~278725~~) operation to create a batch synchronization node in Data Integration. To create a real-time synchronization node or a synchronization solution, you must first call the [GenerateDISyncTaskConfigForCreating](~~383463~~) operation to generate the ID of an asynchronous thread and call the [QueryDISyncTaskConfigProcessResult](~~383465~~) operation to obtain the asynchronously generated parameters based on the ID. Then, you can call the [CreateDISyncTask](~~278725~~) operation and use the parameters as request parameters to create a real-time synchronization node or a synchronization solution in Data Integration.
+      * DataWorks allows you to create real-time synchronization nodes and synchronization solutions in Data Integration only in asynchronous mode.
+      *
+      * @param request GenerateDISyncTaskConfigForCreatingRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return GenerateDISyncTaskConfigForCreatingResponse
+     */
     generateDISyncTaskConfigForCreatingWithOptions(request: GenerateDISyncTaskConfigForCreatingRequest, runtime: $Util.RuntimeOptions): Promise<GenerateDISyncTaskConfigForCreatingResponse>;
+    /**
+      * DataWorks allows you to use only the [CreateDISyncTask](~~278725~~) operation to create a batch synchronization node in Data Integration. To create a real-time synchronization node or a synchronization solution, you must first call the [GenerateDISyncTaskConfigForCreating](~~383463~~) operation to generate the ID of an asynchronous thread and call the [QueryDISyncTaskConfigProcessResult](~~383465~~) operation to obtain the asynchronously generated parameters based on the ID. Then, you can call the [CreateDISyncTask](~~278725~~) operation and use the parameters as request parameters to create a real-time synchronization node or a synchronization solution in Data Integration.
+      * DataWorks allows you to create real-time synchronization nodes and synchronization solutions in Data Integration only in asynchronous mode.
+      *
+      * @param request GenerateDISyncTaskConfigForCreatingRequest
+      * @return GenerateDISyncTaskConfigForCreatingResponse
+     */
     generateDISyncTaskConfigForCreating(request: GenerateDISyncTaskConfigForCreatingRequest): Promise<GenerateDISyncTaskConfigForCreatingResponse>;
+    /**
+      * DataWorks allows you to use only the [UpdateDISyncTask](~~289109~~) operation to update a batch synchronization node in Data Integration. To update a real-time synchronization node or a synchronization solution, you must first call the GenerateDISyncTaskConfigForUpdating operation to generate the ID of an asynchronous thread and call the [QueryDISyncTaskConfigProcessResult](~~383465~~) operation to obtain the asynchronously generated parameters based on the ID. Then, you can call the UpdateDISyncTask operation and use the parameters as request parameters to update a real-time synchronization node or a synchronization solution in Data Integration. DataWorks allows you to update real-time synchronization nodes and synchronization solutions in Data Integration only in asynchronous mode.
+      *
+      * @param request GenerateDISyncTaskConfigForUpdatingRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return GenerateDISyncTaskConfigForUpdatingResponse
+     */
     generateDISyncTaskConfigForUpdatingWithOptions(request: GenerateDISyncTaskConfigForUpdatingRequest, runtime: $Util.RuntimeOptions): Promise<GenerateDISyncTaskConfigForUpdatingResponse>;
+    /**
+      * DataWorks allows you to use only the [UpdateDISyncTask](~~289109~~) operation to update a batch synchronization node in Data Integration. To update a real-time synchronization node or a synchronization solution, you must first call the GenerateDISyncTaskConfigForUpdating operation to generate the ID of an asynchronous thread and call the [QueryDISyncTaskConfigProcessResult](~~383465~~) operation to obtain the asynchronously generated parameters based on the ID. Then, you can call the UpdateDISyncTask operation and use the parameters as request parameters to update a real-time synchronization node or a synchronization solution in Data Integration. DataWorks allows you to update real-time synchronization nodes and synchronization solutions in Data Integration only in asynchronous mode.
+      *
+      * @param request GenerateDISyncTaskConfigForUpdatingRequest
+      * @return GenerateDISyncTaskConfigForUpdatingResponse
+     */
     generateDISyncTaskConfigForUpdating(request: GenerateDISyncTaskConfigForUpdatingRequest): Promise<GenerateDISyncTaskConfigForUpdatingResponse>;
     getBaselineWithOptions(request: GetBaselineRequest, runtime: $Util.RuntimeOptions): Promise<GetBaselineResponse>;
     getBaseline(request: GetBaselineRequest): Promise<GetBaselineResponse>;
@@ -18091,7 +18222,38 @@ export default class Client extends OpenApi {
     getDISyncInstanceInfo(request: GetDISyncInstanceInfoRequest): Promise<GetDISyncInstanceInfoResponse>;
     getDISyncTaskWithOptions(request: GetDISyncTaskRequest, runtime: $Util.RuntimeOptions): Promise<GetDISyncTaskResponse>;
     getDISyncTask(request: GetDISyncTaskRequest): Promise<GetDISyncTaskResponse>;
+    /**
+      * Supported DAG types:
+      * *   MANUAL: the DAG for a manually triggered workflow.
+      * *   SMOKE_TEST: the DAG for a smoke testing workflow.
+      * *   SUPPLY_DATA: the DAG for a data backfill instance.
+      * *   BUSINESS_PROCESS_DAG: the DAG for a one-time workflow.
+      * Supported DAG states:
+      * *   CREATED: The DAG is created.
+      * *   RUNNING: The DAG is running.
+      * *   FAILURE: The DAG fails to run.
+      * *   SUCCESS: The DAG successfully runs.
+      *
+      * @param request GetDagRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return GetDagResponse
+     */
     getDagWithOptions(request: GetDagRequest, runtime: $Util.RuntimeOptions): Promise<GetDagResponse>;
+    /**
+      * Supported DAG types:
+      * *   MANUAL: the DAG for a manually triggered workflow.
+      * *   SMOKE_TEST: the DAG for a smoke testing workflow.
+      * *   SUPPLY_DATA: the DAG for a data backfill instance.
+      * *   BUSINESS_PROCESS_DAG: the DAG for a one-time workflow.
+      * Supported DAG states:
+      * *   CREATED: The DAG is created.
+      * *   RUNNING: The DAG is running.
+      * *   FAILURE: The DAG fails to run.
+      * *   SUCCESS: The DAG successfully runs.
+      *
+      * @param request GetDagRequest
+      * @return GetDagResponse
+     */
     getDag(request: GetDagRequest): Promise<GetDagResponse>;
     getDataServiceApiWithOptions(request: GetDataServiceApiRequest, runtime: $Util.RuntimeOptions): Promise<GetDataServiceApiResponse>;
     getDataServiceApi(request: GetDataServiceApiRequest): Promise<GetDataServiceApiResponse>;
@@ -18168,7 +18330,20 @@ export default class Client extends OpenApi {
       * @return GetInstanceErrorRankResponse
      */
     getInstanceErrorRank(request: GetInstanceErrorRankRequest): Promise<GetInstanceErrorRankResponse>;
+    /**
+      * You may not obtain the instance logs that were generated more than seven days ago.
+      *
+      * @param request GetInstanceLogRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return GetInstanceLogResponse
+     */
     getInstanceLogWithOptions(request: GetInstanceLogRequest, runtime: $Util.RuntimeOptions): Promise<GetInstanceLogResponse>;
+    /**
+      * You may not obtain the instance logs that were generated more than seven days ago.
+      *
+      * @param request GetInstanceLogRequest
+      * @return GetInstanceLogResponse
+     */
     getInstanceLog(request: GetInstanceLogRequest): Promise<GetInstanceLogResponse>;
     /**
       * @deprecated
@@ -18208,7 +18383,20 @@ export default class Client extends OpenApi {
     getMetaCollectionDetail(request: GetMetaCollectionDetailRequest): Promise<GetMetaCollectionDetailResponse>;
     getMetaColumnLineageWithOptions(request: GetMetaColumnLineageRequest, runtime: $Util.RuntimeOptions): Promise<GetMetaColumnLineageResponse>;
     getMetaColumnLineage(request: GetMetaColumnLineageRequest): Promise<GetMetaColumnLineageResponse>;
+    /**
+      * You can call this operation to query only the basic metadata information about a MaxCompute or E-MapReduce (EMR) compute engine instance.
+      *
+      * @param request GetMetaDBInfoRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return GetMetaDBInfoResponse
+     */
     getMetaDBInfoWithOptions(request: GetMetaDBInfoRequest, runtime: $Util.RuntimeOptions): Promise<GetMetaDBInfoResponse>;
+    /**
+      * You can call this operation to query only the basic metadata information about a MaxCompute or E-MapReduce (EMR) compute engine instance.
+      *
+      * @param request GetMetaDBInfoRequest
+      * @return GetMetaDBInfoResponse
+     */
     getMetaDBInfo(request: GetMetaDBInfoRequest): Promise<GetMetaDBInfoResponse>;
     getMetaDBTableListWithOptions(request: GetMetaDBTableListRequest, runtime: $Util.RuntimeOptions): Promise<GetMetaDBTableListResponse>;
     getMetaDBTableList(request: GetMetaDBTableListRequest): Promise<GetMetaDBTableListResponse>;
@@ -18241,7 +18429,20 @@ export default class Client extends OpenApi {
     getMetaTableListByCategory(request: GetMetaTableListByCategoryRequest): Promise<GetMetaTableListByCategoryResponse>;
     getMetaTableOutputWithOptions(request: GetMetaTableOutputRequest, runtime: $Util.RuntimeOptions): Promise<GetMetaTableOutputResponse>;
     getMetaTableOutput(request: GetMetaTableOutputRequest): Promise<GetMetaTableOutputResponse>;
+    /**
+      * You can call this operation to query only the partitions of a metatable in a MaxCompute or E-MapReduce (EMR) compute engine instance.
+      *
+      * @param tmpReq GetMetaTablePartitionRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return GetMetaTablePartitionResponse
+     */
     getMetaTablePartitionWithOptions(tmpReq: GetMetaTablePartitionRequest, runtime: $Util.RuntimeOptions): Promise<GetMetaTablePartitionResponse>;
+    /**
+      * You can call this operation to query only the partitions of a metatable in a MaxCompute or E-MapReduce (EMR) compute engine instance.
+      *
+      * @param request GetMetaTablePartitionRequest
+      * @return GetMetaTablePartitionResponse
+     */
     getMetaTablePartition(request: GetMetaTablePartitionRequest): Promise<GetMetaTablePartitionResponse>;
     getMetaTableProducingTasksWithOptions(request: GetMetaTableProducingTasksRequest, runtime: $Util.RuntimeOptions): Promise<GetMetaTableProducingTasksResponse>;
     getMetaTableProducingTasks(request: GetMetaTableProducingTasksRequest): Promise<GetMetaTableProducingTasksResponse>;
@@ -18356,7 +18557,24 @@ export default class Client extends OpenApi {
     getTopic(request: GetTopicRequest): Promise<GetTopicResponse>;
     getTopicInfluenceWithOptions(request: GetTopicInfluenceRequest, runtime: $Util.RuntimeOptions): Promise<GetTopicInfluenceResponse>;
     getTopicInfluence(request: GetTopicInfluenceRequest): Promise<GetTopicInfluenceResponse>;
+    /**
+      * You can import self-managed data sources or data sources that are exported from other Dataworks workspaces to a specified DataWorks workspace.
+      * *   To import a self-managed data source to DataWorks, the data source type must be supported by DataWorks. For more information about the types of data sources supported by DataWorks, see [Supported data stores](~~181656~~).
+      * *   For more information about how to export data sources from DataWorks workspaces to on-premises devices, see [ExportDataSources](~~279570~~).
+      *
+      * @param request ImportDataSourcesRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return ImportDataSourcesResponse
+     */
     importDataSourcesWithOptions(request: ImportDataSourcesRequest, runtime: $Util.RuntimeOptions): Promise<ImportDataSourcesResponse>;
+    /**
+      * You can import self-managed data sources or data sources that are exported from other Dataworks workspaces to a specified DataWorks workspace.
+      * *   To import a self-managed data source to DataWorks, the data source type must be supported by DataWorks. For more information about the types of data sources supported by DataWorks, see [Supported data stores](~~181656~~).
+      * *   For more information about how to export data sources from DataWorks workspaces to on-premises devices, see [ExportDataSources](~~279570~~).
+      *
+      * @param request ImportDataSourcesRequest
+      * @return ImportDataSourcesResponse
+     */
     importDataSources(request: ImportDataSourcesRequest): Promise<ImportDataSourcesResponse>;
     listAlertMessagesWithOptions(request: ListAlertMessagesRequest, runtime: $Util.RuntimeOptions): Promise<ListAlertMessagesResponse>;
     listAlertMessages(request: ListAlertMessagesRequest): Promise<ListAlertMessagesResponse>;
@@ -18385,9 +18603,53 @@ export default class Client extends OpenApi {
       * @return ListConnectionsResponse
      */
     listConnections(request: ListConnectionsRequest): Promise<ListConnectionsResponse>;
+    /**
+      * DataWorks allows you to set the default global configuration for only the processing rules of DDL messages in sync solutions. After you configure the **processing rules of DDL messages** in sync solutions, the configuration is set as the default global configuration and applies to all real-time sync nodes. You can also modify the **processing rules of DDL messages** based on your business requirements. For more information, see [Sync solutions](~~199008~~).
+      *
+      * @param request ListDIProjectConfigRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return ListDIProjectConfigResponse
+     */
     listDIProjectConfigWithOptions(request: ListDIProjectConfigRequest, runtime: $Util.RuntimeOptions): Promise<ListDIProjectConfigResponse>;
+    /**
+      * DataWorks allows you to set the default global configuration for only the processing rules of DDL messages in sync solutions. After you configure the **processing rules of DDL messages** in sync solutions, the configuration is set as the default global configuration and applies to all real-time sync nodes. You can also modify the **processing rules of DDL messages** based on your business requirements. For more information, see [Sync solutions](~~199008~~).
+      *
+      * @param request ListDIProjectConfigRequest
+      * @return ListDIProjectConfigResponse
+     */
     listDIProjectConfig(request: ListDIProjectConfigRequest): Promise<ListDIProjectConfigResponse>;
+    /**
+      * Supported DAG types:
+      * *   MANUAL: the DAG for a manually triggered workflow.
+      * *   SMOKE_TEST: the DAG for a smoke testing workflow.
+      * *   SUPPLY_DATA: the DAG for a data backfill instance.
+      * *   BUSINESS_PROCESS_DAG: the DAG for a one-time workflow.
+      * Supported DAG states:
+      * *   CREATED: The DAG is created.
+      * *   RUNNING: The DAG is running.
+      * *   FAILURE: The DAG fails to run.
+      * *   SUCCESS: The DAG successfully runs.
+      *
+      * @param request ListDagsRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return ListDagsResponse
+     */
     listDagsWithOptions(request: ListDagsRequest, runtime: $Util.RuntimeOptions): Promise<ListDagsResponse>;
+    /**
+      * Supported DAG types:
+      * *   MANUAL: the DAG for a manually triggered workflow.
+      * *   SMOKE_TEST: the DAG for a smoke testing workflow.
+      * *   SUPPLY_DATA: the DAG for a data backfill instance.
+      * *   BUSINESS_PROCESS_DAG: the DAG for a one-time workflow.
+      * Supported DAG states:
+      * *   CREATED: The DAG is created.
+      * *   RUNNING: The DAG is running.
+      * *   FAILURE: The DAG fails to run.
+      * *   SUCCESS: The DAG successfully runs.
+      *
+      * @param request ListDagsRequest
+      * @return ListDagsResponse
+     */
     listDags(request: ListDagsRequest): Promise<ListDagsResponse>;
     listDataServiceApiAuthoritiesWithOptions(request: ListDataServiceApiAuthoritiesRequest, runtime: $Util.RuntimeOptions): Promise<ListDataServiceApiAuthoritiesResponse>;
     listDataServiceApiAuthorities(request: ListDataServiceApiAuthoritiesRequest): Promise<ListDataServiceApiAuthoritiesResponse>;
@@ -18433,7 +18695,20 @@ export default class Client extends OpenApi {
     listManualDagInstances(request: ListManualDagInstancesRequest): Promise<ListManualDagInstancesResponse>;
     listMetaCollectionEntitiesWithOptions(request: ListMetaCollectionEntitiesRequest, runtime: $Util.RuntimeOptions): Promise<ListMetaCollectionEntitiesResponse>;
     listMetaCollectionEntities(request: ListMetaCollectionEntitiesRequest): Promise<ListMetaCollectionEntitiesResponse>;
+    /**
+      * The type can be ALBUM or ALBUM_CATEGORY. ALBUM indicates data albums. ALBUM_CATEGORY indicates categories.
+      *
+      * @param request ListMetaCollectionsRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return ListMetaCollectionsResponse
+     */
     listMetaCollectionsWithOptions(request: ListMetaCollectionsRequest, runtime: $Util.RuntimeOptions): Promise<ListMetaCollectionsResponse>;
+    /**
+      * The type can be ALBUM or ALBUM_CATEGORY. ALBUM indicates data albums. ALBUM_CATEGORY indicates categories.
+      *
+      * @param request ListMetaCollectionsRequest
+      * @return ListMetaCollectionsResponse
+     */
     listMetaCollections(request: ListMetaCollectionsRequest): Promise<ListMetaCollectionsResponse>;
     listMetaDBWithOptions(request: ListMetaDBRequest, runtime: $Util.RuntimeOptions): Promise<ListMetaDBResponse>;
     listMetaDB(request: ListMetaDBRequest): Promise<ListMetaDBResponse>;
@@ -18479,7 +18754,20 @@ export default class Client extends OpenApi {
       * @return ListProgramTypeCountResponse
      */
     listProgramTypeCount(request: ListProgramTypeCountRequest): Promise<ListProgramTypeCountResponse>;
+    /**
+      * For example, an Alibaba Cloud account can assume the developer, O&M engineer, or workspace administrator role in a workspace. For more information, see [Manage members and roles](~~136941~~).
+      *
+      * @param request ListProjectIdsRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return ListProjectIdsResponse
+     */
     listProjectIdsWithOptions(request: ListProjectIdsRequest, runtime: $Util.RuntimeOptions): Promise<ListProjectIdsResponse>;
+    /**
+      * For example, an Alibaba Cloud account can assume the developer, O&M engineer, or workspace administrator role in a workspace. For more information, see [Manage members and roles](~~136941~~).
+      *
+      * @param request ListProjectIdsRequest
+      * @return ListProjectIdsResponse
+     */
     listProjectIds(request: ListProjectIdsRequest): Promise<ListProjectIdsResponse>;
     listProjectMembersWithOptions(request: ListProjectMembersRequest, runtime: $Util.RuntimeOptions): Promise<ListProjectMembersResponse>;
     listProjectMembers(request: ListProjectMembersRequest): Promise<ListProjectMembersResponse>;
@@ -18530,9 +18818,43 @@ export default class Client extends OpenApi {
     offlineNode(request: OfflineNodeRequest): Promise<OfflineNodeResponse>;
     publishDataServiceApiWithOptions(request: PublishDataServiceApiRequest, runtime: $Util.RuntimeOptions): Promise<PublishDataServiceApiResponse>;
     publishDataServiceApi(request: PublishDataServiceApiRequest): Promise<PublishDataServiceApiResponse>;
+    /**
+      * DataWorks allows you to call only the [CreateDISyncTask](~~278725~~) or [UpdateDISyncTask](~~289109~~) operation to create or update a batch synchronization node in Data Integration. To create or update a real-time synchronization node or a synchronization solution, you must first call the GenerateDISyncTaskConfigForCreating or GenerateDISyncTaskConfigForUpdating operation to generate the ID of an asynchronous thread and call the [QueryDISyncTaskConfigProcessResult](~~383465~~) operation to obtain the asynchronously generated parameters based on the ID. Then, you can call the CreateDISyncTask or UpdateDISyncTask operation and use the parameters as request parameters to create or update a real-time synchronization node or a synchronization solution.
+      * DataWorks allows you to create or update real-time synchronization nodes and synchronization solutions in Data Integration only in asynchronous mode.
+      *
+      * @param request QueryDISyncTaskConfigProcessResultRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return QueryDISyncTaskConfigProcessResultResponse
+     */
     queryDISyncTaskConfigProcessResultWithOptions(request: QueryDISyncTaskConfigProcessResultRequest, runtime: $Util.RuntimeOptions): Promise<QueryDISyncTaskConfigProcessResultResponse>;
+    /**
+      * DataWorks allows you to call only the [CreateDISyncTask](~~278725~~) or [UpdateDISyncTask](~~289109~~) operation to create or update a batch synchronization node in Data Integration. To create or update a real-time synchronization node or a synchronization solution, you must first call the GenerateDISyncTaskConfigForCreating or GenerateDISyncTaskConfigForUpdating operation to generate the ID of an asynchronous thread and call the [QueryDISyncTaskConfigProcessResult](~~383465~~) operation to obtain the asynchronously generated parameters based on the ID. Then, you can call the CreateDISyncTask or UpdateDISyncTask operation and use the parameters as request parameters to create or update a real-time synchronization node or a synchronization solution.
+      * DataWorks allows you to create or update real-time synchronization nodes and synchronization solutions in Data Integration only in asynchronous mode.
+      *
+      * @param request QueryDISyncTaskConfigProcessResultRequest
+      * @return QueryDISyncTaskConfigProcessResultResponse
+     */
     queryDISyncTaskConfigProcessResult(request: QueryDISyncTaskConfigProcessResultRequest): Promise<QueryDISyncTaskConfigProcessResultResponse>;
+    /**
+      * *   You must use FML statements to query information about the data modeling engine when you call this operation.
+      * *   The information about the data modeling engine can be queried by page, except for data layers, business processes, and data domains. You can add an offset to the end of an FML statement.
+      *     The num LIMIT num statement specifies the offset when the information about the data modeling engine is queried, and the number of pages to return each time. The offset value must be a multiple of the number of pages.
+      * *   A maximum of 1,000 entries can be returned each time you call the operation.
+      *
+      * @param request QueryPublicModelEngineRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return QueryPublicModelEngineResponse
+     */
     queryPublicModelEngineWithOptions(request: QueryPublicModelEngineRequest, runtime: $Util.RuntimeOptions): Promise<QueryPublicModelEngineResponse>;
+    /**
+      * *   You must use FML statements to query information about the data modeling engine when you call this operation.
+      * *   The information about the data modeling engine can be queried by page, except for data layers, business processes, and data domains. You can add an offset to the end of an FML statement.
+      *     The num LIMIT num statement specifies the offset when the information about the data modeling engine is queried, and the number of pages to return each time. The offset value must be a multiple of the number of pages.
+      * *   A maximum of 1,000 entries can be returned each time you call the operation.
+      *
+      * @param request QueryPublicModelEngineRequest
+      * @return QueryPublicModelEngineResponse
+     */
     queryPublicModelEngine(request: QueryPublicModelEngineRequest): Promise<QueryPublicModelEngineResponse>;
     removeProjectMemberFromRoleWithOptions(request: RemoveProjectMemberFromRoleRequest, runtime: $Util.RuntimeOptions): Promise<RemoveProjectMemberFromRoleResponse>;
     removeProjectMemberFromRole(request: RemoveProjectMemberFromRoleRequest): Promise<RemoveProjectMemberFromRoleResponse>;
@@ -18544,7 +18866,20 @@ export default class Client extends OpenApi {
     revokeColumnPermission(request: RevokeColumnPermissionRequest): Promise<RevokeColumnPermissionResponse>;
     revokeTablePermissionWithOptions(request: RevokeTablePermissionRequest, runtime: $Util.RuntimeOptions): Promise<RevokeTablePermissionResponse>;
     revokeTablePermission(request: RevokeTablePermissionRequest): Promise<RevokeTablePermissionResponse>;
+    /**
+      * For more information about data backfill, see [Backfill data](~~137937~~).
+      *
+      * @param request RunCycleDagNodesRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return RunCycleDagNodesResponse
+     */
     runCycleDagNodesWithOptions(request: RunCycleDagNodesRequest, runtime: $Util.RuntimeOptions): Promise<RunCycleDagNodesResponse>;
+    /**
+      * For more information about data backfill, see [Backfill data](~~137937~~).
+      *
+      * @param request RunCycleDagNodesRequest
+      * @return RunCycleDagNodesResponse
+     */
     runCycleDagNodes(request: RunCycleDagNodesRequest): Promise<RunCycleDagNodesResponse>;
     runManualDagNodesWithOptions(request: RunManualDagNodesRequest, runtime: $Util.RuntimeOptions): Promise<RunManualDagNodesResponse>;
     runManualDagNodes(request: RunManualDagNodesRequest): Promise<RunManualDagNodesResponse>;
@@ -18554,7 +18889,20 @@ export default class Client extends OpenApi {
     runTriggerNode(request: RunTriggerNodeRequest): Promise<RunTriggerNodeResponse>;
     scanSensitiveDataWithOptions(request: ScanSensitiveDataRequest, runtime: $Util.RuntimeOptions): Promise<ScanSensitiveDataResponse>;
     scanSensitiveData(request: ScanSensitiveDataRequest): Promise<ScanSensitiveDataResponse>;
+    /**
+      * You can call this operation to query only metatables in a MaxCompute or E-MapReduce (EMR) compute engine instance.
+      *
+      * @param request SearchMetaTablesRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return SearchMetaTablesResponse
+     */
     searchMetaTablesWithOptions(request: SearchMetaTablesRequest, runtime: $Util.RuntimeOptions): Promise<SearchMetaTablesResponse>;
+    /**
+      * You can call this operation to query only metatables in a MaxCompute or E-MapReduce (EMR) compute engine instance.
+      *
+      * @param request SearchMetaTablesRequest
+      * @return SearchMetaTablesResponse
+     */
     searchMetaTables(request: SearchMetaTablesRequest): Promise<SearchMetaTablesResponse>;
     /**
       * @deprecated
@@ -18631,7 +18979,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>;
@@ -18639,7 +19000,20 @@ export default class Client extends OpenApi {
     updateDataServiceApi(request: UpdateDataServiceApiRequest): Promise<UpdateDataServiceApiResponse>;
     updateDataSourceWithOptions(request: UpdateDataSourceRequest, runtime: $Util.RuntimeOptions): Promise<UpdateDataSourceResponse>;
     updateDataSource(request: UpdateDataSourceRequest): Promise<UpdateDataSourceResponse>;
+    /**
+      * When you debug or call this operation, you must specify new values for the specified parameters to ensure that the values are different from the original configurations of the file. For example, if the original value of a parameter is A, you must change the value of this parameter to B before you commit the node. If you set the parameter to A, an exception that indicates invalid data occurs.
+      *
+      * @param request UpdateFileRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return UpdateFileResponse
+     */
     updateFileWithOptions(request: UpdateFileRequest, runtime: $Util.RuntimeOptions): Promise<UpdateFileResponse>;
+    /**
+      * When you debug or call this operation, you must specify new values for the specified parameters to ensure that the values are different from the original configurations of the file. For example, if the original value of a parameter is A, you must change the value of this parameter to B before you commit the node. If you set the parameter to A, an exception that indicates invalid data occurs.
+      *
+      * @param request UpdateFileRequest
+      * @return UpdateFileResponse
+     */
     updateFile(request: UpdateFileRequest): Promise<UpdateFileResponse>;
     updateFolderWithOptions(request: UpdateFolderRequest, runtime: $Util.RuntimeOptions): Promise<UpdateFolderResponse>;
     updateFolder(request: UpdateFolderRequest): Promise<UpdateFolderResponse>;
@@ -18647,7 +19021,20 @@ export default class Client extends OpenApi {
     updateIDEEventResult(request: UpdateIDEEventResultRequest): Promise<UpdateIDEEventResultResponse>;
     updateMetaCategoryWithOptions(request: UpdateMetaCategoryRequest, runtime: $Util.RuntimeOptions): Promise<UpdateMetaCategoryResponse>;
     updateMetaCategory(request: UpdateMetaCategoryRequest): Promise<UpdateMetaCategoryResponse>;
+    /**
+      * Only the name and comment of a collection can be updated.
+      *
+      * @param request UpdateMetaCollectionRequest
+      * @param runtime runtime options for this request RuntimeOptions
+      * @return UpdateMetaCollectionResponse
+     */
     updateMetaCollectionWithOptions(request: UpdateMetaCollectionRequest, runtime: $Util.RuntimeOptions): Promise<UpdateMetaCollectionResponse>;
+    /**
+      * Only the name and comment of a collection can be updated.
+      *
+      * @param request UpdateMetaCollectionRequest
+      * @return UpdateMetaCollectionResponse
+     */
     updateMetaCollection(request: UpdateMetaCollectionRequest): Promise<UpdateMetaCollectionResponse>;
     updateMetaTableWithOptions(request: UpdateMetaTableRequest, runtime: $Util.RuntimeOptions): Promise<UpdateMetaTableResponse>;
     updateMetaTable(request: UpdateMetaTableRequest): Promise<UpdateMetaTableResponse>;