Chris Johnson

+1 here Similar issue: ``` java.util.NoSuchElementException: None.get at scala.None$.get(Option.scala:313) at scala.None$.get(Option.scala:311) at awscala.dynamodbv2.DynamoDB$class.putItem(DynamoDB.scala:208) at awscala.dynamodbv2.DynamoDBClient.putItem(DynamoDB.scala:348) at awscala.dynamodbv2.DynamoDB$class.put(DynamoDB.scala:205) at awscala.dynamodbv2.DynamoDBClient.put(DynamoDB.scala:348) at awscala.dynamodbv2.Table.putItem(Table.scala:42) at awscala.dynamodbv2.Table.put(Table.scala:36) ``` This is triggered by a simple...

:+1:

Thanks for the update @tarcieri. Sounds promising.

:+1:

:+1: I like this for debugging. Nice suggestion.

Thank you both. This worked just as I wanted it to, allowing the same input to be used for both new and existing records. :+1: on merging this functionality!

Obviously, the data is available in the `value` of the option, but this seems like a common use case, no?

Wow, nice catch. I'll keep an eye out for this. Hopefully someone from AWS will take a look. @aws-dpt

👍 @manango ?

Same question. 👍