ecto_adapters_dynamodb
ecto_adapters_dynamodb copied to clipboard
DynamoDB adapter for Elixir's Ecto Database layer.
Noticed the following warning when publishing a new release to Hex - not critical, but couldn't hurt to sort it out. ``` warning: ExDoc.Markdown.Earmark (warning) lib/ecto_adapters_dynamodb/query.ex:486 Illegal attributes ["[indexed_fields_list]", "primary,"]...
Until now, we've just been logging unprocessed items - it's time to get around to handling them appropriately - https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_BatchWriteItem.html https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_BatchGetItem.html
While investigating something else, I noticed that none of our test cases ever end up recursively calling the `Query` module's `fetch_recursive` private method - it would probably be a good...
When i attempt to create schema_migrations table by following command ` mix ecto.migrate -r RepoDynamo -n 0` it always raises ``` ** (ExAws.Error) ExAws Request Error! {:error, {"ResourceNotFoundException", "Requested resource...
In a query where a `==` operator is used on a primary key, a filter will be applied as expected - for example, the query ``` from(p in Person, where:...
A query with a `not` filter condition will fail to account for that condition. For example: ``` from(f in Foo, where: f.bar == "1234" and not is_nil(f.deleted_at)) |> Locus.Repo.all() ```...
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...
As of the initial alpha release with Ecto 3 support, 624bffb, we do not support `checkout/3` - `checkout/3` is a `@callback` that was implemented in Ecto 3 for `Ecto.Adapter`, but...
As of the initial alpha release with Ecto 3 support, 624bffb, we have limited support for `lock_for_migrations/4` - `lock_for_migrations/4` is a `@callback` that was implemented in Ecto 3 for `Ecto.Adapter.Migration`,...
As of the initial alpha release with Ecto 3 support, 624bffb075bbca6119b2bc3990750314c7cce851, we do not support `stream/5` - `stream/5` is a `@callback` that was implemented in Ecto 3 for `Ecto.Adapter.Queryable`, but...