Upgrading to Cumulus 1.9.0
Cumulus 1.9 uses versioned collections to support granules from different collections and verison numbers. These granules usually come from PDRs where objects are defined with a DATA_VERSION and DATA_TYPE The associated collections should reflect the same version and dataType. CMR would also need to use the same dataType. If a dataType is not provided, Cumulus will use the collection name.
Collections are stored in a collections folder in S3 using this convention:
A migration exist to migrate existing collections to be versioned.
Cumulus 1.7 creates a lambda function for the migration. The lambda function is named
You have to invoke this lambda function at the end of your deployment to copy your records from ElasticSearch to DynamoDB. This is possible in three ways:
- Use cumulus-api command line utility:
$ ./node_modules/.bin/cumulus-api migrate --stack <your-cloudformation-stack-name>
- Invoke the lambda function directly with AWS CLI:
$ aws lambda invoke --function-name <your-cloudformation-stack-name>-executeMigrations
- Invoke the lambda function from the AWS website:
- go to the lambda service
- find the
- click on