beyond_log_depth in migration logs

[darrenklein]

trafficstars

While running migrations against a production instance of DDB, I noticed a few "beyond_log_depth" "warnings" in the log line:

{"message":"2020-3-25 0:59:0 UTC [Ecto dynamo info] Ecto.Adapters.DynamoDB.Migration.poll_table: table","attributes":{"Ecto.Adapters.DynamoDB.Migration.poll_table-table":{"table_name":"organization","table":{"TableThroughputModeSummary":{"TableThroughputMode":"PAY_PER_REQUEST","LastUpdateToPayPerRequestDateTime":1544560696.543},"TableStatus":"ACTIVE","TableSizeBytes":10334,"TableName":"organization","TableId":"foo","TableArn":"arn:aws:dynamodb:us-east-1:foo:table/organization","ProvisionedThroughput":{"WriteCapacityUnits":0,"ReadCapacityUnits":0,"NumberOfDecreasesToday":0,"LastIncreaseDateTime":1539723196.249,"LastDecreaseDateTime":1539724712.593},"KeySchema":["beyond_log_depth"],"ItemCount":60,"GlobalSecondaryIndexes":["beyond_log_depth"],"CreationDateTime":1513293032.764,"BillingModeSummary":{"LastUpdateToPayPerRequestDateTime":1544560696.543,"BillingMode":"PAY_PER_REQUEST"},"AttributeDefinitions":["beyond_log_depth","beyond_log_depth"]}}}}

This isn't a critical issue, but would be nice to fix, if possible. The docs at https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_CreateTable.html should provide a little insight into the data structures, and how much further the log depth needs to extend.

[alhambra1]

We can also wonder whether we need it.

[darrenklein]

It's certainly low-priority - but do you mean that we might not need this specific issue addressed, or do mean that we might not need to be logging that level of detail?

[alhambra1]

The latter, pending investigation.