Menu
Amazon DynamoDB
Developer Guide (API Version 2012-08-10)

QueryFilter

In a Query operation, QueryFilter is a condition that evaluates the query results after the items are read and returns only the desired values.

This parameter does not support attributes of type List or Map.

Note

A QueryFilter is applied after the items have already been read; the process of filtering does not consume any additional read capacity units.

If you provide more than one condition in the QueryFilter map, then by default all of the conditions must evaluate to true. In other words, the conditions are ANDed together. (You can use the ConditionalOperator parameter to OR the conditions instead. If you do this, then at least one of the conditions must evaluate to true, rather than all of them.)

Note that QueryFilter does not allow key attributes. You cannot define a filter condition on a partition key or a sort key.

Each QueryFilter element consists of an attribute name to compare, along with the following:

  • AttributeValueList - One or more values to evaluate against the supplied attribute. The number of values in the list depends on the operator specified in ComparisonOperator.

    For type Number, value comparisons are numeric.

    String value comparisons for greater than, equals, or less than are based on UTF-8 binary encoding. For example, a is greater than A, and a is greater than B.

    For type Binary, DynamoDB treats each byte of the binary data as unsigned when it compares binary values.

    For information on specifying data types in JSON, see DynamoDB Low-Level API.

  • ComparisonOperator - A comparator for evaluating attributes. For example, equals, greater than, less than, etc.

    The following comparison operators are available:

    EQ | NE | LE | LT | GE | GT | NOT_NULL | NULL | CONTAINS | NOT_CONTAINS | BEGINS_WITH | IN | BETWEEN

Use FilterExpression Instead

Suppose you wanted to query the Music table, but apply a condition to the items before they were returned to you. You could use a Query request with an QueryFilter parameter, like this:

{
    TableName: "Music",
    KeyConditions: {
        "Artist": {
            ComparisonOperator: "EQ",
            AttributeValueList: [ "No One You Know" ]
        }
    },
    QueryFilter: {
        "Price": {
            ComparisonOperator: "GT",
            AttributeValueList: [ 1.00 ]
        }
    }
} 

But you could use a FilterExpression instead:

{
    TableName: "Music",
    KeyConditionExpression: "Artist = :a", 
    FilterExpression: "Price > :p", 
    ExpressionAttributeValues: {
        ":p": 1.00, 
        ":a": "No One You Know"
    }
}