1. Prepare the configuration file (in JSON format) with the identified source and sink details. For details, see Source Configuration Templates and Sink Configuration Templates.

   Note:

   If the items in your DynamoDB JSON File in AWS S3 contain TTL attribute, to optionally import the TTL values, specify the attribute in the ttlAttributeName configuration parameter of the source configuration template and set the includeTTL configuration parameter to true in the sink configuration template. For more details, see Migrating TTL Metadata for Table Rows.
   To specify a user-defined schema file in the sink configuration template, set the defaultSchema to FALSE and specify the schemaPath as a file containing your DDL statement. For details, see Mapping of DynamoDB types to Oracle NoSQL types .

   Note:

   If the Dynamo DB table has a data type that is not supported in NoSQL, the migration fails.
   A sample user-defined schema file is shown below.

   CREATE TABLE IF NOT EXISTS sampledynDBImp (AccountId INTEGER,document JSON, 
   PRIMARY KEY(SHARD(AccountId)));

   The schema file is used to create the DynamoDB table as fixed columns at the sink as part of the migration. As long as the primary key data is provided, the input JSON record will be inserted, otherwise it throws an error.

   Note:

   • If the input data does not contain a value for a particular column(other than the primary key) then the column default value will be used. The default value should be part of the column definition while creating the table. For example id INTEGER not null default 0. If the column does not have a default definition then SQL NULL is inserted if no values are provided for the column.
   • If you are modeling DynamoDB table as a JSON document, ensure that you use AggregateFields transform in order to aggregate non-primary key data into a JSON column. For details, see aggregateFields.

   {
     "source" : {
       "type" : "aws_s3",
       "format" : "dynamodb_json",
       "s3URL" : "<https://<bucket-name>.<s3_endpoint>/export_path>",
       "credentials" : "</path/to/aws/credentials/file>",
       "credentialsProfile" : "default"
     },
     "sink" : {
       "type" : "nosqldb",
       "storeName" : "kvstore",
       "helperHosts" : ["phoenix126166:5000"],
       "table" : "sampledynDBImp",
       "includeTTL" : false,
       "schemaInfo" : {
         "schemaPath" : "<full path of the schema file with the DDL statement>"
       },
       "overwrite" : true,
       "requestTimeoutMs" : 5000
     },
     "transforms" : {
       "aggregateFields" : {
         "fieldName" : "document",
         "skipFields" : ["AccountId"]
       }
     },
     "abortOnError" : true,
     "migratorVersion" : "1.7.0"
   }

2. Open the command prompt and navigate to the directory where you extracted the NoSQL Database Migrator utility.
3. Run the runMigrator command by passing the configuration file. Use --config or -c option.

   [~/nosqlMigrator]$./runMigrator 
   --config <complete/path/to/the/JSON/config/file>

4. The utility proceeds with the data migration, as shown below.

   
   creating source from given configuration:
   source creation completed
   creating sink from given configuration:
   sink creation completed
   creating migrator pipeline
   [nosqldb sink] : start loading DDLs
   [nosqldb sink] : executing DDL: CREATE TABLE IF NOT EXISTS sampledynDBImp (AccountId INTEGER, document JSON, PRIMARY KEY(SHARD(AccountId)))
   [nosqldb sink] : completed loading DDLs
   migration started
   Start writing data to OnDB Sink
   executing for source:azkzkyynnq7w7j7yqbao5377he
   executing for source:jrnmvjofnu3bzlwql4cpyasuma
   executing for source:kdieseqlwa72xlaenwgo5vb7tq
   executing for source:wp776cslq46nhm5snsi23v4j3a
   [INFO] [DDB S3 source] : start parsing JSON records from object: AWSDynamoDB/01754372757879-92f376b3/data/azkzkyynnq7w7j7yqbao5377he.json.gz
   [INFO] [DDB S3 source] : start parsing JSON records from object: AWSDynamoDB/01754372757879-92f376b3/data/jrnmvjofnu3bzlwql4cpyasuma.json.gz
   [INFO] [DDB S3 source] : start parsing JSON records from object: AWSDynamoDB/01754372757879-92f376b3/data/kdieseqlwa72xlaenwgo5vb7tq.json.gz
   [INFO] [DDB S3 source] : start parsing JSON records from object: AWSDynamoDB/01754372757879-92f376b3/data/wp776cslq46nhm5snsi23v4j3a.json.gz
   [INFO] Writing data to OnDB Sink completed.
   [INFO] migration completed.
   Records provided by source=2, Records written to sink=2, Records failed=0,Records skipped=0.
   Elapsed time: 0min 0sec 747ms
   Migration completed.

 java -jar lib/sql.jar -helper-hosts localhost:5000 -store kvstore

{"AccountId":102,"document":{"Address":{"City":"Wales","DoorNum":1024,"Street":"32 main","Zip":560014},"Age":48,"FavColors":["Blue"],"FavNumbers":[10],"FirstName":"John","LastName":"White","Phones":[["222-222"]],"PremierCustomer":false}}
{"AccountId":101,"document":{"Address":{"City":"London","DoorNum":201,"Street":"21 main","Zip":570004},"Age":22,"FavColors":["Red","Green"],"FavNumbers":[10],"FirstName":"Fred","LastName":"Smith","Phones":[["555-222","123-567"]],"PremierCustomer":false}}