Recent AWS Customer Success Stories & Videos

More AWS Customer Success Stories...

« Backup and Restore ElastiCache Redis Clusters | Main | AWS Week in Review - April 21, 2014 »


Feed You can follow this conversation by subscribing to the comment feed for this post.

Daniel Chick

What sort of affect does the QueryFilter have on performance/response time?

Also - is the amount of read capacity consumed the same as if the filter hadn't been applied? I assume this is the case but you don't actually say clearly!

Greg Holland

Awesome! Loving how quickly you guys are adding features to Dynamo.

I have the same question as Daniel, what is the performance hit on applying filters, and is there an additional cost?

Dave Lang

Hi Daniel,

Thanks for the questions. You shouldn't see much of a change in performance. If you are filtering out a lot of items then you will transfer less data between your app and DynamoDB, so you may see some improvement in throughput and response times. If you are transferring data out of the AWS Region in which your DynamoDB table resides (e.g. a mobile app accessing DynamoDB directly), you may also see some reduction in data transfer costs.

Yes, the read capacity consumed will be the same as if there was no filter.

Have fun trying out these new features. We'd love to hear how they work out for you!

Dave Lang
DynamoDB Team


What are the exmaple usages of "conditional update" in PutItem. I think, we can use only NE operator for PutItem API.
Am I missing something here ?


Can i reduce the amount of secondary indexes by pulling via hashkey and filtering it using queryfilter?

Steve Jones

I'm searching for documentation/examples on how to use the QueryFilter in Java - can you provide a link with examples. The latest Java SDK (1.7.1) does not seem to contain QueryFilter?

Suraj P

A support for cpath or pattern matching would be awesome

Greg Holland

@Aloncarmel, I assume you could do that although if you have a huge amount of records you are going to have to pay to read every single one of them, then possibly cop a small performance hit to filter them. If your secondary index can get the results down to a much smaller number, it's going to cost you less and most probably be quicker.


It would be good if it was clearly explained if there is a downside to using query filters.

On the surface it appears this will allow us to use fewer or no secondary indexes. Is this correct?

What is the pros and cons of using query filtering versus secondary indexes?


The comments to this entry are closed.

Featured Events

The AWS Report

Brought to You By

Jeff Barr (@jeffbarr):

Jinesh Varia (@jinman):

Email Subscription

Enter your email address:

Delivered by FeedBurner

April 2014

Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30