1 Answer
- Newest
- Most votes
- Most comments
1
This should work for you. The order of the rule ids in the Mapping Rules of any AWS DMS tasks does not influence the priority unless you use "load-order" in your mapping rules.
Since its only 1 table that you plan to explicitly include, you can try "explicit" as the "rule-action" as well. Something like below:
{ "rules": [ { "rule-type": "selection", "rule-id": "1", "rule-name": "1", "object-locator": { "schema-name": "NewCust", "table-name": "Customer" }, "rule-action": "explicit" } ] }
I would say, go ahead and test both out. Either or both should work.
answered 2 years ago
Relevant content
- asked 6 months ago
- asked 2 years ago
- asked 4 months ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 6 months ago
Did the shared solution work for you?