create_matching_workflow
¶
create_matching_workflow(
workflow_name: EntityName,
input_source_config: InputSourceConfig,
output_source_config: OutputSourceConfig,
resolution_techniques: ResolutionTechniques,
role_arn: str,
*,
config_overrides: Optional[EntityResolutionClientConfig] = None,
description: Optional[Description] = None,
incremental_run_config: Optional[IncrementalRunConfig] = None,
tags: Optional[TagMap] = None,
) -> CreateMatchingWorkflowOutput
Creates a matching workflow that defines the configuration for a data processing job. The workflow name must be unique. To modify an existing workflow, use UpdateMatchingWorkflow.
For workflows where resolutionType is PROVIDER, incremental processing is not supported.
Parameters:
-
workflow_name(EntityName) –The name of the workflow. There can't be multiple
MatchingWorkflowswith the same name. -
description(Optional[Description], default:None) –A description of the workflow.
-
input_source_config(InputSourceConfig) –A list of
InputSourceobjects, which have the fieldsInputSourceARNandSchemaName. -
output_source_config(OutputSourceConfig) –A list of
OutputSourceobjects, each of which contains fieldsoutputS3Path,applyNormalization,KMSArn, andoutput. -
resolution_techniques(ResolutionTechniques) –An object which defines the
resolutionTypeand theruleBasedProperties. -
incremental_run_config(Optional[IncrementalRunConfig], default:None) –Optional. An object that defines the incremental run type. This object contains only the
incrementalRunTypefield, which appears as "Automatic" in the console.For workflows where
resolutionTypeisPROVIDER, incremental processing is not supported. -
role_arn(str) –The Amazon Resource Name (ARN) of the IAM role. Entity Resolution assumes this role to create resources on your behalf as part of workflow execution.
-
tags(Optional[TagMap], default:None) –The tags used to organize, track, or control access for this resource.
Raises:
-
AccessDeniedException–You do not have sufficient access to perform this action.
-
ConflictException–The request couldn't be processed because of conflict in the current state of the resource. Example: Workflow already exists, Schema already exists, Workflow is currently running, etc.
-
ExceedsLimitException–The request was rejected because it attempted to create resources beyond the current Entity Resolution account limits. The error message describes the limit exceeded.
-
InternalServerException–This exception occurs when there is an internal failure in the Entity Resolution service.
-
ThrottlingException–The request was denied due to request throttling.
-
ValidationException–The input fails to satisfy the constraints specified by Entity Resolution.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_entityresolution/_services/entity_resolution.py
551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 | |