1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
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.
con risposta 2 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
Did the shared solution work for you?