Get operation can throw when misused.

[mac01021]

This may or may not be a bug. I'll leave that up to the authors of the library.

I have the impression that get, query, and other operations are intended never to throw an exception (but instead return Left(someError). However, if you call get('myKey -> "myVal") when 'myKey is not the primary key, then exec will throw an exception from within the AWS dynamodb client.

In my case, the issue was that myKey was only the hashing key and I had neglected to provide a value for the sorting key. Clearly user error, but also still a thrown exception.

[regiskuckaertz]

You're right, this shouldn't happen.

[mac01021]

Out of curiosity, what's the reason for query returning List[Either[Error, Record]] rather than Either[Error, List[Record]]?

[regiskuckaertz]

See #174

We'll be working out a refactor of that soon.

[regiskuckaertz]

Technically, the semantics of List[Either[]] is more accurate since errors can occur at the record level. We don't want the whole result to fail if only one record fail, though we don't want to lose that information either. So, I'm not sure Either[List[]] is the right choice here. We need a ScanamoGetResult[A].