Update to use local-dynamo, start local-dynamo from setUp

[chaosgame]

Hello @xiao,

Please review the following commits I made in branch 'nathan-AttributeValueList'.

a9499a9 (2015-07-23 17:04:42 -0700)
Update to use local-dynamo, start local-dynamo from setUp

7b973b5 (2015-07-23 16:37:35 -0700)
Migrate all uses of AttribueValueList/ComparisonOperator to ConditionBuilder

R=@xiao

Test plan: 'New unit test, old unit tests'

[chaosgame]

Now that we have local-dynamo and the test code runs on it's own, it would be nice to see if we could set up travis-ci integration for the repo.

[xiao]

conditions -> filters?

[xiao]

First pass done.

A high-level question -- can we consolidate ConditionBuilder and FilterBuilder into one builder, and maybe call it ConditionBuilder? They are essentially all conditions and they produce the same format in DynamoDB API, for KeyConditions, QueryFilter and ScanFilter.

[chaosgame]

ConditionBuilder and FilterBuilder don't produce the same format in DynamoDB yet, but you are correct -- that is the plan (see my comment above about changes in behavior).

[xiao]

I still think we should consolidate them in this PR, so we don't introduce a new API (FilterBuilder) and change it later.

Here is a proposal that I think would work. Let me know what you think about it.

• Keep the current two APIs in ConditionBuilder.
• Add the new APIs you added into FilterBuilder into ConditionBuilder.
• Use the new ConditionBuilder to generate values for all these fields (DynamoDB API), Expected, KeyConditions, QueryFilter and ScanFilter.
• Stop using Value + Exist, and use AttributeValueList + ComparisonOperator for Expected. This is hidden from the user of Dynamite anyway.
• I really like your idea to keep the APIs in QueryBuilder unchanged.

[chaosgame]

Alright @xiao, changes have been made. PTAL.

[xiao]

LGTM!

Beautiful piece.