-- Hoogle documentation, generated by Haddock
-- See Hoogle, http://www.haskell.org/hoogle/


-- | Amazon DynamoDB SDK.
--   
--   The types from this library are intended to be used with
--   <a>amazonka</a>, which provides mechanisms for specifying AuthN/AuthZ
--   information, sending requests, and receiving responses.
--   
--   Lenses are used for constructing and manipulating types, due to the
--   depth of nesting of AWS types and transparency regarding
--   de/serialisation into more palatable Haskell values. The provided
--   lenses should be compatible with any of the major lens libraries such
--   as <a>lens</a> or <a>lens-family-core</a>.
--   
--   See <a>Network.AWS.DynamoDB</a> or <a>the AWS documentation</a> to get
--   started.
@package amazonka-dynamodb
@version 1.4.5


module Network.AWS.DynamoDB.Types

-- | API version <tt>2012-08-10</tt> of the Amazon DynamoDB SDK
--   configuration.
dynamoDB :: Service

-- | Your request rate is too high. The AWS SDKs for DynamoDB automatically
--   retry requests that receive this exception. Your request is eventually
--   successful, unless your retry queue is too large to finish. Reduce the
--   frequency of requests and use exponential backoff. For more
--   information, go to <a>Error Retries and Exponential Backoff</a> in the
--   <i>Amazon DynamoDB Developer Guide</i> .
_ProvisionedThroughputExceededException :: AsError a => Getting (First ServiceError) a ServiceError

-- | A condition specified in the operation could not be evaluated.
_ConditionalCheckFailedException :: AsError a => Getting (First ServiceError) a ServiceError

-- | An item collection is too large. This exception is only returned for
--   tables that have one or more local secondary indexes.
_ItemCollectionSizeLimitExceededException :: AsError a => Getting (First ServiceError) a ServiceError

-- | An error occurred on the server side.
_InternalServerError :: AsError a => Getting (First ServiceError) a ServiceError

-- | The operation tried to access a nonexistent table or index. The
--   resource might not be specified correctly, or its status might not be
--   <tt>ACTIVE</tt> .
_ResourceNotFoundException :: AsError a => Getting (First ServiceError) a ServiceError

-- | The number of concurrent table requests (cumulative number of tables
--   in the <tt>CREATING</tt> , <tt>DELETING</tt> or <tt>UPDATING</tt>
--   state) exceeds the maximum allowed of 10.
--   
--   Also, for tables with secondary indexes, only one of those tables can
--   be in the <tt>CREATING</tt> state at any point in time. Do not attempt
--   to create more than one such table simultaneously.
--   
--   The total limit of tables in the <tt>ACTIVE</tt> state is 250.
_LimitExceededException :: AsError a => Getting (First ServiceError) a ServiceError

-- | The operation conflicts with the resource's availability. For example,
--   you attempted to recreate an existing table, or tried to delete a
--   table currently in the <tt>CREATING</tt> state.
_ResourceInUseException :: AsError a => Getting (First ServiceError) a ServiceError
data AttributeAction
Add :: AttributeAction
Delete :: AttributeAction
Put :: AttributeAction
data ComparisonOperator
BeginsWith :: ComparisonOperator
Between :: ComparisonOperator
Contains :: ComparisonOperator
EQ' :: ComparisonOperator
GE :: ComparisonOperator
GT' :: ComparisonOperator
IN :: ComparisonOperator
LE :: ComparisonOperator
LT' :: ComparisonOperator
NE :: ComparisonOperator
NotContains :: ComparisonOperator
NotNull :: ComparisonOperator
Null :: ComparisonOperator
data ConditionalOperator
And :: ConditionalOperator
OR :: ConditionalOperator
data IndexStatus
ISActive :: IndexStatus
ISCreating :: IndexStatus
ISDeleting :: IndexStatus
ISUpdating :: IndexStatus
data KeyType
Hash :: KeyType
Range :: KeyType
data ProjectionType
All :: ProjectionType
Include :: ProjectionType
KeysOnly :: ProjectionType

-- | Determines the level of detail about provisioned throughput
--   consumption that is returned in the response:
--   
--   <ul>
--   <li><i>INDEXES</i> - The response includes the aggregate
--   <i>ConsumedCapacity</i> for the operation, together with
--   <i>ConsumedCapacity</i> for each table and secondary index that was
--   accessed.</li>
--   </ul>
--   
--   Note that some operations, such as <i>GetItem</i> and
--   <i>BatchGetItem</i> , do not access any indexes at all. In these
--   cases, specifying <i>INDEXES</i> will only return
--   <i>ConsumedCapacity</i> information for table(s).
--   
--   <ul>
--   <li><i>TOTAL</i> - The response includes only the aggregate
--   <i>ConsumedCapacity</i> for the operation.</li>
--   <li><i>NONE</i> - No <i>ConsumedCapacity</i> details are included in
--   the response.</li>
--   </ul>
data ReturnConsumedCapacity
RCCIndexes :: ReturnConsumedCapacity
RCCNone :: ReturnConsumedCapacity
RCCTotal :: ReturnConsumedCapacity
data ReturnItemCollectionMetrics
RICMNone :: ReturnItemCollectionMetrics
RICMSize :: ReturnItemCollectionMetrics
data ReturnValue
AllNew :: ReturnValue
AllOld :: ReturnValue
None :: ReturnValue
UpdatedNew :: ReturnValue
UpdatedOld :: ReturnValue
data ScalarAttributeType
B :: ScalarAttributeType
N :: ScalarAttributeType
S :: ScalarAttributeType
data Select
AllAttributes :: Select
AllProjectedAttributes :: Select
Count :: Select
SpecificAttributes :: Select
data StreamViewType
SVTKeysOnly :: StreamViewType
SVTNewAndOldImages :: StreamViewType
SVTNewImage :: StreamViewType
SVTOldImage :: StreamViewType
data TableStatus
Active :: TableStatus
Creating :: TableStatus
Deleting :: TableStatus
Updating :: TableStatus

-- | Represents an attribute for describing the key schema for the table
--   and indexes.
--   
--   <i>See:</i> <a>attributeDefinition</a> smart constructor.
data AttributeDefinition

-- | Creates a value of <a>AttributeDefinition</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>adAttributeName</a> - A name for the attribute.</li>
--   <li><a>adAttributeType</a> - The data type for the attribute, where: *
--   <tt>S</tt> - the attribute is of type String * <tt>N</tt> - the
--   attribute is of type Number * <tt>B</tt> - the attribute is of type
--   Binary</li>
--   </ul>
attributeDefinition :: Text -> ScalarAttributeType -> AttributeDefinition

-- | A name for the attribute.
adAttributeName :: Lens' AttributeDefinition Text

-- | The data type for the attribute, where: * <tt>S</tt> - the attribute
--   is of type String * <tt>N</tt> - the attribute is of type Number *
--   <tt>B</tt> - the attribute is of type Binary
adAttributeType :: Lens' AttributeDefinition ScalarAttributeType

-- | Represents the data for an attribute. You can set one, and only one,
--   of the elements.
--   
--   Each attribute in an item is a name-value pair. An attribute can be
--   single-valued or multi-valued set. For example, a book item can have
--   title and authors attributes. Each book has one title but can have
--   many authors. The multi-valued attribute is a set; duplicate values
--   are not allowed.
--   
--   <i>See:</i> <a>attributeValue</a> smart constructor.
data AttributeValue

-- | Creates a value of <a>AttributeValue</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>avL</a> - A List of attribute values.</li>
--   <li><a>avNS</a> - A Number Set data type.</li>
--   <li><a>avM</a> - A Map of attribute values.</li>
--   <li><a>avNULL</a> - A Null data type.</li>
--   <li><a>avN</a> - A Number data type.</li>
--   <li><a>avBS</a> - A Binary Set data type.</li>
--   <li><a>avB</a> - A Binary data type.-- <i>Note:</i> This <tt>Lens</tt>
--   automatically encodes and decodes Base64 data. The underlying
--   isomorphism will encode to Base64 representation during serialisation,
--   and decode from Base64 representation during deserialisation. This
--   <tt>Lens</tt> accepts and returns only raw unencoded data.</li>
--   <li><a>avSS</a> - A String Set data type.</li>
--   <li><a>avS</a> - A String data type.</li>
--   <li><a>avBOOL</a> - A Boolean data type.</li>
--   </ul>
attributeValue :: AttributeValue

-- | A List of attribute values.
avL :: Lens' AttributeValue [AttributeValue]

-- | A Number Set data type.
avNS :: Lens' AttributeValue [Text]

-- | A Map of attribute values.
avM :: Lens' AttributeValue (HashMap Text AttributeValue)

-- | A Null data type.
avNULL :: Lens' AttributeValue (Maybe Bool)

-- | A Number data type.
avN :: Lens' AttributeValue (Maybe Text)

-- | A Binary Set data type.
avBS :: Lens' AttributeValue [ByteString]

-- | A Binary data type.-- <i>Note:</i> This <tt>Lens</tt> automatically
--   encodes and decodes Base64 data. The underlying isomorphism will
--   encode to Base64 representation during serialisation, and decode from
--   Base64 representation during deserialisation. This <tt>Lens</tt>
--   accepts and returns only raw unencoded data.
avB :: Lens' AttributeValue (Maybe ByteString)

-- | A String Set data type.
avSS :: Lens' AttributeValue [Text]

-- | A String data type.
avS :: Lens' AttributeValue (Maybe Text)

-- | A Boolean data type.
avBOOL :: Lens' AttributeValue (Maybe Bool)

-- | For the <i>UpdateItem</i> operation, represents the attributes to be
--   modified, the action to perform on each, and the new value for each.
--   
--   Attribute values cannot be null; string and binary type attributes
--   must have lengths greater than zero; and set type attributes must not
--   be empty. Requests with empty values will be rejected with a
--   <i>ValidationException</i> exception.
--   
--   <i>See:</i> <a>attributeValueUpdate</a> smart constructor.
data AttributeValueUpdate

-- | Creates a value of <a>AttributeValueUpdate</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>avuValue</a> - Undocumented member.</li>
--   <li><a>avuAction</a> - Specifies how to perform the update. Valid
--   values are <tt>PUT</tt> (default), <tt>DELETE</tt> , and <tt>ADD</tt>
--   . The behavior depends on whether the specified primary key already
--   exists in the table. <b>If an item with the specified <i>Key</i> is
--   found in the table:</b> * <tt>PUT</tt> - Adds the specified attribute
--   to the item. If the attribute already exists, it is replaced by the
--   new value. * <tt>DELETE</tt> - If no value is specified, the attribute
--   and its value are removed from the item. The data type of the
--   specified value must match the existing value's data type. If a
--   <i>set</i> of values is specified, then those values are subtracted
--   from the old set. For example, if the attribute value was the set
--   <tt>[a,b,c]</tt> and the <i>DELETE</i> action specified <tt>[a,c]</tt>
--   , then the final attribute value would be <tt>[b]</tt> . Specifying an
--   empty set is an error. * <tt>ADD</tt> - If the attribute does not
--   already exist, then the attribute and its values are added to the
--   item. If the attribute does exist, then the behavior of <tt>ADD</tt>
--   depends on the data type of the attribute: * If the existing attribute
--   is a number, and if <i>Value</i> is also a number, then the
--   <i>Value</i> is mathematically added to the existing attribute. If
--   <i>Value</i> is a negative number, then it is subtracted from the
--   existing attribute. * If the existing data type is a set, and if the
--   <i>Value</i> is also a set, then the <i>Value</i> is added to the
--   existing set. (This is a <i>set</i> operation, not mathematical
--   addition.) For example, if the attribute value was the set
--   <tt>[1,2]</tt> , and the <tt>ADD</tt> action specified <tt>[3]</tt> ,
--   then the final attribute value would be <tt>[1,2,3]</tt> . An error
--   occurs if an Add action is specified for a set attribute and the
--   attribute type specified does not match the existing set type. Both
--   sets must have the same primitive data type. For example, if the
--   existing data type is a set of strings, the <i>Value</i> must also be
--   a set of strings. The same holds true for number sets and binary sets.
--   This action is only valid for an existing attribute whose data type is
--   number or is a set. Do not use <tt>ADD</tt> for any other data types.
--   <b>If no item with the specified <i>Key</i> is found:</b> *
--   <tt>PUT</tt> - DynamoDB creates a new item with the specified primary
--   key, and then adds the attribute. * <tt>DELETE</tt> - Nothing happens;
--   there is no attribute to delete. * <tt>ADD</tt> - DynamoDB creates an
--   item with the supplied primary key and number (or set of numbers) for
--   the attribute value. The only data types allowed are number and number
--   set; no other data types can be specified.</li>
--   </ul>
attributeValueUpdate :: AttributeValueUpdate

-- | Undocumented member.
avuValue :: Lens' AttributeValueUpdate (Maybe AttributeValue)

-- | Specifies how to perform the update. Valid values are <tt>PUT</tt>
--   (default), <tt>DELETE</tt> , and <tt>ADD</tt> . The behavior depends
--   on whether the specified primary key already exists in the table.
--   <b>If an item with the specified <i>Key</i> is found in the table:</b>
--   * <tt>PUT</tt> - Adds the specified attribute to the item. If the
--   attribute already exists, it is replaced by the new value. *
--   <tt>DELETE</tt> - If no value is specified, the attribute and its
--   value are removed from the item. The data type of the specified value
--   must match the existing value's data type. If a <i>set</i> of values
--   is specified, then those values are subtracted from the old set. For
--   example, if the attribute value was the set <tt>[a,b,c]</tt> and the
--   <i>DELETE</i> action specified <tt>[a,c]</tt> , then the final
--   attribute value would be <tt>[b]</tt> . Specifying an empty set is an
--   error. * <tt>ADD</tt> - If the attribute does not already exist, then
--   the attribute and its values are added to the item. If the attribute
--   does exist, then the behavior of <tt>ADD</tt> depends on the data type
--   of the attribute: * If the existing attribute is a number, and if
--   <i>Value</i> is also a number, then the <i>Value</i> is mathematically
--   added to the existing attribute. If <i>Value</i> is a negative number,
--   then it is subtracted from the existing attribute. * If the existing
--   data type is a set, and if the <i>Value</i> is also a set, then the
--   <i>Value</i> is added to the existing set. (This is a <i>set</i>
--   operation, not mathematical addition.) For example, if the attribute
--   value was the set <tt>[1,2]</tt> , and the <tt>ADD</tt> action
--   specified <tt>[3]</tt> , then the final attribute value would be
--   <tt>[1,2,3]</tt> . An error occurs if an Add action is specified for a
--   set attribute and the attribute type specified does not match the
--   existing set type. Both sets must have the same primitive data type.
--   For example, if the existing data type is a set of strings, the
--   <i>Value</i> must also be a set of strings. The same holds true for
--   number sets and binary sets. This action is only valid for an existing
--   attribute whose data type is number or is a set. Do not use
--   <tt>ADD</tt> for any other data types. <b>If no item with the
--   specified <i>Key</i> is found:</b> * <tt>PUT</tt> - DynamoDB creates a
--   new item with the specified primary key, and then adds the attribute.
--   * <tt>DELETE</tt> - Nothing happens; there is no attribute to delete.
--   * <tt>ADD</tt> - DynamoDB creates an item with the supplied primary
--   key and number (or set of numbers) for the attribute value. The only
--   data types allowed are number and number set; no other data types can
--   be specified.
avuAction :: Lens' AttributeValueUpdate (Maybe AttributeAction)

-- | Represents the amount of provisioned throughput capacity consumed on a
--   table or an index.
--   
--   <i>See:</i> <a>capacity</a> smart constructor.
data Capacity

-- | Creates a value of <a>Capacity</a> with the minimum fields required to
--   make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>cCapacityUnits</a> - The total number of capacity units
--   consumed on a table or an index.</li>
--   </ul>
capacity :: Capacity

-- | The total number of capacity units consumed on a table or an index.
cCapacityUnits :: Lens' Capacity (Maybe Double)

-- | Represents the selection criteria for a <i>Query</i> or <i>Scan</i>
--   operation:
--   
--   <ul>
--   <li>For a <i>Query</i> operation, <i>Condition</i> is used for
--   specifying the <i>KeyConditions</i> to use when querying a table or an
--   index. For <i>KeyConditions</i> , only the following comparison
--   operators are supported:</li>
--   </ul>
--   
--   <pre>
--   EQ | LE | LT | GE | GT | BEGINS_WITH | BETWEEN
--   </pre>
--   
--   <i>Condition</i> is also used in a <i>QueryFilter</i> , which
--   evaluates the query results and returns only the desired values.
--   
--   <ul>
--   <li>For a <i>Scan</i> operation, <i>Condition</i> is used in a
--   <i>ScanFilter</i> , which evaluates the scan results and returns only
--   the desired values.</li>
--   </ul>
--   
--   <i>See:</i> <a>condition</a> smart constructor.
data Condition

-- | Creates a value of <a>Condition</a> with the minimum fields required
--   to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>cAttributeValueList</a> - One or more values to evaluate
--   against the supplied attribute. The number of values in the list
--   depends on the <i>ComparisonOperator</i> being used. For type Number,
--   value comparisons are numeric. String value comparisons for greater
--   than, equals, or less than are based on ASCII character code values.
--   For example, <tt>a</tt> is greater than <tt>A</tt> , and <tt>a</tt> is
--   greater than <tt>B</tt> . For a list of code values, see
--   <a>http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters</a> .
--   For Binary, DynamoDB treats each byte of the binary data as unsigned
--   when it compares binary values.</li>
--   <li><a>cComparisonOperator</a> - A comparator for evaluating
--   attributes. For example, equals, greater than, less than, etc. The
--   following comparison operators are available: <tt>EQ | NE | LE | LT |
--   GE | GT | NOT_NULL | NULL | CONTAINS | NOT_CONTAINS | BEGINS_WITH | IN
--   | BETWEEN</tt> The following are descriptions of each comparison
--   operator. * <tt>EQ</tt> : Equal. <tt>EQ</tt> is supported for all
--   datatypes, including lists and maps. <i>AttributeValueList</i> can
--   contain only one <i>AttributeValue</i> element of type String, Number,
--   Binary, String Set, Number Set, or Binary Set. If an item contains an
--   <i>AttributeValue</i> element of a different type than the one
--   provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>NE</tt> : Not equal. <tt>NE</tt> is supported for
--   all datatypes, including lists and maps. <i>AttributeValueList</i> can
--   contain only one <i>AttributeValue</i> of type String, Number, Binary,
--   String Set, Number Set, or Binary Set. If an item contains an
--   <i>AttributeValue</i> of a different type than the one provided in the
--   request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LE</tt> : Less than or equal.
--   <i>AttributeValueList</i> can contain only one <i>AttributeValue</i>
--   element of type String, Number, or Binary (not a set type). If an item
--   contains an <i>AttributeValue</i> element of a different type than the
--   one provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LT</tt> : Less than. <i>AttributeValueList</i> can
--   contain only one <i>AttributeValue</i> of type String, Number, or
--   Binary (not a set type). If an item contains an <i>AttributeValue</i>
--   element of a different type than the one provided in the request, the
--   value does not match. For example, <tt>{<a>S</a>:"6"}</tt> does not
--   equal <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GE</tt> :
--   Greater than or equal. <i>AttributeValueList</i> can contain only one
--   <i>AttributeValue</i> element of type String, Number, or Binary (not a
--   set type). If an item contains an <i>AttributeValue</i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GT</tt> :
--   Greater than. <i>AttributeValueList</i> can contain only one
--   <i>AttributeValue</i> element of type String, Number, or Binary (not a
--   set type). If an item contains an <i>AttributeValue</i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>NOT_NULL</tt>
--   : The attribute exists. <tt>NOT_NULL</tt> is supported for all
--   datatypes, including lists and maps. * <tt>NULL</tt> : The attribute
--   does not exist. <tt>NULL</tt> is supported for all datatypes,
--   including lists and maps. * <tt>CONTAINS</tt> : Checks for a
--   subsequence, or value in a set. <i>AttributeValueList</i> can contain
--   only one <i>AttributeValue</i> element of type String, Number, or
--   Binary (not a set type). If the target attribute of the comparison is
--   of type String, then the operator checks for a substring match. If the
--   target attribute of the comparison is of type Binary, then the
--   operator looks for a subsequence of the target that matches the input.
--   If the target attribute of the comparison is a set ("<tt>SS</tt> ",
--   "<tt>NS</tt> ", or "<tt>BS</tt> "), then the operator evaluates to
--   true if it finds an exact match with any member of the set. CONTAINS
--   is supported for lists: When evaluating "<tt>a CONTAINS b</tt> ",
--   "<tt>a</tt> " can be a list; however, "<tt>b</tt> " cannot be a set, a
--   map, or a list. * <tt>NOT_CONTAINS</tt> : Checks for absence of a
--   subsequence, or absence of a value in a set. <i>AttributeValueList</i>
--   can contain only one <i>AttributeValue</i> element of type String,
--   Number, or Binary (not a set type). If the target attribute of the
--   comparison is a String, then the operator checks for the absence of a
--   substring match. If the target attribute of the comparison is Binary,
--   then the operator checks for the absence of a subsequence of the
--   target that matches the input. If the target attribute of the
--   comparison is a set ("<tt>SS</tt> ", "<tt>NS</tt> ", or "<tt>BS</tt>
--   "), then the operator evaluates to true if it <i>does not</i> find an
--   exact match with any member of the set. NOT_CONTAINS is supported for
--   lists: When evaluating "<tt>a NOT CONTAINS b</tt> ", "<tt>a</tt> " can
--   be a list; however, "<tt>b</tt> " cannot be a set, a map, or a list. *
--   <tt>BEGINS_WITH</tt> : Checks for a prefix. <i>AttributeValueList</i>
--   can contain only one <i>AttributeValue</i> of type String or Binary
--   (not a Number or a set type). The target attribute of the comparison
--   must be of type String or Binary (not a Number or a set type). *
--   <tt>IN</tt> : Checks for matching elements within two sets.
--   <i>AttributeValueList</i> can contain one or more
--   <i>AttributeValue</i> elements of type String, Number, or Binary (not
--   a set type). These attributes are compared against an existing set
--   type attribute of an item. If any elements of the input set are
--   present in the item attribute, the expression evaluates to true. *
--   <tt>BETWEEN</tt> : Greater than or equal to the first value, and less
--   than or equal to the second value. <i>AttributeValueList</i> must
--   contain two <i>AttributeValue</i> elements of the same type, either
--   String, Number, or Binary (not a set type). A target attribute matches
--   if the target value is greater than, or equal to, the first element
--   and less than, or equal to, the second element. If an item contains an
--   <i>AttributeValue</i> element of a different type than the one
--   provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not compare to <tt>{<a>N</a>:"6"}</tt> .
--   Also, <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6",
--   "2", "1"]}</tt> For usage examples of <i>AttributeValueList</i> and
--   <i>ComparisonOperator</i> , see <a>Legacy Conditional Parameters</a>
--   in the <i>Amazon DynamoDB Developer Guide</i> .</li>
--   </ul>
condition :: ComparisonOperator -> Condition

-- | One or more values to evaluate against the supplied attribute. The
--   number of values in the list depends on the <i>ComparisonOperator</i>
--   being used. For type Number, value comparisons are numeric. String
--   value comparisons for greater than, equals, or less than are based on
--   ASCII character code values. For example, <tt>a</tt> is greater than
--   <tt>A</tt> , and <tt>a</tt> is greater than <tt>B</tt> . For a list of
--   code values, see
--   <a>http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters</a> .
--   For Binary, DynamoDB treats each byte of the binary data as unsigned
--   when it compares binary values.
cAttributeValueList :: Lens' Condition [AttributeValue]

-- | A comparator for evaluating attributes. For example, equals, greater
--   than, less than, etc. The following comparison operators are
--   available: <tt>EQ | NE | LE | LT | GE | GT | NOT_NULL | NULL |
--   CONTAINS | NOT_CONTAINS | BEGINS_WITH | IN | BETWEEN</tt> The
--   following are descriptions of each comparison operator. * <tt>EQ</tt>
--   : Equal. <tt>EQ</tt> is supported for all datatypes, including lists
--   and maps. <i>AttributeValueList</i> can contain only one
--   <i>AttributeValue</i> element of type String, Number, Binary, String
--   Set, Number Set, or Binary Set. If an item contains an
--   <i>AttributeValue</i> element of a different type than the one
--   provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>NE</tt> : Not equal. <tt>NE</tt> is supported for
--   all datatypes, including lists and maps. <i>AttributeValueList</i> can
--   contain only one <i>AttributeValue</i> of type String, Number, Binary,
--   String Set, Number Set, or Binary Set. If an item contains an
--   <i>AttributeValue</i> of a different type than the one provided in the
--   request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LE</tt> : Less than or equal.
--   <i>AttributeValueList</i> can contain only one <i>AttributeValue</i>
--   element of type String, Number, or Binary (not a set type). If an item
--   contains an <i>AttributeValue</i> element of a different type than the
--   one provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LT</tt> : Less than. <i>AttributeValueList</i> can
--   contain only one <i>AttributeValue</i> of type String, Number, or
--   Binary (not a set type). If an item contains an <i>AttributeValue</i>
--   element of a different type than the one provided in the request, the
--   value does not match. For example, <tt>{<a>S</a>:"6"}</tt> does not
--   equal <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GE</tt> :
--   Greater than or equal. <i>AttributeValueList</i> can contain only one
--   <i>AttributeValue</i> element of type String, Number, or Binary (not a
--   set type). If an item contains an <i>AttributeValue</i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GT</tt> :
--   Greater than. <i>AttributeValueList</i> can contain only one
--   <i>AttributeValue</i> element of type String, Number, or Binary (not a
--   set type). If an item contains an <i>AttributeValue</i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>NOT_NULL</tt>
--   : The attribute exists. <tt>NOT_NULL</tt> is supported for all
--   datatypes, including lists and maps. * <tt>NULL</tt> : The attribute
--   does not exist. <tt>NULL</tt> is supported for all datatypes,
--   including lists and maps. * <tt>CONTAINS</tt> : Checks for a
--   subsequence, or value in a set. <i>AttributeValueList</i> can contain
--   only one <i>AttributeValue</i> element of type String, Number, or
--   Binary (not a set type). If the target attribute of the comparison is
--   of type String, then the operator checks for a substring match. If the
--   target attribute of the comparison is of type Binary, then the
--   operator looks for a subsequence of the target that matches the input.
--   If the target attribute of the comparison is a set ("<tt>SS</tt> ",
--   "<tt>NS</tt> ", or "<tt>BS</tt> "), then the operator evaluates to
--   true if it finds an exact match with any member of the set. CONTAINS
--   is supported for lists: When evaluating "<tt>a CONTAINS b</tt> ",
--   "<tt>a</tt> " can be a list; however, "<tt>b</tt> " cannot be a set, a
--   map, or a list. * <tt>NOT_CONTAINS</tt> : Checks for absence of a
--   subsequence, or absence of a value in a set. <i>AttributeValueList</i>
--   can contain only one <i>AttributeValue</i> element of type String,
--   Number, or Binary (not a set type). If the target attribute of the
--   comparison is a String, then the operator checks for the absence of a
--   substring match. If the target attribute of the comparison is Binary,
--   then the operator checks for the absence of a subsequence of the
--   target that matches the input. If the target attribute of the
--   comparison is a set ("<tt>SS</tt> ", "<tt>NS</tt> ", or "<tt>BS</tt>
--   "), then the operator evaluates to true if it <i>does not</i> find an
--   exact match with any member of the set. NOT_CONTAINS is supported for
--   lists: When evaluating "<tt>a NOT CONTAINS b</tt> ", "<tt>a</tt> " can
--   be a list; however, "<tt>b</tt> " cannot be a set, a map, or a list. *
--   <tt>BEGINS_WITH</tt> : Checks for a prefix. <i>AttributeValueList</i>
--   can contain only one <i>AttributeValue</i> of type String or Binary
--   (not a Number or a set type). The target attribute of the comparison
--   must be of type String or Binary (not a Number or a set type). *
--   <tt>IN</tt> : Checks for matching elements within two sets.
--   <i>AttributeValueList</i> can contain one or more
--   <i>AttributeValue</i> elements of type String, Number, or Binary (not
--   a set type). These attributes are compared against an existing set
--   type attribute of an item. If any elements of the input set are
--   present in the item attribute, the expression evaluates to true. *
--   <tt>BETWEEN</tt> : Greater than or equal to the first value, and less
--   than or equal to the second value. <i>AttributeValueList</i> must
--   contain two <i>AttributeValue</i> elements of the same type, either
--   String, Number, or Binary (not a set type). A target attribute matches
--   if the target value is greater than, or equal to, the first element
--   and less than, or equal to, the second element. If an item contains an
--   <i>AttributeValue</i> element of a different type than the one
--   provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not compare to <tt>{<a>N</a>:"6"}</tt> .
--   Also, <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6",
--   "2", "1"]}</tt> For usage examples of <i>AttributeValueList</i> and
--   <i>ComparisonOperator</i> , see <a>Legacy Conditional Parameters</a>
--   in the <i>Amazon DynamoDB Developer Guide</i> .
cComparisonOperator :: Lens' Condition ComparisonOperator

-- | The capacity units consumed by an operation. The data returned
--   includes the total provisioned throughput consumed, along with
--   statistics for the table and any indexes involved in the operation.
--   <i>ConsumedCapacity</i> is only returned if the request asked for it.
--   For more information, see <a>Provisioned Throughput</a> in the
--   <i>Amazon DynamoDB Developer Guide</i> .
--   
--   <i>See:</i> <a>consumedCapacity</a> smart constructor.
data ConsumedCapacity

-- | Creates a value of <a>ConsumedCapacity</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>ccGlobalSecondaryIndexes</a> - The amount of throughput
--   consumed on each global index affected by the operation.</li>
--   <li><a>ccCapacityUnits</a> - The total number of capacity units
--   consumed by the operation.</li>
--   <li><a>ccLocalSecondaryIndexes</a> - The amount of throughput consumed
--   on each local index affected by the operation.</li>
--   <li><a>ccTable</a> - The amount of throughput consumed on the table
--   affected by the operation.</li>
--   <li><a>ccTableName</a> - The name of the table that was affected by
--   the operation.</li>
--   </ul>
consumedCapacity :: ConsumedCapacity

-- | The amount of throughput consumed on each global index affected by the
--   operation.
ccGlobalSecondaryIndexes :: Lens' ConsumedCapacity (HashMap Text Capacity)

-- | The total number of capacity units consumed by the operation.
ccCapacityUnits :: Lens' ConsumedCapacity (Maybe Double)

-- | The amount of throughput consumed on each local index affected by the
--   operation.
ccLocalSecondaryIndexes :: Lens' ConsumedCapacity (HashMap Text Capacity)

-- | The amount of throughput consumed on the table affected by the
--   operation.
ccTable :: Lens' ConsumedCapacity (Maybe Capacity)

-- | The name of the table that was affected by the operation.
ccTableName :: Lens' ConsumedCapacity (Maybe Text)

-- | Represents a new global secondary index to be added to an existing
--   table.
--   
--   <i>See:</i> <a>createGlobalSecondaryIndexAction</a> smart constructor.
data CreateGlobalSecondaryIndexAction

-- | Creates a value of <a>CreateGlobalSecondaryIndexAction</a> with the
--   minimum fields required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>cgsiaIndexName</a> - The name of the global secondary index to
--   be created.</li>
--   <li><a>cgsiaKeySchema</a> - The key schema for the global secondary
--   index.</li>
--   <li><a>cgsiaProjection</a> - Undocumented member.</li>
--   <li><a>cgsiaProvisionedThroughput</a> - Undocumented member.</li>
--   </ul>
createGlobalSecondaryIndexAction :: Text -> NonEmpty KeySchemaElement -> Projection -> ProvisionedThroughput -> CreateGlobalSecondaryIndexAction

-- | The name of the global secondary index to be created.
cgsiaIndexName :: Lens' CreateGlobalSecondaryIndexAction Text

-- | The key schema for the global secondary index.
cgsiaKeySchema :: Lens' CreateGlobalSecondaryIndexAction (NonEmpty KeySchemaElement)

-- | Undocumented member.
cgsiaProjection :: Lens' CreateGlobalSecondaryIndexAction Projection

-- | Undocumented member.
cgsiaProvisionedThroughput :: Lens' CreateGlobalSecondaryIndexAction ProvisionedThroughput

-- | Represents a global secondary index to be deleted from an existing
--   table.
--   
--   <i>See:</i> <a>deleteGlobalSecondaryIndexAction</a> smart constructor.
data DeleteGlobalSecondaryIndexAction

-- | Creates a value of <a>DeleteGlobalSecondaryIndexAction</a> with the
--   minimum fields required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>dgsiaIndexName</a> - The name of the global secondary index to
--   be deleted.</li>
--   </ul>
deleteGlobalSecondaryIndexAction :: Text -> DeleteGlobalSecondaryIndexAction

-- | The name of the global secondary index to be deleted.
dgsiaIndexName :: Lens' DeleteGlobalSecondaryIndexAction Text

-- | Represents a request to perform a <i>DeleteItem</i> operation on an
--   item.
--   
--   <i>See:</i> <a>deleteRequest</a> smart constructor.
data DeleteRequest

-- | Creates a value of <a>DeleteRequest</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>drKey</a> - A map of attribute name to attribute values,
--   representing the primary key of the item to delete. All of the table's
--   primary key attributes must be specified, and their data types must
--   match those of the table's key schema.</li>
--   </ul>
deleteRequest :: DeleteRequest

-- | A map of attribute name to attribute values, representing the primary
--   key of the item to delete. All of the table's primary key attributes
--   must be specified, and their data types must match those of the
--   table's key schema.
drKey :: Lens' DeleteRequest (HashMap Text AttributeValue)

-- | Represents a condition to be compared with an attribute value. This
--   condition can be used with <i>DeleteItem</i> , <i>PutItem</i> or
--   <i>UpdateItem</i> operations; if the comparison evaluates to true, the
--   operation succeeds; if not, the operation fails. You can use
--   <i>ExpectedAttributeValue</i> in one of two different ways:
--   
--   <ul>
--   <li>Use <i>AttributeValueList</i> to specify one or more values to
--   compare against an attribute. Use <i>ComparisonOperator</i> to specify
--   how you want to perform the comparison. If the comparison evaluates to
--   true, then the conditional operation succeeds.</li>
--   <li>Use <i>Value</i> to specify a value that DynamoDB will compare
--   against an attribute. If the values match, then
--   <i>ExpectedAttributeValue</i> evaluates to true and the conditional
--   operation succeeds. Optionally, you can also set <i>Exists</i> to
--   false, indicating that you <i>do not</i> expect to find the attribute
--   value in the table. In this case, the conditional operation succeeds
--   only if the comparison evaluates to false.</li>
--   </ul>
--   
--   <i>Value</i> and <i>Exists</i> are incompatible with
--   <i>AttributeValueList</i> and <i>ComparisonOperator</i> . Note that if
--   you use both sets of parameters at once, DynamoDB will return a
--   <i>ValidationException</i> exception.
--   
--   <i>See:</i> <a>expectedAttributeValue</a> smart constructor.
data ExpectedAttributeValue

-- | Creates a value of <a>ExpectedAttributeValue</a> with the minimum
--   fields required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>eavAttributeValueList</a> - One or more values to evaluate
--   against the supplied attribute. The number of values in the list
--   depends on the <i>ComparisonOperator</i> being used. For type Number,
--   value comparisons are numeric. String value comparisons for greater
--   than, equals, or less than are based on ASCII character code values.
--   For example, <tt>a</tt> is greater than <tt>A</tt> , and <tt>a</tt> is
--   greater than <tt>B</tt> . For a list of code values, see
--   <a>http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters</a> .
--   For 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 <a>JSON Data Format</a> in the <i>Amazon DynamoDB
--   Developer Guide</i> .</li>
--   <li><a>eavExists</a> - Causes DynamoDB to evaluate the value before
--   attempting a conditional operation: * If <i>Exists</i> is
--   <tt>true</tt> , DynamoDB will check to see if that attribute value
--   already exists in the table. If it is found, then the operation
--   succeeds. If it is not found, the operation fails with a
--   <i>ConditionalCheckFailedException</i> . * If <i>Exists</i> is
--   <tt>false</tt> , DynamoDB assumes that the attribute value does not
--   exist in the table. If in fact the value does not exist, then the
--   assumption is valid and the operation succeeds. If the value is found,
--   despite the assumption that it does not exist, the operation fails
--   with a <i>ConditionalCheckFailedException</i> . The default setting
--   for <i>Exists</i> is <tt>true</tt> . If you supply a <i>Value</i> all
--   by itself, DynamoDB assumes the attribute exists: You don't have to
--   set <i>Exists</i> to <tt>true</tt> , because it is implied. DynamoDB
--   returns a <i>ValidationException</i> if: * <i>Exists</i> is
--   <tt>true</tt> but there is no <i>Value</i> to check. (You expect a
--   value to exist, but don't specify what that value is.) * <i>Exists</i>
--   is <tt>false</tt> but you also provide a <i>Value</i> . (You cannot
--   expect an attribute to have a value, while also expecting it not to
--   exist.)</li>
--   <li><a>eavValue</a> - Undocumented member.</li>
--   <li><a>eavComparisonOperator</a> - A comparator for evaluating
--   attributes in the <i>AttributeValueList</i> . For example, equals,
--   greater than, less than, etc. The following comparison operators are
--   available: <tt>EQ | NE | LE | LT | GE | GT | NOT_NULL | NULL |
--   CONTAINS | NOT_CONTAINS | BEGINS_WITH | IN | BETWEEN</tt> The
--   following are descriptions of each comparison operator. * <tt>EQ</tt>
--   : Equal. <tt>EQ</tt> is supported for all datatypes, including lists
--   and maps. <i>AttributeValueList</i> can contain only one
--   <i>AttributeValue</i> element of type String, Number, Binary, String
--   Set, Number Set, or Binary Set. If an item contains an
--   <i>AttributeValue</i> element of a different type than the one
--   provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>NE</tt> : Not equal. <tt>NE</tt> is supported for
--   all datatypes, including lists and maps. <i>AttributeValueList</i> can
--   contain only one <i>AttributeValue</i> of type String, Number, Binary,
--   String Set, Number Set, or Binary Set. If an item contains an
--   <i>AttributeValue</i> of a different type than the one provided in the
--   request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LE</tt> : Less than or equal.
--   <i>AttributeValueList</i> can contain only one <i>AttributeValue</i>
--   element of type String, Number, or Binary (not a set type). If an item
--   contains an <i>AttributeValue</i> element of a different type than the
--   one provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LT</tt> : Less than. <i>AttributeValueList</i> can
--   contain only one <i>AttributeValue</i> of type String, Number, or
--   Binary (not a set type). If an item contains an <i>AttributeValue</i>
--   element of a different type than the one provided in the request, the
--   value does not match. For example, <tt>{<a>S</a>:"6"}</tt> does not
--   equal <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GE</tt> :
--   Greater than or equal. <i>AttributeValueList</i> can contain only one
--   <i>AttributeValue</i> element of type String, Number, or Binary (not a
--   set type). If an item contains an <i>AttributeValue</i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GT</tt> :
--   Greater than. <i>AttributeValueList</i> can contain only one
--   <i>AttributeValue</i> element of type String, Number, or Binary (not a
--   set type). If an item contains an <i>AttributeValue</i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>NOT_NULL</tt>
--   : The attribute exists. <tt>NOT_NULL</tt> is supported for all
--   datatypes, including lists and maps. * <tt>NULL</tt> : The attribute
--   does not exist. <tt>NULL</tt> is supported for all datatypes,
--   including lists and maps. * <tt>CONTAINS</tt> : Checks for a
--   subsequence, or value in a set. <i>AttributeValueList</i> can contain
--   only one <i>AttributeValue</i> element of type String, Number, or
--   Binary (not a set type). If the target attribute of the comparison is
--   of type String, then the operator checks for a substring match. If the
--   target attribute of the comparison is of type Binary, then the
--   operator looks for a subsequence of the target that matches the input.
--   If the target attribute of the comparison is a set ("<tt>SS</tt> ",
--   "<tt>NS</tt> ", or "<tt>BS</tt> "), then the operator evaluates to
--   true if it finds an exact match with any member of the set. CONTAINS
--   is supported for lists: When evaluating "<tt>a CONTAINS b</tt> ",
--   "<tt>a</tt> " can be a list; however, "<tt>b</tt> " cannot be a set, a
--   map, or a list. * <tt>NOT_CONTAINS</tt> : Checks for absence of a
--   subsequence, or absence of a value in a set. <i>AttributeValueList</i>
--   can contain only one <i>AttributeValue</i> element of type String,
--   Number, or Binary (not a set type). If the target attribute of the
--   comparison is a String, then the operator checks for the absence of a
--   substring match. If the target attribute of the comparison is Binary,
--   then the operator checks for the absence of a subsequence of the
--   target that matches the input. If the target attribute of the
--   comparison is a set ("<tt>SS</tt> ", "<tt>NS</tt> ", or "<tt>BS</tt>
--   "), then the operator evaluates to true if it <i>does not</i> find an
--   exact match with any member of the set. NOT_CONTAINS is supported for
--   lists: When evaluating "<tt>a NOT CONTAINS b</tt> ", "<tt>a</tt> " can
--   be a list; however, "<tt>b</tt> " cannot be a set, a map, or a list. *
--   <tt>BEGINS_WITH</tt> : Checks for a prefix. <i>AttributeValueList</i>
--   can contain only one <i>AttributeValue</i> of type String or Binary
--   (not a Number or a set type). The target attribute of the comparison
--   must be of type String or Binary (not a Number or a set type). *
--   <tt>IN</tt> : Checks for matching elements within two sets.
--   <i>AttributeValueList</i> can contain one or more
--   <i>AttributeValue</i> elements of type String, Number, or Binary (not
--   a set type). These attributes are compared against an existing set
--   type attribute of an item. If any elements of the input set are
--   present in the item attribute, the expression evaluates to true. *
--   <tt>BETWEEN</tt> : Greater than or equal to the first value, and less
--   than or equal to the second value. <i>AttributeValueList</i> must
--   contain two <i>AttributeValue</i> elements of the same type, either
--   String, Number, or Binary (not a set type). A target attribute matches
--   if the target value is greater than, or equal to, the first element
--   and less than, or equal to, the second element. If an item contains an
--   <i>AttributeValue</i> element of a different type than the one
--   provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not compare to <tt>{<a>N</a>:"6"}</tt> .
--   Also, <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6",
--   "2", "1"]}</tt></li>
--   </ul>
expectedAttributeValue :: ExpectedAttributeValue

-- | One or more values to evaluate against the supplied attribute. The
--   number of values in the list depends on the <i>ComparisonOperator</i>
--   being used. For type Number, value comparisons are numeric. String
--   value comparisons for greater than, equals, or less than are based on
--   ASCII character code values. For example, <tt>a</tt> is greater than
--   <tt>A</tt> , and <tt>a</tt> is greater than <tt>B</tt> . For a list of
--   code values, see
--   <a>http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters</a> .
--   For 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 <a>JSON Data Format</a> in the <i>Amazon DynamoDB
--   Developer Guide</i> .
eavAttributeValueList :: Lens' ExpectedAttributeValue [AttributeValue]

-- | Causes DynamoDB to evaluate the value before attempting a conditional
--   operation: * If <i>Exists</i> is <tt>true</tt> , DynamoDB will check
--   to see if that attribute value already exists in the table. If it is
--   found, then the operation succeeds. If it is not found, the operation
--   fails with a <i>ConditionalCheckFailedException</i> . * If
--   <i>Exists</i> is <tt>false</tt> , DynamoDB assumes that the attribute
--   value does not exist in the table. If in fact the value does not
--   exist, then the assumption is valid and the operation succeeds. If the
--   value is found, despite the assumption that it does not exist, the
--   operation fails with a <i>ConditionalCheckFailedException</i> . The
--   default setting for <i>Exists</i> is <tt>true</tt> . If you supply a
--   <i>Value</i> all by itself, DynamoDB assumes the attribute exists: You
--   don't have to set <i>Exists</i> to <tt>true</tt> , because it is
--   implied. DynamoDB returns a <i>ValidationException</i> if: *
--   <i>Exists</i> is <tt>true</tt> but there is no <i>Value</i> to check.
--   (You expect a value to exist, but don't specify what that value is.) *
--   <i>Exists</i> is <tt>false</tt> but you also provide a <i>Value</i> .
--   (You cannot expect an attribute to have a value, while also expecting
--   it not to exist.)
eavExists :: Lens' ExpectedAttributeValue (Maybe Bool)

-- | Undocumented member.
eavValue :: Lens' ExpectedAttributeValue (Maybe AttributeValue)

-- | A comparator for evaluating attributes in the
--   <i>AttributeValueList</i> . For example, equals, greater than, less
--   than, etc. The following comparison operators are available: <tt>EQ |
--   NE | LE | LT | GE | GT | NOT_NULL | NULL | CONTAINS | NOT_CONTAINS |
--   BEGINS_WITH | IN | BETWEEN</tt> The following are descriptions of each
--   comparison operator. * <tt>EQ</tt> : Equal. <tt>EQ</tt> is supported
--   for all datatypes, including lists and maps. <i>AttributeValueList</i>
--   can contain only one <i>AttributeValue</i> element of type String,
--   Number, Binary, String Set, Number Set, or Binary Set. If an item
--   contains an <i>AttributeValue</i> element of a different type than the
--   one provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>NE</tt> : Not equal. <tt>NE</tt> is supported for
--   all datatypes, including lists and maps. <i>AttributeValueList</i> can
--   contain only one <i>AttributeValue</i> of type String, Number, Binary,
--   String Set, Number Set, or Binary Set. If an item contains an
--   <i>AttributeValue</i> of a different type than the one provided in the
--   request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LE</tt> : Less than or equal.
--   <i>AttributeValueList</i> can contain only one <i>AttributeValue</i>
--   element of type String, Number, or Binary (not a set type). If an item
--   contains an <i>AttributeValue</i> element of a different type than the
--   one provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LT</tt> : Less than. <i>AttributeValueList</i> can
--   contain only one <i>AttributeValue</i> of type String, Number, or
--   Binary (not a set type). If an item contains an <i>AttributeValue</i>
--   element of a different type than the one provided in the request, the
--   value does not match. For example, <tt>{<a>S</a>:"6"}</tt> does not
--   equal <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GE</tt> :
--   Greater than or equal. <i>AttributeValueList</i> can contain only one
--   <i>AttributeValue</i> element of type String, Number, or Binary (not a
--   set type). If an item contains an <i>AttributeValue</i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GT</tt> :
--   Greater than. <i>AttributeValueList</i> can contain only one
--   <i>AttributeValue</i> element of type String, Number, or Binary (not a
--   set type). If an item contains an <i>AttributeValue</i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>NOT_NULL</tt>
--   : The attribute exists. <tt>NOT_NULL</tt> is supported for all
--   datatypes, including lists and maps. * <tt>NULL</tt> : The attribute
--   does not exist. <tt>NULL</tt> is supported for all datatypes,
--   including lists and maps. * <tt>CONTAINS</tt> : Checks for a
--   subsequence, or value in a set. <i>AttributeValueList</i> can contain
--   only one <i>AttributeValue</i> element of type String, Number, or
--   Binary (not a set type). If the target attribute of the comparison is
--   of type String, then the operator checks for a substring match. If the
--   target attribute of the comparison is of type Binary, then the
--   operator looks for a subsequence of the target that matches the input.
--   If the target attribute of the comparison is a set ("<tt>SS</tt> ",
--   "<tt>NS</tt> ", or "<tt>BS</tt> "), then the operator evaluates to
--   true if it finds an exact match with any member of the set. CONTAINS
--   is supported for lists: When evaluating "<tt>a CONTAINS b</tt> ",
--   "<tt>a</tt> " can be a list; however, "<tt>b</tt> " cannot be a set, a
--   map, or a list. * <tt>NOT_CONTAINS</tt> : Checks for absence of a
--   subsequence, or absence of a value in a set. <i>AttributeValueList</i>
--   can contain only one <i>AttributeValue</i> element of type String,
--   Number, or Binary (not a set type). If the target attribute of the
--   comparison is a String, then the operator checks for the absence of a
--   substring match. If the target attribute of the comparison is Binary,
--   then the operator checks for the absence of a subsequence of the
--   target that matches the input. If the target attribute of the
--   comparison is a set ("<tt>SS</tt> ", "<tt>NS</tt> ", or "<tt>BS</tt>
--   "), then the operator evaluates to true if it <i>does not</i> find an
--   exact match with any member of the set. NOT_CONTAINS is supported for
--   lists: When evaluating "<tt>a NOT CONTAINS b</tt> ", "<tt>a</tt> " can
--   be a list; however, "<tt>b</tt> " cannot be a set, a map, or a list. *
--   <tt>BEGINS_WITH</tt> : Checks for a prefix. <i>AttributeValueList</i>
--   can contain only one <i>AttributeValue</i> of type String or Binary
--   (not a Number or a set type). The target attribute of the comparison
--   must be of type String or Binary (not a Number or a set type). *
--   <tt>IN</tt> : Checks for matching elements within two sets.
--   <i>AttributeValueList</i> can contain one or more
--   <i>AttributeValue</i> elements of type String, Number, or Binary (not
--   a set type). These attributes are compared against an existing set
--   type attribute of an item. If any elements of the input set are
--   present in the item attribute, the expression evaluates to true. *
--   <tt>BETWEEN</tt> : Greater than or equal to the first value, and less
--   than or equal to the second value. <i>AttributeValueList</i> must
--   contain two <i>AttributeValue</i> elements of the same type, either
--   String, Number, or Binary (not a set type). A target attribute matches
--   if the target value is greater than, or equal to, the first element
--   and less than, or equal to, the second element. If an item contains an
--   <i>AttributeValue</i> element of a different type than the one
--   provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not compare to <tt>{<a>N</a>:"6"}</tt> .
--   Also, <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6",
--   "2", "1"]}</tt>
eavComparisonOperator :: Lens' ExpectedAttributeValue (Maybe ComparisonOperator)

-- | Represents the properties of a global secondary index.
--   
--   <i>See:</i> <a>globalSecondaryIndex</a> smart constructor.
data GlobalSecondaryIndex

-- | Creates a value of <a>GlobalSecondaryIndex</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>gsiIndexName</a> - The name of the global secondary index. The
--   name must be unique among all other indexes on this table.</li>
--   <li><a>gsiKeySchema</a> - The complete key schema for a global
--   secondary index, which consists of one or more pairs of attribute
--   names and key types: * <tt>HASH</tt> - partition key * <tt>RANGE</tt>
--   - sort key</li>
--   <li><a>gsiProjection</a> - Undocumented member.</li>
--   <li><a>gsiProvisionedThroughput</a> - Undocumented member.</li>
--   </ul>
globalSecondaryIndex :: Text -> NonEmpty KeySchemaElement -> Projection -> ProvisionedThroughput -> GlobalSecondaryIndex

-- | The name of the global secondary index. The name must be unique among
--   all other indexes on this table.
gsiIndexName :: Lens' GlobalSecondaryIndex Text

-- | The complete key schema for a global secondary index, which consists
--   of one or more pairs of attribute names and key types: * <tt>HASH</tt>
--   - partition key * <tt>RANGE</tt> - sort key
gsiKeySchema :: Lens' GlobalSecondaryIndex (NonEmpty KeySchemaElement)

-- | Undocumented member.
gsiProjection :: Lens' GlobalSecondaryIndex Projection

-- | Undocumented member.
gsiProvisionedThroughput :: Lens' GlobalSecondaryIndex ProvisionedThroughput

-- | Represents the properties of a global secondary index.
--   
--   <i>See:</i> <a>globalSecondaryIndexDescription</a> smart constructor.
data GlobalSecondaryIndexDescription

-- | Creates a value of <a>GlobalSecondaryIndexDescription</a> with the
--   minimum fields required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>gsidBackfilling</a> - Indicates whether the index is currently
--   backfilling. <i>Backfilling</i> is the process of reading items from
--   the table and determining whether they can be added to the index. (Not
--   all items will qualify: For example, a partition key cannot have any
--   duplicate values.) If an item can be added to the index, DynamoDB will
--   do so. After all items have been processed, the backfilling operation
--   is complete and <i>Backfilling</i> is false.</li>
--   <li><a>gsidIndexSizeBytes</a> - The total size of the specified index,
--   in bytes. DynamoDB updates this value approximately every six hours.
--   Recent changes might not be reflected in this value.</li>
--   <li><a>gsidIndexStatus</a> - The current state of the global secondary
--   index: * <i>CREATING</i> - The index is being created. *
--   <i>UPDATING</i> - The index is being updated. * <i>DELETING</i> - The
--   index is being deleted. * <i>ACTIVE</i> - The index is ready for
--   use.</li>
--   <li><a>gsidProvisionedThroughput</a> - Undocumented member.</li>
--   <li><a>gsidIndexARN</a> - The Amazon Resource Name (ARN) that uniquely
--   identifies the index.</li>
--   <li><a>gsidKeySchema</a> - The complete key schema for a global
--   secondary index, which consists of one or more pairs of attribute
--   names and key types: * <tt>HASH</tt> - partition key * <tt>RANGE</tt>
--   - sort key</li>
--   <li><a>gsidProjection</a> - Undocumented member.</li>
--   <li><a>gsidItemCount</a> - The number of items in the specified index.
--   DynamoDB updates this value approximately every six hours. Recent
--   changes might not be reflected in this value.</li>
--   <li><a>gsidIndexName</a> - The name of the global secondary
--   index.</li>
--   </ul>
globalSecondaryIndexDescription :: GlobalSecondaryIndexDescription

-- | Indicates whether the index is currently backfilling.
--   <i>Backfilling</i> is the process of reading items from the table and
--   determining whether they can be added to the index. (Not all items
--   will qualify: For example, a partition key cannot have any duplicate
--   values.) If an item can be added to the index, DynamoDB will do so.
--   After all items have been processed, the backfilling operation is
--   complete and <i>Backfilling</i> is false.
gsidBackfilling :: Lens' GlobalSecondaryIndexDescription (Maybe Bool)

-- | The total size of the specified index, in bytes. DynamoDB updates this
--   value approximately every six hours. Recent changes might not be
--   reflected in this value.
gsidIndexSizeBytes :: Lens' GlobalSecondaryIndexDescription (Maybe Integer)

-- | The current state of the global secondary index: * <i>CREATING</i> -
--   The index is being created. * <i>UPDATING</i> - The index is being
--   updated. * <i>DELETING</i> - The index is being deleted. *
--   <i>ACTIVE</i> - The index is ready for use.
gsidIndexStatus :: Lens' GlobalSecondaryIndexDescription (Maybe IndexStatus)

-- | Undocumented member.
gsidProvisionedThroughput :: Lens' GlobalSecondaryIndexDescription (Maybe ProvisionedThroughputDescription)

-- | The Amazon Resource Name (ARN) that uniquely identifies the index.
gsidIndexARN :: Lens' GlobalSecondaryIndexDescription (Maybe Text)

-- | The complete key schema for a global secondary index, which consists
--   of one or more pairs of attribute names and key types: * <tt>HASH</tt>
--   - partition key * <tt>RANGE</tt> - sort key
gsidKeySchema :: Lens' GlobalSecondaryIndexDescription (Maybe (NonEmpty KeySchemaElement))

-- | Undocumented member.
gsidProjection :: Lens' GlobalSecondaryIndexDescription (Maybe Projection)

-- | The number of items in the specified index. DynamoDB updates this
--   value approximately every six hours. Recent changes might not be
--   reflected in this value.
gsidItemCount :: Lens' GlobalSecondaryIndexDescription (Maybe Integer)

-- | The name of the global secondary index.
gsidIndexName :: Lens' GlobalSecondaryIndexDescription (Maybe Text)

-- | Represents one of the following:
--   
--   <ul>
--   <li>A new global secondary index to be added to an existing
--   table.</li>
--   <li>New provisioned throughput parameters for an existing global
--   secondary index.</li>
--   <li>An existing global secondary index to be removed from an existing
--   table.</li>
--   </ul>
--   
--   <i>See:</i> <a>globalSecondaryIndexUpdate</a> smart constructor.
data GlobalSecondaryIndexUpdate

-- | Creates a value of <a>GlobalSecondaryIndexUpdate</a> with the minimum
--   fields required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>gsiuCreate</a> - The parameters required for creating a global
--   secondary index on an existing table: * <tt>IndexName </tt> *
--   <tt>KeySchema </tt> * <tt>AttributeDefinitions </tt> * <tt>Projection
--   </tt> * <tt>ProvisionedThroughput </tt></li>
--   <li><a>gsiuDelete</a> - The name of an existing global secondary index
--   to be removed.</li>
--   <li><a>gsiuUpdate</a> - The name of an existing global secondary
--   index, along with new provisioned throughput settings to be applied to
--   that index.</li>
--   </ul>
globalSecondaryIndexUpdate :: GlobalSecondaryIndexUpdate

-- | The parameters required for creating a global secondary index on an
--   existing table: * <tt>IndexName </tt> * <tt>KeySchema </tt> *
--   <tt>AttributeDefinitions </tt> * <tt>Projection </tt> *
--   <tt>ProvisionedThroughput </tt>
gsiuCreate :: Lens' GlobalSecondaryIndexUpdate (Maybe CreateGlobalSecondaryIndexAction)

-- | The name of an existing global secondary index to be removed.
gsiuDelete :: Lens' GlobalSecondaryIndexUpdate (Maybe DeleteGlobalSecondaryIndexAction)

-- | The name of an existing global secondary index, along with new
--   provisioned throughput settings to be applied to that index.
gsiuUpdate :: Lens' GlobalSecondaryIndexUpdate (Maybe UpdateGlobalSecondaryIndexAction)

-- | Information about item collections, if any, that were affected by the
--   operation. <i>ItemCollectionMetrics</i> is only returned if the
--   request asked for it. If the table does not have any local secondary
--   indexes, this information is not returned in the response.
--   
--   <i>See:</i> <a>itemCollectionMetrics</a> smart constructor.
data ItemCollectionMetrics

-- | Creates a value of <a>ItemCollectionMetrics</a> with the minimum
--   fields required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>icmItemCollectionKey</a> - The partition key value of the item
--   collection. This value is the same as the partition key value of the
--   item.</li>
--   <li><a>icmSizeEstimateRangeGB</a> - An estimate of item collection
--   size, in gigabytes. This value is a two-element array containing a
--   lower bound and an upper bound for the estimate. The estimate includes
--   the size of all the items in the table, plus the size of all
--   attributes projected into all of the local secondary indexes on that
--   table. Use this estimate to measure whether a local secondary index is
--   approaching its size limit. The estimate is subject to change over
--   time; therefore, do not rely on the precision or accuracy of the
--   estimate.</li>
--   </ul>
itemCollectionMetrics :: ItemCollectionMetrics

-- | The partition key value of the item collection. This value is the same
--   as the partition key value of the item.
icmItemCollectionKey :: Lens' ItemCollectionMetrics (HashMap Text AttributeValue)

-- | An estimate of item collection size, in gigabytes. This value is a
--   two-element array containing a lower bound and an upper bound for the
--   estimate. The estimate includes the size of all the items in the
--   table, plus the size of all attributes projected into all of the local
--   secondary indexes on that table. Use this estimate to measure whether
--   a local secondary index is approaching its size limit. The estimate is
--   subject to change over time; therefore, do not rely on the precision
--   or accuracy of the estimate.
icmSizeEstimateRangeGB :: Lens' ItemCollectionMetrics [Double]

-- | Represents <i>a single element</i> of a key schema. A key schema
--   specifies the attributes that make up the primary key of a table, or
--   the key attributes of an index.
--   
--   A <i>KeySchemaElement</i> represents exactly one attribute of the
--   primary key. For example, a simple primary key would be represented by
--   one <i>KeySchemaElement</i> (for the partition key). A composite
--   primary key would require one <i>KeySchemaElement</i> for the
--   partition key, and another <i>KeySchemaElement</i> for the sort key.
--   
--   A <i>KeySchemaElement</i> must be a scalar, top-level attribute (not a
--   nested attribute). The data type must be one of String, Number, or
--   Binary. The attribute cannot be nested within a List or a Map.
--   
--   <i>See:</i> <a>keySchemaElement</a> smart constructor.
data KeySchemaElement

-- | Creates a value of <a>KeySchemaElement</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>kseAttributeName</a> - The name of a key attribute.</li>
--   <li><a>kseKeyType</a> - The role that this key attribute will assume:
--   * <tt>HASH</tt> - partition key * <tt>RANGE</tt> - sort key</li>
--   </ul>
keySchemaElement :: Text -> KeyType -> KeySchemaElement

-- | The name of a key attribute.
kseAttributeName :: Lens' KeySchemaElement Text

-- | The role that this key attribute will assume: * <tt>HASH</tt> -
--   partition key * <tt>RANGE</tt> - sort key
kseKeyType :: Lens' KeySchemaElement KeyType

-- | Represents a set of primary keys and, for each key, the attributes to
--   retrieve from the table.
--   
--   For each primary key, you must provide <i>all</i> of the key
--   attributes. For example, with a simple primary key, you only need to
--   provide the partition key. For a composite primary key, you must
--   provide <i>both</i> the partition key and the sort key.
--   
--   <i>See:</i> <a>keysAndAttributes</a> smart constructor.
data KeysAndAttributes

-- | Creates a value of <a>KeysAndAttributes</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>kaaProjectionExpression</a> - A string that identifies one or
--   more attributes to retrieve from the table. These attributes can
--   include scalars, sets, or elements of a JSON document. The attributes
--   in the <i>ProjectionExpression</i> must be separated by commas. If no
--   attribute names are specified, then all attributes will be returned.
--   If any of the requested attributes are not found, they will not appear
--   in the result. For more information, see <a>Accessing Item
--   Attributes</a> in the <i>Amazon DynamoDB Developer Guide</i> .</li>
--   <li><a>kaaAttributesToGet</a> - One or more attributes to retrieve
--   from the table or index. If no attribute names are specified then all
--   attributes will be returned. If any of the specified attributes are
--   not found, they will not appear in the result.</li>
--   <li><a>kaaExpressionAttributeNames</a> - One or more substitution
--   tokens for attribute names in an expression. The following are some
--   use cases for using <i>ExpressionAttributeNames</i> : * To access an
--   attribute whose name conflicts with a DynamoDB reserved word. * To
--   create a placeholder for repeating occurrences of an attribute name in
--   an expression. * To prevent special characters in an attribute name
--   from being misinterpreted in an expression. Use the <b>#</b> character
--   in an expression to dereference an attribute name. For example,
--   consider the following attribute name: * <tt>Percentile</tt> The name
--   of this attribute conflicts with a reserved word, so it cannot be used
--   directly in an expression. (For the complete list of reserved words,
--   see <a>Reserved Words</a> in the <i>Amazon DynamoDB Developer
--   Guide</i> ). To work around this, you could specify the following for
--   <i>ExpressionAttributeNames</i> : * <tt>{"#P":<a>Percentile</a>}</tt>
--   You could then use this substitution in an expression, as in this
--   example: * <tt>#P = :val</tt> For more information on expression
--   attribute names, see <a>Accessing Item Attributes</a> in the <i>Amazon
--   DynamoDB Developer Guide</i> .</li>
--   <li><a>kaaConsistentRead</a> - The consistency of a read operation. If
--   set to <tt>true</tt> , then a strongly consistent read is used;
--   otherwise, an eventually consistent read is used.</li>
--   <li><a>kaaKeys</a> - The primary key attribute values that define the
--   items and the attributes associated with the items.</li>
--   </ul>
keysAndAttributes :: NonEmpty (HashMap Text AttributeValue) -> KeysAndAttributes

-- | A string that identifies one or more attributes to retrieve from the
--   table. These attributes can include scalars, sets, or elements of a
--   JSON document. The attributes in the <i>ProjectionExpression</i> must
--   be separated by commas. If no attribute names are specified, then all
--   attributes will be returned. If any of the requested attributes are
--   not found, they will not appear in the result. For more information,
--   see <a>Accessing Item Attributes</a> in the <i>Amazon DynamoDB
--   Developer Guide</i> .
kaaProjectionExpression :: Lens' KeysAndAttributes (Maybe Text)

-- | One or more attributes to retrieve from the table or index. If no
--   attribute names are specified then all attributes will be returned. If
--   any of the specified attributes are not found, they will not appear in
--   the result.
kaaAttributesToGet :: Lens' KeysAndAttributes (Maybe (NonEmpty Text))

-- | One or more substitution tokens for attribute names in an expression.
--   The following are some use cases for using
--   <i>ExpressionAttributeNames</i> : * To access an attribute whose name
--   conflicts with a DynamoDB reserved word. * To create a placeholder for
--   repeating occurrences of an attribute name in an expression. * To
--   prevent special characters in an attribute name from being
--   misinterpreted in an expression. Use the <b>#</b> character in an
--   expression to dereference an attribute name. For example, consider the
--   following attribute name: * <tt>Percentile</tt> The name of this
--   attribute conflicts with a reserved word, so it cannot be used
--   directly in an expression. (For the complete list of reserved words,
--   see <a>Reserved Words</a> in the <i>Amazon DynamoDB Developer
--   Guide</i> ). To work around this, you could specify the following for
--   <i>ExpressionAttributeNames</i> : * <tt>{"#P":<a>Percentile</a>}</tt>
--   You could then use this substitution in an expression, as in this
--   example: * <tt>#P = :val</tt> For more information on expression
--   attribute names, see <a>Accessing Item Attributes</a> in the <i>Amazon
--   DynamoDB Developer Guide</i> .
kaaExpressionAttributeNames :: Lens' KeysAndAttributes (HashMap Text Text)

-- | The consistency of a read operation. If set to <tt>true</tt> , then a
--   strongly consistent read is used; otherwise, an eventually consistent
--   read is used.
kaaConsistentRead :: Lens' KeysAndAttributes (Maybe Bool)

-- | The primary key attribute values that define the items and the
--   attributes associated with the items.
kaaKeys :: Lens' KeysAndAttributes (NonEmpty (HashMap Text AttributeValue))

-- | Represents the properties of a local secondary index.
--   
--   <i>See:</i> <a>localSecondaryIndex</a> smart constructor.
data LocalSecondaryIndex

-- | Creates a value of <a>LocalSecondaryIndex</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>lsiIndexName</a> - The name of the local secondary index. The
--   name must be unique among all other indexes on this table.</li>
--   <li><a>lsiKeySchema</a> - The complete key schema for the local
--   secondary index, consisting of one or more pairs of attribute names
--   and key types: * <tt>HASH</tt> - partition key * <tt>RANGE</tt> - sort
--   key</li>
--   <li><a>lsiProjection</a> - Undocumented member.</li>
--   </ul>
localSecondaryIndex :: Text -> NonEmpty KeySchemaElement -> Projection -> LocalSecondaryIndex

-- | The name of the local secondary index. The name must be unique among
--   all other indexes on this table.
lsiIndexName :: Lens' LocalSecondaryIndex Text

-- | The complete key schema for the local secondary index, consisting of
--   one or more pairs of attribute names and key types: * <tt>HASH</tt> -
--   partition key * <tt>RANGE</tt> - sort key
lsiKeySchema :: Lens' LocalSecondaryIndex (NonEmpty KeySchemaElement)

-- | Undocumented member.
lsiProjection :: Lens' LocalSecondaryIndex Projection

-- | Represents the properties of a local secondary index.
--   
--   <i>See:</i> <a>localSecondaryIndexDescription</a> smart constructor.
data LocalSecondaryIndexDescription

-- | Creates a value of <a>LocalSecondaryIndexDescription</a> with the
--   minimum fields required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>lsidIndexSizeBytes</a> - The total size of the specified index,
--   in bytes. DynamoDB updates this value approximately every six hours.
--   Recent changes might not be reflected in this value.</li>
--   <li><a>lsidIndexARN</a> - The Amazon Resource Name (ARN) that uniquely
--   identifies the index.</li>
--   <li><a>lsidKeySchema</a> - The complete key schema for the local
--   secondary index, consisting of one or more pairs of attribute names
--   and key types: * <tt>HASH</tt> - partition key * <tt>RANGE</tt> - sort
--   key</li>
--   <li><a>lsidProjection</a> - Undocumented member.</li>
--   <li><a>lsidItemCount</a> - The number of items in the specified index.
--   DynamoDB updates this value approximately every six hours. Recent
--   changes might not be reflected in this value.</li>
--   <li><a>lsidIndexName</a> - Represents the name of the local secondary
--   index.</li>
--   </ul>
localSecondaryIndexDescription :: LocalSecondaryIndexDescription

-- | The total size of the specified index, in bytes. DynamoDB updates this
--   value approximately every six hours. Recent changes might not be
--   reflected in this value.
lsidIndexSizeBytes :: Lens' LocalSecondaryIndexDescription (Maybe Integer)

-- | The Amazon Resource Name (ARN) that uniquely identifies the index.
lsidIndexARN :: Lens' LocalSecondaryIndexDescription (Maybe Text)

-- | The complete key schema for the local secondary index, consisting of
--   one or more pairs of attribute names and key types: * <tt>HASH</tt> -
--   partition key * <tt>RANGE</tt> - sort key
lsidKeySchema :: Lens' LocalSecondaryIndexDescription (Maybe (NonEmpty KeySchemaElement))

-- | Undocumented member.
lsidProjection :: Lens' LocalSecondaryIndexDescription (Maybe Projection)

-- | The number of items in the specified index. DynamoDB updates this
--   value approximately every six hours. Recent changes might not be
--   reflected in this value.
lsidItemCount :: Lens' LocalSecondaryIndexDescription (Maybe Integer)

-- | Represents the name of the local secondary index.
lsidIndexName :: Lens' LocalSecondaryIndexDescription (Maybe Text)

-- | Represents attributes that are copied (projected) from the table into
--   an index. These are in addition to the primary key attributes and
--   index key attributes, which are automatically projected.
--   
--   <i>See:</i> <a>projection</a> smart constructor.
data Projection

-- | Creates a value of <a>Projection</a> with the minimum fields required
--   to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>pProjectionType</a> - The set of attributes that are projected
--   into the index: * <tt>KEYS_ONLY</tt> - Only the index and primary keys
--   are projected into the index. * <tt>INCLUDE</tt> - Only the specified
--   table attributes are projected into the index. The list of projected
--   attributes are in <i>NonKeyAttributes</i> . * <tt>ALL</tt> - All of
--   the table attributes are projected into the index.</li>
--   <li><a>pNonKeyAttributes</a> - Represents the non-key attribute names
--   which will be projected into the index. For local secondary indexes,
--   the total count of <i>NonKeyAttributes</i> summed across all of the
--   local secondary indexes, must not exceed 20. If you project the same
--   attribute into two different indexes, this counts as two distinct
--   attributes when determining the total.</li>
--   </ul>
projection :: Projection

-- | The set of attributes that are projected into the index: *
--   <tt>KEYS_ONLY</tt> - Only the index and primary keys are projected
--   into the index. * <tt>INCLUDE</tt> - Only the specified table
--   attributes are projected into the index. The list of projected
--   attributes are in <i>NonKeyAttributes</i> . * <tt>ALL</tt> - All of
--   the table attributes are projected into the index.
pProjectionType :: Lens' Projection (Maybe ProjectionType)

-- | Represents the non-key attribute names which will be projected into
--   the index. For local secondary indexes, the total count of
--   <i>NonKeyAttributes</i> summed across all of the local secondary
--   indexes, must not exceed 20. If you project the same attribute into
--   two different indexes, this counts as two distinct attributes when
--   determining the total.
pNonKeyAttributes :: Lens' Projection (Maybe (NonEmpty Text))

-- | Represents the provisioned throughput settings for a specified table
--   or index. The settings can be modified using the <i>UpdateTable</i>
--   operation.
--   
--   For current minimum and maximum provisioned throughput values, see
--   <a>Limits</a> in the <i>Amazon DynamoDB Developer Guide</i> .
--   
--   <i>See:</i> <a>provisionedThroughput</a> smart constructor.
data ProvisionedThroughput

-- | Creates a value of <a>ProvisionedThroughput</a> with the minimum
--   fields required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>ptReadCapacityUnits</a> - The maximum number of strongly
--   consistent reads consumed per second before DynamoDB returns a
--   <i>ThrottlingException</i> . For more information, see <a>Specifying
--   Read and Write Requirements</a> in the <i>Amazon DynamoDB Developer
--   Guide</i> .</li>
--   <li><a>ptWriteCapacityUnits</a> - The maximum number of writes
--   consumed per second before DynamoDB returns a
--   <i>ThrottlingException</i> . For more information, see <a>Specifying
--   Read and Write Requirements</a> in the <i>Amazon DynamoDB Developer
--   Guide</i> .</li>
--   </ul>
provisionedThroughput :: Natural -> Natural -> ProvisionedThroughput

-- | The maximum number of strongly consistent reads consumed per second
--   before DynamoDB returns a <i>ThrottlingException</i> . For more
--   information, see <a>Specifying Read and Write Requirements</a> in the
--   <i>Amazon DynamoDB Developer Guide</i> .
ptReadCapacityUnits :: Lens' ProvisionedThroughput Natural

-- | The maximum number of writes consumed per second before DynamoDB
--   returns a <i>ThrottlingException</i> . For more information, see
--   <a>Specifying Read and Write Requirements</a> in the <i>Amazon
--   DynamoDB Developer Guide</i> .
ptWriteCapacityUnits :: Lens' ProvisionedThroughput Natural

-- | Represents the provisioned throughput settings for the table,
--   consisting of read and write capacity units, along with data about
--   increases and decreases.
--   
--   <i>See:</i> <a>provisionedThroughputDescription</a> smart constructor.
data ProvisionedThroughputDescription

-- | Creates a value of <a>ProvisionedThroughputDescription</a> with the
--   minimum fields required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>ptdReadCapacityUnits</a> - The maximum number of strongly
--   consistent reads consumed per second before DynamoDB returns a
--   <i>ThrottlingException</i> . Eventually consistent reads require less
--   effort than strongly consistent reads, so a setting of 50
--   <i>ReadCapacityUnits</i> per second provides 100 eventually consistent
--   <i>ReadCapacityUnits</i> per second.</li>
--   <li><a>ptdLastDecreaseDateTime</a> - The date and time of the last
--   provisioned throughput decrease for this table.</li>
--   <li><a>ptdWriteCapacityUnits</a> - The maximum number of writes
--   consumed per second before DynamoDB returns a
--   <i>ThrottlingException</i> .</li>
--   <li><a>ptdNumberOfDecreasesToday</a> - The number of provisioned
--   throughput decreases for this table during this UTC calendar day. For
--   current maximums on provisioned throughput decreases, see
--   <a>Limits</a> in the <i>Amazon DynamoDB Developer Guide</i> .</li>
--   <li><a>ptdLastIncreaseDateTime</a> - The date and time of the last
--   provisioned throughput increase for this table.</li>
--   </ul>
provisionedThroughputDescription :: ProvisionedThroughputDescription

-- | The maximum number of strongly consistent reads consumed per second
--   before DynamoDB returns a <i>ThrottlingException</i> . Eventually
--   consistent reads require less effort than strongly consistent reads,
--   so a setting of 50 <i>ReadCapacityUnits</i> per second provides 100
--   eventually consistent <i>ReadCapacityUnits</i> per second.
ptdReadCapacityUnits :: Lens' ProvisionedThroughputDescription (Maybe Natural)

-- | The date and time of the last provisioned throughput decrease for this
--   table.
ptdLastDecreaseDateTime :: Lens' ProvisionedThroughputDescription (Maybe UTCTime)

-- | The maximum number of writes consumed per second before DynamoDB
--   returns a <i>ThrottlingException</i> .
ptdWriteCapacityUnits :: Lens' ProvisionedThroughputDescription (Maybe Natural)

-- | The number of provisioned throughput decreases for this table during
--   this UTC calendar day. For current maximums on provisioned throughput
--   decreases, see <a>Limits</a> in the <i>Amazon DynamoDB Developer
--   Guide</i> .
ptdNumberOfDecreasesToday :: Lens' ProvisionedThroughputDescription (Maybe Natural)

-- | The date and time of the last provisioned throughput increase for this
--   table.
ptdLastIncreaseDateTime :: Lens' ProvisionedThroughputDescription (Maybe UTCTime)

-- | Represents a request to perform a <i>PutItem</i> operation on an item.
--   
--   <i>See:</i> <a>putRequest</a> smart constructor.
data PutRequest

-- | Creates a value of <a>PutRequest</a> with the minimum fields required
--   to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>prItem</a> - A map of attribute name to attribute values,
--   representing the primary key of an item to be processed by
--   <i>PutItem</i> . All of the table's primary key attributes must be
--   specified, and their data types must match those of the table's key
--   schema. If any attributes are present in the item which are part of an
--   index key schema for the table, their types must match the index key
--   schema.</li>
--   </ul>
putRequest :: PutRequest

-- | A map of attribute name to attribute values, representing the primary
--   key of an item to be processed by <i>PutItem</i> . All of the table's
--   primary key attributes must be specified, and their data types must
--   match those of the table's key schema. If any attributes are present
--   in the item which are part of an index key schema for the table, their
--   types must match the index key schema.
prItem :: Lens' PutRequest (HashMap Text AttributeValue)

-- | Represents the DynamoDB Streams configuration for a table in DynamoDB.
--   
--   <i>See:</i> <a>streamSpecification</a> smart constructor.
data StreamSpecification

-- | Creates a value of <a>StreamSpecification</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>ssStreamViewType</a> - The DynamoDB Streams settings for the
--   table. These settings consist of: * <i>StreamEnabled</i> - Indicates
--   whether DynamoDB Streams is enabled (true) or disabled (false) on the
--   table. * <i>StreamViewType</i> - When an item in the table is
--   modified, <i>StreamViewType</i> determines what information is written
--   to the stream for this table. Valid values for <i>StreamViewType</i>
--   are: * <i>KEYS_ONLY</i> - Only the key attributes of the modified item
--   are written to the stream. * <i>NEW_IMAGE</i> - The entire item, as it
--   appears after it was modified, is written to the stream. *
--   <i>OLD_IMAGE</i> - The entire item, as it appeared before it was
--   modified, is written to the stream. * <i>NEW_AND_OLD_IMAGES</i> - Both
--   the new and the old item images of the item are written to the
--   stream.</li>
--   <li><a>ssStreamEnabled</a> - Indicates whether DynamoDB Streams is
--   enabled (true) or disabled (false) on the table.</li>
--   </ul>
streamSpecification :: StreamSpecification

-- | The DynamoDB Streams settings for the table. These settings consist
--   of: * <i>StreamEnabled</i> - Indicates whether DynamoDB Streams is
--   enabled (true) or disabled (false) on the table. *
--   <i>StreamViewType</i> - When an item in the table is modified,
--   <i>StreamViewType</i> determines what information is written to the
--   stream for this table. Valid values for <i>StreamViewType</i> are: *
--   <i>KEYS_ONLY</i> - Only the key attributes of the modified item are
--   written to the stream. * <i>NEW_IMAGE</i> - The entire item, as it
--   appears after it was modified, is written to the stream. *
--   <i>OLD_IMAGE</i> - The entire item, as it appeared before it was
--   modified, is written to the stream. * <i>NEW_AND_OLD_IMAGES</i> - Both
--   the new and the old item images of the item are written to the stream.
ssStreamViewType :: Lens' StreamSpecification (Maybe StreamViewType)

-- | Indicates whether DynamoDB Streams is enabled (true) or disabled
--   (false) on the table.
ssStreamEnabled :: Lens' StreamSpecification (Maybe Bool)

-- | Represents the properties of a table.
--   
--   <i>See:</i> <a>tableDescription</a> smart constructor.
data TableDescription

-- | Creates a value of <a>TableDescription</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>tdTableSizeBytes</a> - The total size of the specified table,
--   in bytes. DynamoDB updates this value approximately every six hours.
--   Recent changes might not be reflected in this value.</li>
--   <li><a>tdAttributeDefinitions</a> - An array of
--   <i>AttributeDefinition</i> objects. Each of these objects describes
--   one attribute in the table and index key schema. Each
--   <i>AttributeDefinition</i> object in this array is composed of: *
--   <i>AttributeName</i> - The name of the attribute. *
--   <i>AttributeType</i> - The data type for the attribute.</li>
--   <li><a>tdLatestStreamARN</a> - The Amazon Resource Name (ARN) that
--   uniquely identifies the latest stream for this table.</li>
--   <li><a>tdProvisionedThroughput</a> - The provisioned throughput
--   settings for the table, consisting of read and write capacity units,
--   along with data about increases and decreases.</li>
--   <li><a>tdTableStatus</a> - The current state of the table: *
--   <i>CREATING</i> - The table is being created. * <i>UPDATING</i> - The
--   table is being updated. * <i>DELETING</i> - The table is being
--   deleted. * <i>ACTIVE</i> - The table is ready for use.</li>
--   <li><a>tdTableARN</a> - The Amazon Resource Name (ARN) that uniquely
--   identifies the table.</li>
--   <li><a>tdKeySchema</a> - The primary key structure for the table. Each
--   <i>KeySchemaElement</i> consists of: * <i>AttributeName</i> - The name
--   of the attribute. * <i>KeyType</i> - The role of the attribute: *
--   <tt>HASH</tt> - partition key * <tt>RANGE</tt> - sort key For more
--   information about primary keys, see <a>Primary Key</a> in the
--   <i>Amazon DynamoDB Developer Guide</i> .</li>
--   <li><a>tdGlobalSecondaryIndexes</a> - The global secondary indexes, if
--   any, on the table. Each index is scoped to a given partition key
--   value. Each element is composed of: * <i>Backfilling</i> - If true,
--   then the index is currently in the backfilling phase. Backfilling
--   occurs only when a new global secondary index is added to the table;
--   it is the process by which DynamoDB populates the new index with data
--   from the table. (This attribute does not appear for indexes that were
--   created during a <i>CreateTable</i> operation.) * <i>IndexName</i> -
--   The name of the global secondary index. * <i>IndexSizeBytes</i> - The
--   total size of the global secondary index, in bytes. DynamoDB updates
--   this value approximately every six hours. Recent changes might not be
--   reflected in this value. * <i>IndexStatus</i> - The current status of
--   the global secondary index: * <i>CREATING</i> - The index is being
--   created. * <i>UPDATING</i> - The index is being updated. *
--   <i>DELETING</i> - The index is being deleted. * <i>ACTIVE</i> - The
--   index is ready for use. * <i>ItemCount</i> - The number of items in
--   the global secondary index. DynamoDB updates this value approximately
--   every six hours. Recent changes might not be reflected in this value.
--   * <i>KeySchema</i> - Specifies the complete index key schema. The
--   attribute names in the key schema must be between 1 and 255 characters
--   (inclusive). The key schema must begin with the same partition key as
--   the table. * <i>Projection</i> - Specifies attributes that are copied
--   (projected) from the table into the index. These are in addition to
--   the primary key attributes and index key attributes, which are
--   automatically projected. Each attribute specification is composed of:
--   * <i>ProjectionType</i> - One of the following: * <tt>KEYS_ONLY</tt> -
--   Only the index and primary keys are projected into the index. *
--   <tt>INCLUDE</tt> - Only the specified table attributes are projected
--   into the index. The list of projected attributes are in
--   <i>NonKeyAttributes</i> . * <tt>ALL</tt> - All of the table attributes
--   are projected into the index. * <i>NonKeyAttributes</i> - A list of
--   one or more non-key attribute names that are projected into the
--   secondary index. The total count of attributes provided in
--   <i>NonKeyAttributes</i> , summed across all of the secondary indexes,
--   must not exceed 20. If you project the same attribute into two
--   different indexes, this counts as two distinct attributes when
--   determining the total. * <i>ProvisionedThroughput</i> - The
--   provisioned throughput settings for the global secondary index,
--   consisting of read and write capacity units, along with data about
--   increases and decreases. If the table is in the <tt>DELETING</tt>
--   state, no information about indexes will be returned.</li>
--   <li><a>tdLatestStreamLabel</a> - A timestamp, in ISO 8601 format, for
--   this stream. Note that <i>LatestStreamLabel</i> is not a unique
--   identifier for the stream, because it is possible that a stream from
--   another table might have the same timestamp. However, the combination
--   of the following three elements is guaranteed to be unique: * the AWS
--   customer ID. * the table name. * the <i>StreamLabel</i> .</li>
--   <li><a>tdLocalSecondaryIndexes</a> - Represents one or more local
--   secondary indexes on the table. Each index is scoped to a given
--   partition key value. Tables with one or more local secondary indexes
--   are subject to an item collection size limit, where the amount of data
--   within a given item collection cannot exceed 10 GB. Each element is
--   composed of: * <i>IndexName</i> - The name of the local secondary
--   index. * <i>KeySchema</i> - Specifies the complete index key schema.
--   The attribute names in the key schema must be between 1 and 255
--   characters (inclusive). The key schema must begin with the same
--   partition key as the table. * <i>Projection</i> - Specifies attributes
--   that are copied (projected) from the table into the index. These are
--   in addition to the primary key attributes and index key attributes,
--   which are automatically projected. Each attribute specification is
--   composed of: * <i>ProjectionType</i> - One of the following: *
--   <tt>KEYS_ONLY</tt> - Only the index and primary keys are projected
--   into the index. * <tt>INCLUDE</tt> - Only the specified table
--   attributes are projected into the index. The list of projected
--   attributes are in <i>NonKeyAttributes</i> . * <tt>ALL</tt> - All of
--   the table attributes are projected into the index. *
--   <i>NonKeyAttributes</i> - A list of one or more non-key attribute
--   names that are projected into the secondary index. The total count of
--   attributes provided in <i>NonKeyAttributes</i> , summed across all of
--   the secondary indexes, must not exceed 20. If you project the same
--   attribute into two different indexes, this counts as two distinct
--   attributes when determining the total. * <i>IndexSizeBytes</i> -
--   Represents the total size of the index, in bytes. DynamoDB updates
--   this value approximately every six hours. Recent changes might not be
--   reflected in this value. * <i>ItemCount</i> - Represents the number of
--   items in the index. DynamoDB updates this value approximately every
--   six hours. Recent changes might not be reflected in this value. If the
--   table is in the <tt>DELETING</tt> state, no information about indexes
--   will be returned.</li>
--   <li><a>tdCreationDateTime</a> - The date and time when the table was
--   created, in <a>UNIX epoch time</a> format.</li>
--   <li><a>tdItemCount</a> - The number of items in the specified table.
--   DynamoDB updates this value approximately every six hours. Recent
--   changes might not be reflected in this value.</li>
--   <li><a>tdTableName</a> - The name of the table.</li>
--   <li><a>tdStreamSpecification</a> - The current DynamoDB Streams
--   configuration for the table.</li>
--   </ul>
tableDescription :: TableDescription

-- | The total size of the specified table, in bytes. DynamoDB updates this
--   value approximately every six hours. Recent changes might not be
--   reflected in this value.
tdTableSizeBytes :: Lens' TableDescription (Maybe Integer)

-- | An array of <i>AttributeDefinition</i> objects. Each of these objects
--   describes one attribute in the table and index key schema. Each
--   <i>AttributeDefinition</i> object in this array is composed of: *
--   <i>AttributeName</i> - The name of the attribute. *
--   <i>AttributeType</i> - The data type for the attribute.
tdAttributeDefinitions :: Lens' TableDescription [AttributeDefinition]

-- | The Amazon Resource Name (ARN) that uniquely identifies the latest
--   stream for this table.
tdLatestStreamARN :: Lens' TableDescription (Maybe Text)

-- | The provisioned throughput settings for the table, consisting of read
--   and write capacity units, along with data about increases and
--   decreases.
tdProvisionedThroughput :: Lens' TableDescription (Maybe ProvisionedThroughputDescription)

-- | The current state of the table: * <i>CREATING</i> - The table is being
--   created. * <i>UPDATING</i> - The table is being updated. *
--   <i>DELETING</i> - The table is being deleted. * <i>ACTIVE</i> - The
--   table is ready for use.
tdTableStatus :: Lens' TableDescription (Maybe TableStatus)

-- | The Amazon Resource Name (ARN) that uniquely identifies the table.
tdTableARN :: Lens' TableDescription (Maybe Text)

-- | The primary key structure for the table. Each <i>KeySchemaElement</i>
--   consists of: * <i>AttributeName</i> - The name of the attribute. *
--   <i>KeyType</i> - The role of the attribute: * <tt>HASH</tt> -
--   partition key * <tt>RANGE</tt> - sort key For more information about
--   primary keys, see <a>Primary Key</a> in the <i>Amazon DynamoDB
--   Developer Guide</i> .
tdKeySchema :: Lens' TableDescription (Maybe (NonEmpty KeySchemaElement))

-- | The global secondary indexes, if any, on the table. Each index is
--   scoped to a given partition key value. Each element is composed of: *
--   <i>Backfilling</i> - If true, then the index is currently in the
--   backfilling phase. Backfilling occurs only when a new global secondary
--   index is added to the table; it is the process by which DynamoDB
--   populates the new index with data from the table. (This attribute does
--   not appear for indexes that were created during a <i>CreateTable</i>
--   operation.) * <i>IndexName</i> - The name of the global secondary
--   index. * <i>IndexSizeBytes</i> - The total size of the global
--   secondary index, in bytes. DynamoDB updates this value approximately
--   every six hours. Recent changes might not be reflected in this value.
--   * <i>IndexStatus</i> - The current status of the global secondary
--   index: * <i>CREATING</i> - The index is being created. *
--   <i>UPDATING</i> - The index is being updated. * <i>DELETING</i> - The
--   index is being deleted. * <i>ACTIVE</i> - The index is ready for use.
--   * <i>ItemCount</i> - The number of items in the global secondary
--   index. DynamoDB updates this value approximately every six hours.
--   Recent changes might not be reflected in this value. *
--   <i>KeySchema</i> - Specifies the complete index key schema. The
--   attribute names in the key schema must be between 1 and 255 characters
--   (inclusive). The key schema must begin with the same partition key as
--   the table. * <i>Projection</i> - Specifies attributes that are copied
--   (projected) from the table into the index. These are in addition to
--   the primary key attributes and index key attributes, which are
--   automatically projected. Each attribute specification is composed of:
--   * <i>ProjectionType</i> - One of the following: * <tt>KEYS_ONLY</tt> -
--   Only the index and primary keys are projected into the index. *
--   <tt>INCLUDE</tt> - Only the specified table attributes are projected
--   into the index. The list of projected attributes are in
--   <i>NonKeyAttributes</i> . * <tt>ALL</tt> - All of the table attributes
--   are projected into the index. * <i>NonKeyAttributes</i> - A list of
--   one or more non-key attribute names that are projected into the
--   secondary index. The total count of attributes provided in
--   <i>NonKeyAttributes</i> , summed across all of the secondary indexes,
--   must not exceed 20. If you project the same attribute into two
--   different indexes, this counts as two distinct attributes when
--   determining the total. * <i>ProvisionedThroughput</i> - The
--   provisioned throughput settings for the global secondary index,
--   consisting of read and write capacity units, along with data about
--   increases and decreases. If the table is in the <tt>DELETING</tt>
--   state, no information about indexes will be returned.
tdGlobalSecondaryIndexes :: Lens' TableDescription [GlobalSecondaryIndexDescription]

-- | A timestamp, in ISO 8601 format, for this stream. Note that
--   <i>LatestStreamLabel</i> is not a unique identifier for the stream,
--   because it is possible that a stream from another table might have the
--   same timestamp. However, the combination of the following three
--   elements is guaranteed to be unique: * the AWS customer ID. * the
--   table name. * the <i>StreamLabel</i> .
tdLatestStreamLabel :: Lens' TableDescription (Maybe Text)

-- | Represents one or more local secondary indexes on the table. Each
--   index is scoped to a given partition key value. Tables with one or
--   more local secondary indexes are subject to an item collection size
--   limit, where the amount of data within a given item collection cannot
--   exceed 10 GB. Each element is composed of: * <i>IndexName</i> - The
--   name of the local secondary index. * <i>KeySchema</i> - Specifies the
--   complete index key schema. The attribute names in the key schema must
--   be between 1 and 255 characters (inclusive). The key schema must begin
--   with the same partition key as the table. * <i>Projection</i> -
--   Specifies attributes that are copied (projected) from the table into
--   the index. These are in addition to the primary key attributes and
--   index key attributes, which are automatically projected. Each
--   attribute specification is composed of: * <i>ProjectionType</i> - One
--   of the following: * <tt>KEYS_ONLY</tt> - Only the index and primary
--   keys are projected into the index. * <tt>INCLUDE</tt> - Only the
--   specified table attributes are projected into the index. The list of
--   projected attributes are in <i>NonKeyAttributes</i> . * <tt>ALL</tt> -
--   All of the table attributes are projected into the index. *
--   <i>NonKeyAttributes</i> - A list of one or more non-key attribute
--   names that are projected into the secondary index. The total count of
--   attributes provided in <i>NonKeyAttributes</i> , summed across all of
--   the secondary indexes, must not exceed 20. If you project the same
--   attribute into two different indexes, this counts as two distinct
--   attributes when determining the total. * <i>IndexSizeBytes</i> -
--   Represents the total size of the index, in bytes. DynamoDB updates
--   this value approximately every six hours. Recent changes might not be
--   reflected in this value. * <i>ItemCount</i> - Represents the number of
--   items in the index. DynamoDB updates this value approximately every
--   six hours. Recent changes might not be reflected in this value. If the
--   table is in the <tt>DELETING</tt> state, no information about indexes
--   will be returned.
tdLocalSecondaryIndexes :: Lens' TableDescription [LocalSecondaryIndexDescription]

-- | The date and time when the table was created, in <a>UNIX epoch
--   time</a> format.
tdCreationDateTime :: Lens' TableDescription (Maybe UTCTime)

-- | The number of items in the specified table. DynamoDB updates this
--   value approximately every six hours. Recent changes might not be
--   reflected in this value.
tdItemCount :: Lens' TableDescription (Maybe Integer)

-- | The name of the table.
tdTableName :: Lens' TableDescription (Maybe Text)

-- | The current DynamoDB Streams configuration for the table.
tdStreamSpecification :: Lens' TableDescription (Maybe StreamSpecification)

-- | Represents the new provisioned throughput settings to be applied to a
--   global secondary index.
--   
--   <i>See:</i> <a>updateGlobalSecondaryIndexAction</a> smart constructor.
data UpdateGlobalSecondaryIndexAction

-- | Creates a value of <a>UpdateGlobalSecondaryIndexAction</a> with the
--   minimum fields required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>ugsiaIndexName</a> - The name of the global secondary index to
--   be updated.</li>
--   <li><a>ugsiaProvisionedThroughput</a> - Undocumented member.</li>
--   </ul>
updateGlobalSecondaryIndexAction :: Text -> ProvisionedThroughput -> UpdateGlobalSecondaryIndexAction

-- | The name of the global secondary index to be updated.
ugsiaIndexName :: Lens' UpdateGlobalSecondaryIndexAction Text

-- | Undocumented member.
ugsiaProvisionedThroughput :: Lens' UpdateGlobalSecondaryIndexAction ProvisionedThroughput

-- | Represents an operation to perform - either <i>DeleteItem</i> or
--   <i>PutItem</i> . You can only request one of these operations, not
--   both, in a single <i>WriteRequest</i> . If you do need to perform both
--   of these operations, you will need to provide two separate
--   <i>WriteRequest</i> objects.
--   
--   <i>See:</i> <a>writeRequest</a> smart constructor.
data WriteRequest

-- | Creates a value of <a>WriteRequest</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>wrDeleteRequest</a> - A request to perform a <i>DeleteItem</i>
--   operation.</li>
--   <li><a>wrPutRequest</a> - A request to perform a <i>PutItem</i>
--   operation.</li>
--   </ul>
writeRequest :: WriteRequest

-- | A request to perform a <i>DeleteItem</i> operation.
wrDeleteRequest :: Lens' WriteRequest (Maybe DeleteRequest)

-- | A request to perform a <i>PutItem</i> operation.
wrPutRequest :: Lens' WriteRequest (Maybe PutRequest)


-- | Edits an existing item's attributes, or adds a new item to the table
--   if it does not already exist. You can put, delete, or add attribute
--   values. You can also perform a conditional update on an existing item
--   (insert a new attribute name-value pair if it doesn't exist, or
--   replace an existing name-value pair if it has certain expected
--   attribute values).
--   
--   You can also return the item's attribute values in the same
--   <i>UpdateItem</i> operation using the <i>ReturnValues</i> parameter.
module Network.AWS.DynamoDB.UpdateItem

-- | Creates a value of <a>UpdateItem</a> with the minimum fields required
--   to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>uiExpressionAttributeNames</a> - One or more substitution
--   tokens for attribute names in an expression. The following are some
--   use cases for using <i>ExpressionAttributeNames</i> : * To access an
--   attribute whose name conflicts with a DynamoDB reserved word. * To
--   create a placeholder for repeating occurrences of an attribute name in
--   an expression. * To prevent special characters in an attribute name
--   from being misinterpreted in an expression. Use the <b>#</b> character
--   in an expression to dereference an attribute name. For example,
--   consider the following attribute name: * <tt>Percentile</tt> The name
--   of this attribute conflicts with a reserved word, so it cannot be used
--   directly in an expression. (For the complete list of reserved words,
--   see <a>Reserved Words</a> in the <i>Amazon DynamoDB Developer
--   Guide</i> ). To work around this, you could specify the following for
--   <i>ExpressionAttributeNames</i> : * <tt>{"#P":<a>Percentile</a>}</tt>
--   You could then use this substitution in an expression, as in this
--   example: * <tt>#P = :val</tt> For more information on expression
--   attribute names, see <a>Accessing Item Attributes</a> in the <i>Amazon
--   DynamoDB Developer Guide</i> .</li>
--   <li><a>uiReturnValues</a> - Use <i>ReturnValues</i> if you want to get
--   the item attributes as they appeared either before or after they were
--   updated. For <i>UpdateItem</i> , the valid values are: * <tt>NONE</tt>
--   - If <i>ReturnValues</i> is not specified, or if its value is
--   <tt>NONE</tt> , then nothing is returned. (This setting is the default
--   for <i>ReturnValues</i> .) * <tt>ALL_OLD</tt> - If <i>UpdateItem</i>
--   overwrote an attribute name-value pair, then the content of the old
--   item is returned. * <tt>UPDATED_OLD</tt> - The old versions of only
--   the updated attributes are returned. * <tt>ALL_NEW</tt> - All of the
--   attributes of the new version of the item are returned. *
--   <tt>UPDATED_NEW</tt> - The new versions of only the updated attributes
--   are returned. There is no additional cost associated with requesting a
--   return value aside from the small network and processing overhead of
--   receiving a larger response. No Read Capacity Units are consumed.
--   Values returned are strongly consistent</li>
--   <li><a>uiUpdateExpression</a> - An expression that defines one or more
--   attributes to be updated, the action to be performed on them, and new
--   value(s) for them. The following action values are available for
--   <i>UpdateExpression</i> . * <tt>SET</tt> - Adds one or more attributes
--   and values to an item. If any of these attribute already exist, they
--   are replaced by the new values. You can also use <tt>SET</tt> to add
--   or subtract from an attribute that is of type Number. For example:
--   <tt>SET myNum = myNum + :val</tt> <tt>SET</tt> supports the following
--   functions: * <tt>if_not_exists (path, operand)</tt> - if the item does
--   not contain an attribute at the specified path, then
--   <tt>if_not_exists</tt> evaluates to operand; otherwise, it evaluates
--   to path. You can use this function to avoid overwriting an attribute
--   that may already be present in the item. * <tt>list_append (operand,
--   operand)</tt> - evaluates to a list with a new element added to it.
--   You can append the new element to the start or the end of the list by
--   reversing the order of the operands. These function names are
--   case-sensitive. * <tt>REMOVE</tt> - Removes one or more attributes
--   from an item. * <tt>ADD</tt> - Adds the specified value to the item,
--   if the attribute does not already exist. If the attribute does exist,
--   then the behavior of <tt>ADD</tt> depends on the data type of the
--   attribute: * If the existing attribute is a number, and if
--   <i>Value</i> is also a number, then <i>Value</i> is mathematically
--   added to the existing attribute. If <i>Value</i> is a negative number,
--   then it is subtracted from the existing attribute. * If the existing
--   data type is a set and if <i>Value</i> is also a set, then
--   <i>Value</i> is added to the existing set. For example, if the
--   attribute value is the set <tt>[1,2]</tt> , and the <tt>ADD</tt>
--   action specified <tt>[3]</tt> , then the final attribute value is
--   <tt>[1,2,3]</tt> . An error occurs if an <tt>ADD</tt> action is
--   specified for a set attribute and the attribute type specified does
--   not match the existing set type. Both sets must have the same
--   primitive data type. For example, if the existing data type is a set
--   of strings, the <i>Value</i> must also be a set of strings.
--   <i>Important:</i> The <tt>ADD</tt> action only supports Number and set
--   data types. In addition, <tt>ADD</tt> can only be used on top-level
--   attributes, not nested attributes. * <tt>DELETE</tt> - Deletes an
--   element from a set. If a set of values is specified, then those values
--   are subtracted from the old set. For example, if the attribute value
--   was the set <tt>[a,b,c]</tt> and the <tt>DELETE</tt> action specifies
--   <tt>[a,c]</tt> , then the final attribute value is <tt>[b]</tt> .
--   Specifying an empty set is an error. <i>Important:</i> The
--   <tt>DELETE</tt> action only supports set data types. In addition,
--   <tt>DELETE</tt> can only be used on top-level attributes, not nested
--   attributes. You can have many actions in a single expression, such as
--   the following: <tt>SET a=:value1, b=:value2 DELETE :value3, :value4,
--   :value5</tt> For more information on update expressions, see
--   <a>Modifying Items and Attributes</a> in the <i>Amazon DynamoDB
--   Developer Guide</i> .</li>
--   <li><a>uiExpressionAttributeValues</a> - One or more values that can
--   be substituted in an expression. Use the <b>:</b> (colon) character in
--   an expression to dereference an attribute value. For example, suppose
--   that you wanted to check whether the value of the <i>ProductStatus</i>
--   attribute was one of the following: <tt>Available | Backordered |
--   Discontinued</tt> You would first need to specify
--   <i>ExpressionAttributeValues</i> as follows: <tt>{
--   ":avail":{<a>S</a>:<a>Available</a>},
--   ":back":{<a>S</a>:<a>Backordered</a>},
--   ":disc":{<a>S</a>:<a>Discontinued</a>} }</tt> You could then use these
--   values in an expression, such as this: <tt>ProductStatus IN (:avail,
--   :back, :disc)</tt> For more information on expression attribute
--   values, see <a>Specifying Conditions</a> in the <i>Amazon DynamoDB
--   Developer Guide</i> .</li>
--   <li><a>uiAttributeUpdates</a> - <i>Important:</i> This is a legacy
--   parameter, for backward compatibility. New applications should use
--   <i>UpdateExpression</i> instead. Do not combine legacy parameters and
--   expression parameters in a single API call; otherwise, DynamoDB will
--   return a <i>ValidationException</i> exception. This parameter can be
--   used for modifying top-level attributes; however, it does not support
--   individual list or map elements. The names of attributes to be
--   modified, the action to perform on each, and the new value for each.
--   If you are updating an attribute that is an index key attribute for
--   any indexes on that table, the attribute type must match the index key
--   type defined in the <i>AttributesDefinition</i> of the table
--   description. You can use <i>UpdateItem</i> to update any non-key
--   attributes. Attribute values cannot be null. String and Binary type
--   attributes must have lengths greater than zero. Set type attributes
--   must not be empty. Requests with empty values will be rejected with a
--   <i>ValidationException</i> exception. Each <i>AttributeUpdates</i>
--   element consists of an attribute name to modify, along with the
--   following: * <i>Value</i> - The new value, if applicable, for this
--   attribute. * <i>Action</i> - A value that specifies how to perform the
--   update. This action is only valid for an existing attribute whose data
--   type is Number or is a set; do not use <tt>ADD</tt> for other data
--   types. If an item with the specified primary key is found in the
--   table, the following values perform the following actions: *
--   <tt>PUT</tt> - Adds the specified attribute to the item. If the
--   attribute already exists, it is replaced by the new value. *
--   <tt>DELETE</tt> - Removes the attribute and its value, if no value is
--   specified for <tt>DELETE</tt> . The data type of the specified value
--   must match the existing value's data type. If a set of values is
--   specified, then those values are subtracted from the old set. For
--   example, if the attribute value was the set <tt>[a,b,c]</tt> and the
--   <tt>DELETE</tt> action specifies <tt>[a,c]</tt> , then the final
--   attribute value is <tt>[b]</tt> . Specifying an empty set is an error.
--   * <tt>ADD</tt> - Adds the specified value to the item, if the
--   attribute does not already exist. If the attribute does exist, then
--   the behavior of <tt>ADD</tt> depends on the data type of the
--   attribute: * If the existing attribute is a number, and if
--   <i>Value</i> is also a number, then <i>Value</i> is mathematically
--   added to the existing attribute. If <i>Value</i> is a negative number,
--   then it is subtracted from the existing attribute. * If the existing
--   data type is a set, and if <i>Value</i> is also a set, then
--   <i>Value</i> is appended to the existing set. For example, if the
--   attribute value is the set <tt>[1,2]</tt> , and the <tt>ADD</tt>
--   action specified <tt>[3]</tt> , then the final attribute value is
--   <tt>[1,2,3]</tt> . An error occurs if an <tt>ADD</tt> action is
--   specified for a set attribute and the attribute type specified does
--   not match the existing set type. Both sets must have the same
--   primitive data type. For example, if the existing data type is a set
--   of strings, <i>Value</i> must also be a set of strings. If no item
--   with the specified key is found in the table, the following values
--   perform the following actions: * <tt>PUT</tt> - Causes DynamoDB to
--   create a new item with the specified primary key, and then adds the
--   attribute. * <tt>DELETE</tt> - Nothing happens, because attributes
--   cannot be deleted from a nonexistent item. The operation succeeds, but
--   DynamoDB does not create a new item. * <tt>ADD</tt> - Causes DynamoDB
--   to create an item with the supplied primary key and number (or set of
--   numbers) for the attribute value. The only data types allowed are
--   Number and Number Set. If you provide any attributes that are part of
--   an index key, then the data types for those attributes must match
--   those of the schema in the table's attribute definition.</li>
--   <li><a>uiReturnConsumedCapacity</a> - Undocumented member.</li>
--   <li><a>uiReturnItemCollectionMetrics</a> - Determines whether item
--   collection metrics are returned. If set to <tt>SIZE</tt> , the
--   response includes statistics about item collections, if any, that were
--   modified during the operation are returned in the response. If set to
--   <tt>NONE</tt> (the default), no statistics are returned.</li>
--   <li><a>uiConditionExpression</a> - A condition that must be satisfied
--   in order for a conditional update to succeed. An expression can
--   contain any of the following: * Functions: <tt>attribute_exists |
--   attribute_not_exists | attribute_type | contains | begins_with |
--   size</tt> These function names are case-sensitive. * Comparison
--   operators: <tt>= | &lt;&gt; | &lt; | &gt; | &lt;= | &gt;= | BETWEEN |
--   IN</tt> * Logical operators: <tt>AND | OR | NOT</tt> For more
--   information on condition expressions, see <a>Specifying Conditions</a>
--   in the <i>Amazon DynamoDB Developer Guide</i> .</li>
--   <li><a>uiConditionalOperator</a> - <i>Important:</i> This is a legacy
--   parameter, for backward compatibility. New applications should use
--   <i>ConditionExpression</i> instead. Do not combine legacy parameters
--   and expression parameters in a single API call; otherwise, DynamoDB
--   will return a <i>ValidationException</i> exception. A logical operator
--   to apply to the conditions in the <i>Expected</i> map: * <tt>AND</tt>
--   - If all of the conditions evaluate to true, then the entire map
--   evaluates to true. * <tt>OR</tt> - If at least one of the conditions
--   evaluate to true, then the entire map evaluates to true. If you omit
--   <i>ConditionalOperator</i> , then <tt>AND</tt> is the default. The
--   operation will succeed only if the entire map evaluates to true.</li>
--   <li><a>uiExpected</a> - <i>Important:</i> This is a legacy parameter,
--   for backward compatibility. New applications should use
--   <i>ConditionExpression </i> instead. Do not combine legacy parameters
--   and expression parameters in a single API call; otherwise, DynamoDB
--   will return a <i>ValidationException</i> exception. A map of
--   attribute<i>condition pairs. </i>Expected<i> provides a conditional
--   block for the </i>UpdateItem<i> operation. Each element of
--   </i>Expected<i> consists of an attribute name, a comparison operator,
--   and one or more values. DynamoDB compares the attribute with the
--   value(s) you supplied, using the comparison operator. For each
--   </i>Expected<i> element, the result of the evaluation is either true
--   or false. If you specify more than one element in the </i>Expected<i>
--   map, then by default all of the conditions must evaluate to true. In
--   other words, the conditions are ANDed together. (You can use the
--   </i>ConditionalOperator<i> 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.) If the </i>Expected<i> map evaluates
--   to true, then the conditional operation succeeds; otherwise, it fails.
--   </i>Expected<i> contains the following: * </i>AttributeValueList<i> -
--   One or more values to evaluate against the supplied attribute. The
--   number of values in the list depends on the </i>ComparisonOperator<i>
--   being used. For type Number, value comparisons are numeric. String
--   value comparisons for greater than, equals, or less than are based on
--   ASCII character code values. For example, <tt>a</tt> is greater than
--   <tt>A</tt> , and <tt>a</tt> is greater than <tt>B</tt> . For a list of
--   code values, see
--   &lt;http:</i><i>en.wikipedia.org</i>wiki<i>ASCII#ASCII_printable_characters
--   http:</i><i>en.wikipedia.org</i>wiki<i>ASCII#ASCII_printable_characters&gt;
--   . For type Binary, DynamoDB treats each byte of the binary data as
--   unsigned when it compares binary values. * </i>ComparisonOperator<i> -
--   A comparator for evaluating attributes in the
--   </i>AttributeValueList<i> . When performing the comparison, DynamoDB
--   uses strongly consistent reads. The following comparison operators are
--   available: <tt>EQ | NE | LE | LT | GE | GT | NOT_NULL | NULL |
--   CONTAINS | NOT_CONTAINS | BEGINS_WITH | IN | BETWEEN</tt> The
--   following are descriptions of each comparison operator. * <tt>EQ</tt>
--   : Equal. <tt>EQ</tt> is supported for all datatypes, including lists
--   and maps. </i>AttributeValueList<i> can contain only one
--   </i>AttributeValue<i> element of type String, Number, Binary, String
--   Set, Number Set, or Binary Set. If an item contains an
--   </i>AttributeValue<i> element of a different type than the one
--   provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>NE</tt> : Not equal. <tt>NE</tt> is supported for
--   all datatypes, including lists and maps. </i>AttributeValueList<i> can
--   contain only one </i>AttributeValue<i> of type String, Number, Binary,
--   String Set, Number Set, or Binary Set. If an item contains an
--   </i>AttributeValue<i> of a different type than the one provided in the
--   request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LE</tt> : Less than or equal.
--   </i>AttributeValueList<i> can contain only one </i>AttributeValue<i>
--   element of type String, Number, or Binary (not a set type). If an item
--   contains an </i>AttributeValue<i> element of a different type than the
--   one provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LT</tt> : Less than. </i>AttributeValueList<i> can
--   contain only one </i>AttributeValue<i> of type String, Number, or
--   Binary (not a set type). If an item contains an </i>AttributeValue<i>
--   element of a different type than the one provided in the request, the
--   value does not match. For example, <tt>{<a>S</a>:"6"}</tt> does not
--   equal <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GE</tt> :
--   Greater than or equal. </i>AttributeValueList<i> can contain only one
--   </i>AttributeValue<i> element of type String, Number, or Binary (not a
--   set type). If an item contains an </i>AttributeValue<i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GT</tt> :
--   Greater than. </i>AttributeValueList<i> can contain only one
--   </i>AttributeValue<i> element of type String, Number, or Binary (not a
--   set type). If an item contains an </i>AttributeValue<i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>NOT_NULL</tt>
--   : The attribute exists. <tt>NOT_NULL</tt> is supported for all
--   datatypes, including lists and maps. * <tt>NULL</tt> : The attribute
--   does not exist. <tt>NULL</tt> is supported for all datatypes,
--   including lists and maps. * <tt>CONTAINS</tt> : Checks for a
--   subsequence, or value in a set. </i>AttributeValueList<i> can contain
--   only one </i>AttributeValue<i> element of type String, Number, or
--   Binary (not a set type). If the target attribute of the comparison is
--   of type String, then the operator checks for a substring match. If the
--   target attribute of the comparison is of type Binary, then the
--   operator looks for a subsequence of the target that matches the input.
--   If the target attribute of the comparison is a set ("<tt>SS</tt> ",
--   "<tt>NS</tt> ", or "<tt>BS</tt> "), then the operator evaluates to
--   true if it finds an exact match with any member of the set. CONTAINS
--   is supported for lists: When evaluating "<tt>a CONTAINS b</tt> ",
--   "<tt>a</tt> " can be a list; however, "<tt>b</tt> " cannot be a set, a
--   map, or a list. * <tt>NOT_CONTAINS</tt> : Checks for absence of a
--   subsequence, or absence of a value in a set. </i>AttributeValueList<i>
--   can contain only one </i>AttributeValue<i> element of type String,
--   Number, or Binary (not a set type). If the target attribute of the
--   comparison is a String, then the operator checks for the absence of a
--   substring match. If the target attribute of the comparison is Binary,
--   then the operator checks for the absence of a subsequence of the
--   target that matches the input. If the target attribute of the
--   comparison is a set ("<tt>SS</tt> ", "<tt>NS</tt> ", or "<tt>BS</tt>
--   "), then the operator evaluates to true if it </i>does not<i> find an
--   exact match with any member of the set. NOT_CONTAINS is supported for
--   lists: When evaluating "<tt>a NOT CONTAINS b</tt> ", "<tt>a</tt> " can
--   be a list; however, "<tt>b</tt> " cannot be a set, a map, or a list. *
--   <tt>BEGINS_WITH</tt> : Checks for a prefix. </i>AttributeValueList<i>
--   can contain only one </i>AttributeValue<i> of type String or Binary
--   (not a Number or a set type). The target attribute of the comparison
--   must be of type String or Binary (not a Number or a set type). *
--   <tt>IN</tt> : Checks for matching elements within two sets.
--   </i>AttributeValueList<i> can contain one or more
--   </i>AttributeValue<i> elements of type String, Number, or Binary (not
--   a set type). These attributes are compared against an existing set
--   type attribute of an item. If any elements of the input set are
--   present in the item attribute, the expression evaluates to true. *
--   <tt>BETWEEN</tt> : Greater than or equal to the first value, and less
--   than or equal to the second value. </i>AttributeValueList<i> must
--   contain two </i>AttributeValue<i> elements of the same type, either
--   String, Number, or Binary (not a set type). A target attribute matches
--   if the target value is greater than, or equal to, the first element
--   and less than, or equal to, the second element. If an item contains an
--   </i>AttributeValue<i> element of a different type than the one
--   provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not compare to <tt>{<a>N</a>:"6"}</tt> .
--   Also, <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6",
--   "2", "1"]}</tt> For usage examples of </i>AttributeValueList<i> and
--   </i>ComparisonOperator<i> , see
--   &lt;http:</i><i>docs.aws.amazon.com</i>amazondynamodb<i>latest</i>developerguide<i>LegacyConditionalParameters.html
--   Legacy Conditional Parameters&gt; in the </i>Amazon DynamoDB Developer
--   Guide<i> . For backward compatibility with previous DynamoDB releases,
--   the following parameters can be used instead of
--   </i>AttributeValueList<i> and </i>ComparisonOperator<i> : *
--   </i>Value<i> - A value for DynamoDB to compare with an attribute. *
--   </i>Exists<i> - A Boolean value that causes DynamoDB to evaluate the
--   value before attempting the conditional operation: * If </i>Exists<i>
--   is <tt>true</tt> , DynamoDB will check to see if that attribute value
--   already exists in the table. If it is found, then the condition
--   evaluates to true; otherwise the condition evaluate to false. * If
--   </i>Exists<i> is <tt>false</tt> , DynamoDB assumes that the attribute
--   value does </i>not<i> exist in the table. If in fact the value does
--   not exist, then the assumption is valid and the condition evaluates to
--   true. If the value is found, despite the assumption that it does not
--   exist, the condition evaluates to false. Note that the default value
--   for </i>Exists<i> is <tt>true</tt> . The </i>Value<i> and
--   </i>Exists<i> parameters are incompatible with
--   </i>AttributeValueList<i> and </i>ComparisonOperator<i> . Note that if
--   you use both sets of parameters at once, DynamoDB will return a
--   </i>ValidationException/ exception.</li>
--   <li><a>uiTableName</a> - The name of the table containing the item to
--   update.</li>
--   <li><a>uiKey</a> - The primary key of the item to be updated. Each
--   element consists of an attribute name and a value for that attribute.
--   For the primary key, you must provide all of the attributes. For
--   example, with a simple primary key, you only need to provide a value
--   for the partition key. For a composite primary key, you must provide
--   values for both the partition key and the sort key.</li>
--   </ul>
updateItem :: Text -> UpdateItem

-- | Represents the input of an <i>UpdateItem</i> operation.
--   
--   <i>See:</i> <a>updateItem</a> smart constructor.
data UpdateItem

-- | One or more substitution tokens for attribute names in an expression.
--   The following are some use cases for using
--   <i>ExpressionAttributeNames</i> : * To access an attribute whose name
--   conflicts with a DynamoDB reserved word. * To create a placeholder for
--   repeating occurrences of an attribute name in an expression. * To
--   prevent special characters in an attribute name from being
--   misinterpreted in an expression. Use the <b>#</b> character in an
--   expression to dereference an attribute name. For example, consider the
--   following attribute name: * <tt>Percentile</tt> The name of this
--   attribute conflicts with a reserved word, so it cannot be used
--   directly in an expression. (For the complete list of reserved words,
--   see <a>Reserved Words</a> in the <i>Amazon DynamoDB Developer
--   Guide</i> ). To work around this, you could specify the following for
--   <i>ExpressionAttributeNames</i> : * <tt>{"#P":<a>Percentile</a>}</tt>
--   You could then use this substitution in an expression, as in this
--   example: * <tt>#P = :val</tt> For more information on expression
--   attribute names, see <a>Accessing Item Attributes</a> in the <i>Amazon
--   DynamoDB Developer Guide</i> .
uiExpressionAttributeNames :: Lens' UpdateItem (HashMap Text Text)

-- | Use <i>ReturnValues</i> if you want to get the item attributes as they
--   appeared either before or after they were updated. For
--   <i>UpdateItem</i> , the valid values are: * <tt>NONE</tt> - If
--   <i>ReturnValues</i> is not specified, or if its value is <tt>NONE</tt>
--   , then nothing is returned. (This setting is the default for
--   <i>ReturnValues</i> .) * <tt>ALL_OLD</tt> - If <i>UpdateItem</i>
--   overwrote an attribute name-value pair, then the content of the old
--   item is returned. * <tt>UPDATED_OLD</tt> - The old versions of only
--   the updated attributes are returned. * <tt>ALL_NEW</tt> - All of the
--   attributes of the new version of the item are returned. *
--   <tt>UPDATED_NEW</tt> - The new versions of only the updated attributes
--   are returned. There is no additional cost associated with requesting a
--   return value aside from the small network and processing overhead of
--   receiving a larger response. No Read Capacity Units are consumed.
--   Values returned are strongly consistent
uiReturnValues :: Lens' UpdateItem (Maybe ReturnValue)

-- | An expression that defines one or more attributes to be updated, the
--   action to be performed on them, and new value(s) for them. The
--   following action values are available for <i>UpdateExpression</i> . *
--   <tt>SET</tt> - Adds one or more attributes and values to an item. If
--   any of these attribute already exist, they are replaced by the new
--   values. You can also use <tt>SET</tt> to add or subtract from an
--   attribute that is of type Number. For example: <tt>SET myNum = myNum +
--   :val</tt> <tt>SET</tt> supports the following functions: *
--   <tt>if_not_exists (path, operand)</tt> - if the item does not contain
--   an attribute at the specified path, then <tt>if_not_exists</tt>
--   evaluates to operand; otherwise, it evaluates to path. You can use
--   this function to avoid overwriting an attribute that may already be
--   present in the item. * <tt>list_append (operand, operand)</tt> -
--   evaluates to a list with a new element added to it. You can append the
--   new element to the start or the end of the list by reversing the order
--   of the operands. These function names are case-sensitive. *
--   <tt>REMOVE</tt> - Removes one or more attributes from an item. *
--   <tt>ADD</tt> - Adds the specified value to the item, if the attribute
--   does not already exist. If the attribute does exist, then the behavior
--   of <tt>ADD</tt> depends on the data type of the attribute: * If the
--   existing attribute is a number, and if <i>Value</i> is also a number,
--   then <i>Value</i> is mathematically added to the existing attribute.
--   If <i>Value</i> is a negative number, then it is subtracted from the
--   existing attribute. * If the existing data type is a set and if
--   <i>Value</i> is also a set, then <i>Value</i> is added to the existing
--   set. For example, if the attribute value is the set <tt>[1,2]</tt> ,
--   and the <tt>ADD</tt> action specified <tt>[3]</tt> , then the final
--   attribute value is <tt>[1,2,3]</tt> . An error occurs if an
--   <tt>ADD</tt> action is specified for a set attribute and the attribute
--   type specified does not match the existing set type. Both sets must
--   have the same primitive data type. For example, if the existing data
--   type is a set of strings, the <i>Value</i> must also be a set of
--   strings. <i>Important:</i> The <tt>ADD</tt> action only supports
--   Number and set data types. In addition, <tt>ADD</tt> can only be used
--   on top-level attributes, not nested attributes. * <tt>DELETE</tt> -
--   Deletes an element from a set. If a set of values is specified, then
--   those values are subtracted from the old set. For example, if the
--   attribute value was the set <tt>[a,b,c]</tt> and the <tt>DELETE</tt>
--   action specifies <tt>[a,c]</tt> , then the final attribute value is
--   <tt>[b]</tt> . Specifying an empty set is an error. <i>Important:</i>
--   The <tt>DELETE</tt> action only supports set data types. In addition,
--   <tt>DELETE</tt> can only be used on top-level attributes, not nested
--   attributes. You can have many actions in a single expression, such as
--   the following: <tt>SET a=:value1, b=:value2 DELETE :value3, :value4,
--   :value5</tt> For more information on update expressions, see
--   <a>Modifying Items and Attributes</a> in the <i>Amazon DynamoDB
--   Developer Guide</i> .
uiUpdateExpression :: Lens' UpdateItem (Maybe Text)

-- | One or more values that can be substituted in an expression. Use the
--   <b>:</b> (colon) character in an expression to dereference an
--   attribute value. For example, suppose that you wanted to check whether
--   the value of the <i>ProductStatus</i> attribute was one of the
--   following: <tt>Available | Backordered | Discontinued</tt> You would
--   first need to specify <i>ExpressionAttributeValues</i> as follows:
--   <tt>{ ":avail":{<a>S</a>:<a>Available</a>},
--   ":back":{<a>S</a>:<a>Backordered</a>},
--   ":disc":{<a>S</a>:<a>Discontinued</a>} }</tt> You could then use these
--   values in an expression, such as this: <tt>ProductStatus IN (:avail,
--   :back, :disc)</tt> For more information on expression attribute
--   values, see <a>Specifying Conditions</a> in the <i>Amazon DynamoDB
--   Developer Guide</i> .
uiExpressionAttributeValues :: Lens' UpdateItem (HashMap Text AttributeValue)

-- | <i>Important:</i> This is a legacy parameter, for backward
--   compatibility. New applications should use <i>UpdateExpression</i>
--   instead. Do not combine legacy parameters and expression parameters in
--   a single API call; otherwise, DynamoDB will return a
--   <i>ValidationException</i> exception. This parameter can be used for
--   modifying top-level attributes; however, it does not support
--   individual list or map elements. The names of attributes to be
--   modified, the action to perform on each, and the new value for each.
--   If you are updating an attribute that is an index key attribute for
--   any indexes on that table, the attribute type must match the index key
--   type defined in the <i>AttributesDefinition</i> of the table
--   description. You can use <i>UpdateItem</i> to update any non-key
--   attributes. Attribute values cannot be null. String and Binary type
--   attributes must have lengths greater than zero. Set type attributes
--   must not be empty. Requests with empty values will be rejected with a
--   <i>ValidationException</i> exception. Each <i>AttributeUpdates</i>
--   element consists of an attribute name to modify, along with the
--   following: * <i>Value</i> - The new value, if applicable, for this
--   attribute. * <i>Action</i> - A value that specifies how to perform the
--   update. This action is only valid for an existing attribute whose data
--   type is Number or is a set; do not use <tt>ADD</tt> for other data
--   types. If an item with the specified primary key is found in the
--   table, the following values perform the following actions: *
--   <tt>PUT</tt> - Adds the specified attribute to the item. If the
--   attribute already exists, it is replaced by the new value. *
--   <tt>DELETE</tt> - Removes the attribute and its value, if no value is
--   specified for <tt>DELETE</tt> . The data type of the specified value
--   must match the existing value's data type. If a set of values is
--   specified, then those values are subtracted from the old set. For
--   example, if the attribute value was the set <tt>[a,b,c]</tt> and the
--   <tt>DELETE</tt> action specifies <tt>[a,c]</tt> , then the final
--   attribute value is <tt>[b]</tt> . Specifying an empty set is an error.
--   * <tt>ADD</tt> - Adds the specified value to the item, if the
--   attribute does not already exist. If the attribute does exist, then
--   the behavior of <tt>ADD</tt> depends on the data type of the
--   attribute: * If the existing attribute is a number, and if
--   <i>Value</i> is also a number, then <i>Value</i> is mathematically
--   added to the existing attribute. If <i>Value</i> is a negative number,
--   then it is subtracted from the existing attribute. * If the existing
--   data type is a set, and if <i>Value</i> is also a set, then
--   <i>Value</i> is appended to the existing set. For example, if the
--   attribute value is the set <tt>[1,2]</tt> , and the <tt>ADD</tt>
--   action specified <tt>[3]</tt> , then the final attribute value is
--   <tt>[1,2,3]</tt> . An error occurs if an <tt>ADD</tt> action is
--   specified for a set attribute and the attribute type specified does
--   not match the existing set type. Both sets must have the same
--   primitive data type. For example, if the existing data type is a set
--   of strings, <i>Value</i> must also be a set of strings. If no item
--   with the specified key is found in the table, the following values
--   perform the following actions: * <tt>PUT</tt> - Causes DynamoDB to
--   create a new item with the specified primary key, and then adds the
--   attribute. * <tt>DELETE</tt> - Nothing happens, because attributes
--   cannot be deleted from a nonexistent item. The operation succeeds, but
--   DynamoDB does not create a new item. * <tt>ADD</tt> - Causes DynamoDB
--   to create an item with the supplied primary key and number (or set of
--   numbers) for the attribute value. The only data types allowed are
--   Number and Number Set. If you provide any attributes that are part of
--   an index key, then the data types for those attributes must match
--   those of the schema in the table's attribute definition.
uiAttributeUpdates :: Lens' UpdateItem (HashMap Text AttributeValueUpdate)

-- | Undocumented member.
uiReturnConsumedCapacity :: Lens' UpdateItem (Maybe ReturnConsumedCapacity)

-- | Determines whether item collection metrics are returned. If set to
--   <tt>SIZE</tt> , the response includes statistics about item
--   collections, if any, that were modified during the operation are
--   returned in the response. If set to <tt>NONE</tt> (the default), no
--   statistics are returned.
uiReturnItemCollectionMetrics :: Lens' UpdateItem (Maybe ReturnItemCollectionMetrics)

-- | A condition that must be satisfied in order for a conditional update
--   to succeed. An expression can contain any of the following: *
--   Functions: <tt>attribute_exists | attribute_not_exists |
--   attribute_type | contains | begins_with | size</tt> These function
--   names are case-sensitive. * Comparison operators: <tt>= | &lt;&gt; |
--   &lt; | &gt; | &lt;= | &gt;= | BETWEEN | IN</tt> * Logical operators:
--   <tt>AND | OR | NOT</tt> For more information on condition expressions,
--   see <a>Specifying Conditions</a> in the <i>Amazon DynamoDB Developer
--   Guide</i> .
uiConditionExpression :: Lens' UpdateItem (Maybe Text)

-- | <i>Important:</i> This is a legacy parameter, for backward
--   compatibility. New applications should use <i>ConditionExpression</i>
--   instead. Do not combine legacy parameters and expression parameters in
--   a single API call; otherwise, DynamoDB will return a
--   <i>ValidationException</i> exception. A logical operator to apply to
--   the conditions in the <i>Expected</i> map: * <tt>AND</tt> - If all of
--   the conditions evaluate to true, then the entire map evaluates to
--   true. * <tt>OR</tt> - If at least one of the conditions evaluate to
--   true, then the entire map evaluates to true. If you omit
--   <i>ConditionalOperator</i> , then <tt>AND</tt> is the default. The
--   operation will succeed only if the entire map evaluates to true.
uiConditionalOperator :: Lens' UpdateItem (Maybe ConditionalOperator)

-- | <i>Important:</i> This is a legacy parameter, for backward
--   compatibility. New applications should use <i>ConditionExpression </i>
--   instead. Do not combine legacy parameters and expression parameters in
--   a single API call; otherwise, DynamoDB will return a
--   <i>ValidationException</i> exception. A map of attribute<i>condition
--   pairs. </i>Expected<i> provides a conditional block for the
--   </i>UpdateItem<i> operation. Each element of </i>Expected<i> consists
--   of an attribute name, a comparison operator, and one or more values.
--   DynamoDB compares the attribute with the value(s) you supplied, using
--   the comparison operator. For each </i>Expected<i> element, the result
--   of the evaluation is either true or false. If you specify more than
--   one element in the </i>Expected<i> map, then by default all of the
--   conditions must evaluate to true. In other words, the conditions are
--   ANDed together. (You can use the </i>ConditionalOperator<i> 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.) If the
--   </i>Expected<i> map evaluates to true, then the conditional operation
--   succeeds; otherwise, it fails. </i>Expected<i> contains the following:
--   * </i>AttributeValueList<i> - One or more values to evaluate against
--   the supplied attribute. The number of values in the list depends on
--   the </i>ComparisonOperator<i> being used. For type Number, value
--   comparisons are numeric. String value comparisons for greater than,
--   equals, or less than are based on ASCII character code values. For
--   example, <tt>a</tt> is greater than <tt>A</tt> , and <tt>a</tt> is
--   greater than <tt>B</tt> . For a list of code values, see
--   &lt;http:</i><i>en.wikipedia.org</i>wiki<i>ASCII#ASCII_printable_characters
--   http:</i><i>en.wikipedia.org</i>wiki<i>ASCII#ASCII_printable_characters&gt;
--   . For type Binary, DynamoDB treats each byte of the binary data as
--   unsigned when it compares binary values. * </i>ComparisonOperator<i> -
--   A comparator for evaluating attributes in the
--   </i>AttributeValueList<i> . When performing the comparison, DynamoDB
--   uses strongly consistent reads. The following comparison operators are
--   available: <tt>EQ | NE | LE | LT | GE | GT | NOT_NULL | NULL |
--   CONTAINS | NOT_CONTAINS | BEGINS_WITH | IN | BETWEEN</tt> The
--   following are descriptions of each comparison operator. * <tt>EQ</tt>
--   : Equal. <tt>EQ</tt> is supported for all datatypes, including lists
--   and maps. </i>AttributeValueList<i> can contain only one
--   </i>AttributeValue<i> element of type String, Number, Binary, String
--   Set, Number Set, or Binary Set. If an item contains an
--   </i>AttributeValue<i> element of a different type than the one
--   provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>NE</tt> : Not equal. <tt>NE</tt> is supported for
--   all datatypes, including lists and maps. </i>AttributeValueList<i> can
--   contain only one </i>AttributeValue<i> of type String, Number, Binary,
--   String Set, Number Set, or Binary Set. If an item contains an
--   </i>AttributeValue<i> of a different type than the one provided in the
--   request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LE</tt> : Less than or equal.
--   </i>AttributeValueList<i> can contain only one </i>AttributeValue<i>
--   element of type String, Number, or Binary (not a set type). If an item
--   contains an </i>AttributeValue<i> element of a different type than the
--   one provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LT</tt> : Less than. </i>AttributeValueList<i> can
--   contain only one </i>AttributeValue<i> of type String, Number, or
--   Binary (not a set type). If an item contains an </i>AttributeValue<i>
--   element of a different type than the one provided in the request, the
--   value does not match. For example, <tt>{<a>S</a>:"6"}</tt> does not
--   equal <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GE</tt> :
--   Greater than or equal. </i>AttributeValueList<i> can contain only one
--   </i>AttributeValue<i> element of type String, Number, or Binary (not a
--   set type). If an item contains an </i>AttributeValue<i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GT</tt> :
--   Greater than. </i>AttributeValueList<i> can contain only one
--   </i>AttributeValue<i> element of type String, Number, or Binary (not a
--   set type). If an item contains an </i>AttributeValue<i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>NOT_NULL</tt>
--   : The attribute exists. <tt>NOT_NULL</tt> is supported for all
--   datatypes, including lists and maps. * <tt>NULL</tt> : The attribute
--   does not exist. <tt>NULL</tt> is supported for all datatypes,
--   including lists and maps. * <tt>CONTAINS</tt> : Checks for a
--   subsequence, or value in a set. </i>AttributeValueList<i> can contain
--   only one </i>AttributeValue<i> element of type String, Number, or
--   Binary (not a set type). If the target attribute of the comparison is
--   of type String, then the operator checks for a substring match. If the
--   target attribute of the comparison is of type Binary, then the
--   operator looks for a subsequence of the target that matches the input.
--   If the target attribute of the comparison is a set ("<tt>SS</tt> ",
--   "<tt>NS</tt> ", or "<tt>BS</tt> "), then the operator evaluates to
--   true if it finds an exact match with any member of the set. CONTAINS
--   is supported for lists: When evaluating "<tt>a CONTAINS b</tt> ",
--   "<tt>a</tt> " can be a list; however, "<tt>b</tt> " cannot be a set, a
--   map, or a list. * <tt>NOT_CONTAINS</tt> : Checks for absence of a
--   subsequence, or absence of a value in a set. </i>AttributeValueList<i>
--   can contain only one </i>AttributeValue<i> element of type String,
--   Number, or Binary (not a set type). If the target attribute of the
--   comparison is a String, then the operator checks for the absence of a
--   substring match. If the target attribute of the comparison is Binary,
--   then the operator checks for the absence of a subsequence of the
--   target that matches the input. If the target attribute of the
--   comparison is a set ("<tt>SS</tt> ", "<tt>NS</tt> ", or "<tt>BS</tt>
--   "), then the operator evaluates to true if it </i>does not<i> find an
--   exact match with any member of the set. NOT_CONTAINS is supported for
--   lists: When evaluating "<tt>a NOT CONTAINS b</tt> ", "<tt>a</tt> " can
--   be a list; however, "<tt>b</tt> " cannot be a set, a map, or a list. *
--   <tt>BEGINS_WITH</tt> : Checks for a prefix. </i>AttributeValueList<i>
--   can contain only one </i>AttributeValue<i> of type String or Binary
--   (not a Number or a set type). The target attribute of the comparison
--   must be of type String or Binary (not a Number or a set type). *
--   <tt>IN</tt> : Checks for matching elements within two sets.
--   </i>AttributeValueList<i> can contain one or more
--   </i>AttributeValue<i> elements of type String, Number, or Binary (not
--   a set type). These attributes are compared against an existing set
--   type attribute of an item. If any elements of the input set are
--   present in the item attribute, the expression evaluates to true. *
--   <tt>BETWEEN</tt> : Greater than or equal to the first value, and less
--   than or equal to the second value. </i>AttributeValueList<i> must
--   contain two </i>AttributeValue<i> elements of the same type, either
--   String, Number, or Binary (not a set type). A target attribute matches
--   if the target value is greater than, or equal to, the first element
--   and less than, or equal to, the second element. If an item contains an
--   </i>AttributeValue<i> element of a different type than the one
--   provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not compare to <tt>{<a>N</a>:"6"}</tt> .
--   Also, <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6",
--   "2", "1"]}</tt> For usage examples of </i>AttributeValueList<i> and
--   </i>ComparisonOperator<i> , see
--   &lt;http:</i><i>docs.aws.amazon.com</i>amazondynamodb<i>latest</i>developerguide<i>LegacyConditionalParameters.html
--   Legacy Conditional Parameters&gt; in the </i>Amazon DynamoDB Developer
--   Guide<i> . For backward compatibility with previous DynamoDB releases,
--   the following parameters can be used instead of
--   </i>AttributeValueList<i> and </i>ComparisonOperator<i> : *
--   </i>Value<i> - A value for DynamoDB to compare with an attribute. *
--   </i>Exists<i> - A Boolean value that causes DynamoDB to evaluate the
--   value before attempting the conditional operation: * If </i>Exists<i>
--   is <tt>true</tt> , DynamoDB will check to see if that attribute value
--   already exists in the table. If it is found, then the condition
--   evaluates to true; otherwise the condition evaluate to false. * If
--   </i>Exists<i> is <tt>false</tt> , DynamoDB assumes that the attribute
--   value does </i>not<i> exist in the table. If in fact the value does
--   not exist, then the assumption is valid and the condition evaluates to
--   true. If the value is found, despite the assumption that it does not
--   exist, the condition evaluates to false. Note that the default value
--   for </i>Exists<i> is <tt>true</tt> . The </i>Value<i> and
--   </i>Exists<i> parameters are incompatible with
--   </i>AttributeValueList<i> and </i>ComparisonOperator<i> . Note that if
--   you use both sets of parameters at once, DynamoDB will return a
--   </i>ValidationException/ exception.
uiExpected :: Lens' UpdateItem (HashMap Text ExpectedAttributeValue)

-- | The name of the table containing the item to update.
uiTableName :: Lens' UpdateItem Text

-- | The primary key of the item to be updated. Each element consists of an
--   attribute name and a value for that attribute. For the primary key,
--   you must provide all of the attributes. For example, with a simple
--   primary key, you only need to provide a value for the partition key.
--   For a composite primary key, you must provide values for both the
--   partition key and the sort key.
uiKey :: Lens' UpdateItem (HashMap Text AttributeValue)

-- | Creates a value of <a>UpdateItemResponse</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>uirsItemCollectionMetrics</a> - Undocumented member.</li>
--   <li><a>uirsConsumedCapacity</a> - Undocumented member.</li>
--   <li><a>uirsAttributes</a> - A map of attribute values as they appeared
--   before the <i>UpdateItem</i> operation. This map only appears if
--   <i>ReturnValues</i> was specified as something other than
--   <tt>NONE</tt> in the request. Each element represents one
--   attribute.</li>
--   <li><a>uirsResponseStatus</a> - -- | The response status code.</li>
--   </ul>
updateItemResponse :: Int -> UpdateItemResponse

-- | Represents the output of an <i>UpdateItem</i> operation.
--   
--   <i>See:</i> <a>updateItemResponse</a> smart constructor.
data UpdateItemResponse

-- | Undocumented member.
uirsItemCollectionMetrics :: Lens' UpdateItemResponse (Maybe ItemCollectionMetrics)

-- | Undocumented member.
uirsConsumedCapacity :: Lens' UpdateItemResponse (Maybe ConsumedCapacity)

-- | A map of attribute values as they appeared before the
--   <i>UpdateItem</i> operation. This map only appears if
--   <i>ReturnValues</i> was specified as something other than
--   <tt>NONE</tt> in the request. Each element represents one attribute.
uirsAttributes :: Lens' UpdateItemResponse (HashMap Text AttributeValue)

-- | <ul>
--   <li>- | The response status code.</li>
--   </ul>
uirsResponseStatus :: Lens' UpdateItemResponse Int
instance GHC.Generics.Generic Network.AWS.DynamoDB.UpdateItem.UpdateItemResponse
instance Data.Data.Data Network.AWS.DynamoDB.UpdateItem.UpdateItemResponse
instance GHC.Show.Show Network.AWS.DynamoDB.UpdateItem.UpdateItemResponse
instance GHC.Read.Read Network.AWS.DynamoDB.UpdateItem.UpdateItemResponse
instance GHC.Classes.Eq Network.AWS.DynamoDB.UpdateItem.UpdateItemResponse
instance GHC.Generics.Generic Network.AWS.DynamoDB.UpdateItem.UpdateItem
instance Data.Data.Data Network.AWS.DynamoDB.UpdateItem.UpdateItem
instance GHC.Show.Show Network.AWS.DynamoDB.UpdateItem.UpdateItem
instance GHC.Read.Read Network.AWS.DynamoDB.UpdateItem.UpdateItem
instance GHC.Classes.Eq Network.AWS.DynamoDB.UpdateItem.UpdateItem
instance Network.AWS.Types.AWSRequest Network.AWS.DynamoDB.UpdateItem.UpdateItem
instance Data.Hashable.Class.Hashable Network.AWS.DynamoDB.UpdateItem.UpdateItem
instance Control.DeepSeq.NFData Network.AWS.DynamoDB.UpdateItem.UpdateItem
instance Network.AWS.Data.Headers.ToHeaders Network.AWS.DynamoDB.UpdateItem.UpdateItem
instance Data.Aeson.Types.ToJSON.ToJSON Network.AWS.DynamoDB.UpdateItem.UpdateItem
instance Network.AWS.Data.Path.ToPath Network.AWS.DynamoDB.UpdateItem.UpdateItem
instance Network.AWS.Data.Query.ToQuery Network.AWS.DynamoDB.UpdateItem.UpdateItem
instance Control.DeepSeq.NFData Network.AWS.DynamoDB.UpdateItem.UpdateItemResponse


-- | Modifies the provisioned throughput settings, global secondary
--   indexes, or DynamoDB Streams settings for a given table.
--   
--   You can only perform one of the following operations at once:
--   
--   <ul>
--   <li>Modify the provisioned throughput settings of the table.</li>
--   <li>Enable or disable Streams on the table.</li>
--   <li>Remove a global secondary index from the table.</li>
--   <li>Create a new global secondary index on the table. Once the index
--   begins backfilling, you can use <i>UpdateTable</i> to perform other
--   operations.</li>
--   </ul>
--   
--   <i>UpdateTable</i> is an asynchronous operation; while it is
--   executing, the table status changes from <tt>ACTIVE</tt> to
--   <tt>UPDATING</tt> . While it is <tt>UPDATING</tt> , you cannot issue
--   another <i>UpdateTable</i> request. When the table returns to the
--   <tt>ACTIVE</tt> state, the <i>UpdateTable</i> operation is complete.
module Network.AWS.DynamoDB.UpdateTable

-- | Creates a value of <a>UpdateTable</a> with the minimum fields required
--   to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>utAttributeDefinitions</a> - An array of attributes that
--   describe the key schema for the table and indexes. If you are adding a
--   new global secondary index to the table, <i>AttributeDefinitions</i>
--   must include the key element(s) of the new index.</li>
--   <li><a>utProvisionedThroughput</a> - Undocumented member.</li>
--   <li><a>utGlobalSecondaryIndexUpdates</a> - An array of one or more
--   global secondary indexes for the table. For each index in the array,
--   you can request one action: * <i>Create</i> - add a new global
--   secondary index to the table. * <i>Update</i> - modify the provisioned
--   throughput settings of an existing global secondary index. *
--   <i>Delete</i> - remove a global secondary index from the table. For
--   more information, see <a>Managing Global Secondary Indexes</a> in the
--   <i>Amazon DynamoDB Developer Guide</i> .</li>
--   <li><a>utStreamSpecification</a> - Represents the DynamoDB Streams
--   configuration for the table.</li>
--   <li><a>utTableName</a> - The name of the table to be updated.</li>
--   </ul>
updateTable :: Text -> UpdateTable

-- | Represents the input of an <i>UpdateTable</i> operation.
--   
--   <i>See:</i> <a>updateTable</a> smart constructor.
data UpdateTable

-- | An array of attributes that describe the key schema for the table and
--   indexes. If you are adding a new global secondary index to the table,
--   <i>AttributeDefinitions</i> must include the key element(s) of the new
--   index.
utAttributeDefinitions :: Lens' UpdateTable [AttributeDefinition]

-- | Undocumented member.
utProvisionedThroughput :: Lens' UpdateTable (Maybe ProvisionedThroughput)

-- | An array of one or more global secondary indexes for the table. For
--   each index in the array, you can request one action: * <i>Create</i> -
--   add a new global secondary index to the table. * <i>Update</i> -
--   modify the provisioned throughput settings of an existing global
--   secondary index. * <i>Delete</i> - remove a global secondary index
--   from the table. For more information, see <a>Managing Global Secondary
--   Indexes</a> in the <i>Amazon DynamoDB Developer Guide</i> .
utGlobalSecondaryIndexUpdates :: Lens' UpdateTable [GlobalSecondaryIndexUpdate]

-- | Represents the DynamoDB Streams configuration for the table.
utStreamSpecification :: Lens' UpdateTable (Maybe StreamSpecification)

-- | The name of the table to be updated.
utTableName :: Lens' UpdateTable Text

-- | Creates a value of <a>UpdateTableResponse</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>utrsTableDescription</a> - Undocumented member.</li>
--   <li><a>utrsResponseStatus</a> - -- | The response status code.</li>
--   </ul>
updateTableResponse :: Int -> UpdateTableResponse

-- | Represents the output of an <i>UpdateTable</i> operation.
--   
--   <i>See:</i> <a>updateTableResponse</a> smart constructor.
data UpdateTableResponse

-- | Undocumented member.
utrsTableDescription :: Lens' UpdateTableResponse (Maybe TableDescription)

-- | <ul>
--   <li>- | The response status code.</li>
--   </ul>
utrsResponseStatus :: Lens' UpdateTableResponse Int
instance GHC.Generics.Generic Network.AWS.DynamoDB.UpdateTable.UpdateTableResponse
instance Data.Data.Data Network.AWS.DynamoDB.UpdateTable.UpdateTableResponse
instance GHC.Show.Show Network.AWS.DynamoDB.UpdateTable.UpdateTableResponse
instance GHC.Read.Read Network.AWS.DynamoDB.UpdateTable.UpdateTableResponse
instance GHC.Classes.Eq Network.AWS.DynamoDB.UpdateTable.UpdateTableResponse
instance GHC.Generics.Generic Network.AWS.DynamoDB.UpdateTable.UpdateTable
instance Data.Data.Data Network.AWS.DynamoDB.UpdateTable.UpdateTable
instance GHC.Show.Show Network.AWS.DynamoDB.UpdateTable.UpdateTable
instance GHC.Read.Read Network.AWS.DynamoDB.UpdateTable.UpdateTable
instance GHC.Classes.Eq Network.AWS.DynamoDB.UpdateTable.UpdateTable
instance Network.AWS.Types.AWSRequest Network.AWS.DynamoDB.UpdateTable.UpdateTable
instance Data.Hashable.Class.Hashable Network.AWS.DynamoDB.UpdateTable.UpdateTable
instance Control.DeepSeq.NFData Network.AWS.DynamoDB.UpdateTable.UpdateTable
instance Network.AWS.Data.Headers.ToHeaders Network.AWS.DynamoDB.UpdateTable.UpdateTable
instance Data.Aeson.Types.ToJSON.ToJSON Network.AWS.DynamoDB.UpdateTable.UpdateTable
instance Network.AWS.Data.Path.ToPath Network.AWS.DynamoDB.UpdateTable.UpdateTable
instance Network.AWS.Data.Query.ToQuery Network.AWS.DynamoDB.UpdateTable.UpdateTable
instance Control.DeepSeq.NFData Network.AWS.DynamoDB.UpdateTable.UpdateTableResponse


-- | The <i>Scan</i> operation returns one or more items and item
--   attributes by accessing every item in a table or a secondary index. To
--   have DynamoDB return fewer items, you can provide a <i>ScanFilter</i>
--   operation.
--   
--   If the total number of scanned items exceeds the maximum data set size
--   limit of 1 MB, the scan stops and results are returned to the user as
--   a <i>LastEvaluatedKey</i> value to continue the scan in a subsequent
--   operation. The results also include the number of items exceeding the
--   limit. A scan can result in no table data meeting the filter criteria.
--   
--   By default, <i>Scan</i> operations proceed sequentially; however, for
--   faster performance on a large table or secondary index, applications
--   can request a parallel <i>Scan</i> operation by providing the
--   <i>Segment</i> and <i>TotalSegments</i> parameters. For more
--   information, see <a>Parallel Scan</a> in the <i>Amazon DynamoDB
--   Developer Guide</i> .
--   
--   By default, <i>Scan</i> uses eventually consistent reads when
--   accessing the data in a table; therefore, the result set might not
--   include the changes to data in the table immediately before the
--   operation began. If you need a consistent copy of the data, as of the
--   time that the Scan begins, you can set the <i>ConsistentRead</i>
--   parameter to <i>true</i> .
--   
--   This operation returns paginated results.
module Network.AWS.DynamoDB.Scan

-- | Creates a value of <a>Scan</a> with the minimum fields required to
--   make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>sProjectionExpression</a> - A string that identifies one or
--   more attributes to retrieve from the specified table or index. These
--   attributes can include scalars, sets, or elements of a JSON document.
--   The attributes in the expression must be separated by commas. If no
--   attribute names are specified, then all attributes will be returned.
--   If any of the requested attributes are not found, they will not appear
--   in the result. For more information, see <a>Accessing Item
--   Attributes</a> in the <i>Amazon DynamoDB Developer Guide</i> .</li>
--   <li><a>sScanFilter</a> - <i>Important:</i> This is a legacy parameter,
--   for backward compatibility. New applications should use
--   <i>FilterExpression</i> instead. Do not combine legacy parameters and
--   expression parameters in a single API call; otherwise, DynamoDB will
--   return a <i>ValidationException</i> exception. A condition that
--   evaluates the scan results and returns only the desired values. If you
--   specify more than one condition in the <i>ScanFilter</i> map, then by
--   default all of the conditions must evaluate to true. In other words,
--   the conditions are ANDed together. (You can use the
--   <i>ConditionalOperator</i> 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.) Each <i>ScanFilter</i> element
--   consists of an attribute name to compare, along with the following: *
--   <i>AttributeValueList</i> - One or more values to evaluate against the
--   supplied attribute. The number of values in the list depends on the
--   operator specified in <i>ComparisonOperator</i> . For type Number,
--   value comparisons are numeric. String value comparisons for greater
--   than, equals, or less than are based on ASCII character code values.
--   For example, <tt>a</tt> is greater than <tt>A</tt> , and <tt>a</tt> is
--   greater than <tt>B</tt> . For a list of code values, see
--   <a>http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters</a> .
--   For 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 <a>JSON Data Format</a> in the <i>Amazon DynamoDB
--   Developer Guide</i> . * <i>ComparisonOperator</i> - A comparator for
--   evaluating attributes. For example, equals, greater than, less than,
--   etc. The following comparison operators are available: <tt>EQ | NE |
--   LE | LT | GE | GT | NOT_NULL | NULL | CONTAINS | NOT_CONTAINS |
--   BEGINS_WITH | IN | BETWEEN</tt> For complete descriptions of all
--   comparison operators, see <a>Condition</a> .</li>
--   <li><a>sAttributesToGet</a> - <i>Important:</i> This is a legacy
--   parameter, for backward compatibility. New applications should use
--   <i>ProjectionExpression</i> instead. Do not combine legacy parameters
--   and expression parameters in a single API call; otherwise, DynamoDB
--   will return a <i>ValidationException</i> exception. This parameter
--   allows you to retrieve attributes of type List or Map; however, it
--   cannot retrieve individual elements within a List or a Map. The names
--   of one or more attributes to retrieve. If no attribute names are
--   provided, then all attributes will be returned. If any of the
--   requested attributes are not found, they will not appear in the
--   result. Note that <i>AttributesToGet</i> has no effect on provisioned
--   throughput consumption. DynamoDB determines capacity units consumed
--   based on item size, not on the amount of data that is returned to an
--   application.</li>
--   <li><a>sTotalSegments</a> - For a parallel <i>Scan</i> request,
--   <i>TotalSegments</i> represents the total number of segments into
--   which the <i>Scan</i> operation will be divided. The value of
--   <i>TotalSegments</i> corresponds to the number of application workers
--   that will perform the parallel scan. For example, if you want to use
--   four application threads to scan a table or an index, specify a
--   <i>TotalSegments</i> value of 4. The value for <i>TotalSegments</i>
--   must be greater than or equal to 1, and less than or equal to 1000000.
--   If you specify a <i>TotalSegments</i> value of 1, the <i>Scan</i>
--   operation will be sequential rather than parallel. If you specify
--   <i>TotalSegments</i> , you must also specify <i>Segment</i> .</li>
--   <li><a>sExpressionAttributeNames</a> - One or more substitution tokens
--   for attribute names in an expression. The following are some use cases
--   for using <i>ExpressionAttributeNames</i> : * To access an attribute
--   whose name conflicts with a DynamoDB reserved word. * To create a
--   placeholder for repeating occurrences of an attribute name in an
--   expression. * To prevent special characters in an attribute name from
--   being misinterpreted in an expression. Use the <b>#</b> character in
--   an expression to dereference an attribute name. For example, consider
--   the following attribute name: * <tt>Percentile</tt> The name of this
--   attribute conflicts with a reserved word, so it cannot be used
--   directly in an expression. (For the complete list of reserved words,
--   see <a>Reserved Words</a> in the <i>Amazon DynamoDB Developer
--   Guide</i> ). To work around this, you could specify the following for
--   <i>ExpressionAttributeNames</i> : * <tt>{"#P":<a>Percentile</a>}</tt>
--   You could then use this substitution in an expression, as in this
--   example: * <tt>#P = :val</tt> For more information on expression
--   attribute names, see <a>Accessing Item Attributes</a> in the <i>Amazon
--   DynamoDB Developer Guide</i> .</li>
--   <li><a>sFilterExpression</a> - A string that contains conditions that
--   DynamoDB applies after the <i>Scan</i> operation, but before the data
--   is returned to you. Items that do not satisfy the
--   <i>FilterExpression</i> criteria are not returned. For more
--   information, see <a>Filter Expressions</a> in the <i>Amazon DynamoDB
--   Developer Guide</i> .</li>
--   <li><a>sConsistentRead</a> - A Boolean value that determines the read
--   consistency model during the scan: * If <i>ConsistentRead</i> is
--   <tt>false</tt> , then the data returned from <i>Scan</i> might not
--   contain the results from other recently completed write operations
--   (PutItem, UpdateItem or DeleteItem). * If <i>ConsistentRead</i> is
--   <tt>true</tt> , then all of the write operations that completed before
--   the <i>Scan</i> began are guaranteed to be contained in the
--   <i>Scan</i> response. The default setting for <i>ConsistentRead</i> is
--   <tt>false</tt> . The <i>ConsistentRead</i> parameter is not supported
--   on global secondary indexes. If you scan a global secondary index with
--   <i>ConsistentRead</i> set to true, you will receive a
--   <i>ValidationException</i> .</li>
--   <li><a>sExpressionAttributeValues</a> - One or more values that can be
--   substituted in an expression. Use the <b>:</b> (colon) character in an
--   expression to dereference an attribute value. For example, suppose
--   that you wanted to check whether the value of the <i>ProductStatus</i>
--   attribute was one of the following: <tt>Available | Backordered |
--   Discontinued</tt> You would first need to specify
--   <i>ExpressionAttributeValues</i> as follows: <tt>{
--   ":avail":{<a>S</a>:<a>Available</a>},
--   ":back":{<a>S</a>:<a>Backordered</a>},
--   ":disc":{<a>S</a>:<a>Discontinued</a>} }</tt> You could then use these
--   values in an expression, such as this: <tt>ProductStatus IN (:avail,
--   :back, :disc)</tt> For more information on expression attribute
--   values, see <a>Specifying Conditions</a> in the <i>Amazon DynamoDB
--   Developer Guide</i> .</li>
--   <li><a>sReturnConsumedCapacity</a> - Undocumented member.</li>
--   <li><a>sLimit</a> - The maximum number of items to evaluate (not
--   necessarily the number of matching items). If DynamoDB processes the
--   number of items up to the limit while processing the results, it stops
--   the operation and returns the matching values up to that point, and a
--   key in <i>LastEvaluatedKey</i> to apply in a subsequent operation, so
--   that you can pick up where you left off. Also, if the processed data
--   set size exceeds 1 MB before DynamoDB reaches this limit, it stops the
--   operation and returns the matching values up to the limit, and a key
--   in <i>LastEvaluatedKey</i> to apply in a subsequent operation to
--   continue the operation. For more information, see <a>Query and
--   Scan</a> in the <i>Amazon DynamoDB Developer Guide</i> .</li>
--   <li><a>sSelect</a> - The attributes to be returned in the result. You
--   can retrieve all item attributes, specific item attributes, or the
--   count of matching items. * <tt>ALL_ATTRIBUTES</tt> - Returns all of
--   the item attributes. * <tt>ALL_PROJECTED_ATTRIBUTES</tt> - Allowed
--   only when querying an index. Retrieves all attributes that have been
--   projected into the index. If the index is configured to project all
--   attributes, this return value is equivalent to specifying
--   <tt>ALL_ATTRIBUTES</tt> . * <tt>COUNT</tt> - Returns the number of
--   matching items, rather than the matching items themselves. *
--   <tt>SPECIFIC_ATTRIBUTES</tt> - Returns only the attributes listed in
--   <i>AttributesToGet</i> . This return value is equivalent to specifying
--   <i>AttributesToGet</i> without specifying any value for <i>Select</i>
--   . If neither <i>Select</i> nor <i>AttributesToGet</i> are specified,
--   DynamoDB defaults to <tt>ALL_ATTRIBUTES</tt> . You cannot use both
--   <i>AttributesToGet</i> and <i>Select</i> together in a single request,
--   unless the value for <i>Select</i> is <tt>SPECIFIC_ATTRIBUTES</tt> .
--   (This usage is equivalent to specifying <i>AttributesToGet</i> without
--   any value for <i>Select</i> .)</li>
--   <li><a>sSegment</a> - For a parallel <i>Scan</i> request,
--   <i>Segment</i> identifies an individual segment to be scanned by an
--   application worker. Segment IDs are zero-based, so the first segment
--   is always 0. For example, if you want to use four application threads
--   to scan a table or an index, then the first thread specifies a
--   <i>Segment</i> value of 0, the second thread specifies 1, and so on.
--   The value of <i>LastEvaluatedKey</i> returned from a parallel
--   <i>Scan</i> request must be used as <i>ExclusiveStartKey</i> with the
--   same segment ID in a subsequent <i>Scan</i> operation. The value for
--   <i>Segment</i> must be greater than or equal to 0, and less than the
--   value provided for <i>TotalSegments</i> . If you provide
--   <i>Segment</i> , you must also provide <i>TotalSegments</i> .</li>
--   <li><a>sConditionalOperator</a> - <i>Important:</i> This is a legacy
--   parameter, for backward compatibility. New applications should use
--   <i>FilterExpression</i> instead. Do not combine legacy parameters and
--   expression parameters in a single API call; otherwise, DynamoDB will
--   return a <i>ValidationException</i> exception. A logical operator to
--   apply to the conditions in a <i>ScanFilter</i> map: * <tt>AND</tt> -
--   If all of the conditions evaluate to true, then the entire map
--   evaluates to true. * <tt>OR</tt> - If at least one of the conditions
--   evaluate to true, then the entire map evaluates to true. If you omit
--   <i>ConditionalOperator</i> , then <tt>AND</tt> is the default. The
--   operation will succeed only if the entire map evaluates to true.</li>
--   <li><a>sExclusiveStartKey</a> - The primary key of the first item that
--   this operation will evaluate. Use the value that was returned for
--   <i>LastEvaluatedKey</i> in the previous operation. The data type for
--   <i>ExclusiveStartKey</i> must be String, Number or Binary. No set data
--   types are allowed. In a parallel scan, a <i>Scan</i> request that
--   includes <i>ExclusiveStartKey</i> must specify the same segment whose
--   previous <i>Scan</i> returned the corresponding value of
--   <i>LastEvaluatedKey</i> .</li>
--   <li><a>sIndexName</a> - The name of a secondary index to scan. This
--   index can be any local secondary index or global secondary index. Note
--   that if you use the <tt>IndexName</tt> parameter, you must also
--   provide <tt>TableName</tt> .</li>
--   <li><a>sTableName</a> - The name of the table containing the requested
--   items; or, if you provide <tt>IndexName</tt> , the name of the table
--   to which that index belongs.</li>
--   </ul>
scan :: Text -> Scan

-- | Represents the input of a <i>Scan</i> operation.
--   
--   <i>See:</i> <a>scan</a> smart constructor.
data Scan

-- | A string that identifies one or more attributes to retrieve from the
--   specified table or index. These attributes can include scalars, sets,
--   or elements of a JSON document. The attributes in the expression must
--   be separated by commas. If no attribute names are specified, then all
--   attributes will be returned. If any of the requested attributes are
--   not found, they will not appear in the result. For more information,
--   see <a>Accessing Item Attributes</a> in the <i>Amazon DynamoDB
--   Developer Guide</i> .
sProjectionExpression :: Lens' Scan (Maybe Text)

-- | <i>Important:</i> This is a legacy parameter, for backward
--   compatibility. New applications should use <i>FilterExpression</i>
--   instead. Do not combine legacy parameters and expression parameters in
--   a single API call; otherwise, DynamoDB will return a
--   <i>ValidationException</i> exception. A condition that evaluates the
--   scan results and returns only the desired values. If you specify more
--   than one condition in the <i>ScanFilter</i> map, then by default all
--   of the conditions must evaluate to true. In other words, the
--   conditions are ANDed together. (You can use the
--   <i>ConditionalOperator</i> 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.) Each <i>ScanFilter</i> element
--   consists of an attribute name to compare, along with the following: *
--   <i>AttributeValueList</i> - One or more values to evaluate against the
--   supplied attribute. The number of values in the list depends on the
--   operator specified in <i>ComparisonOperator</i> . For type Number,
--   value comparisons are numeric. String value comparisons for greater
--   than, equals, or less than are based on ASCII character code values.
--   For example, <tt>a</tt> is greater than <tt>A</tt> , and <tt>a</tt> is
--   greater than <tt>B</tt> . For a list of code values, see
--   <a>http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters</a> .
--   For 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 <a>JSON Data Format</a> in the <i>Amazon DynamoDB
--   Developer Guide</i> . * <i>ComparisonOperator</i> - A comparator for
--   evaluating attributes. For example, equals, greater than, less than,
--   etc. The following comparison operators are available: <tt>EQ | NE |
--   LE | LT | GE | GT | NOT_NULL | NULL | CONTAINS | NOT_CONTAINS |
--   BEGINS_WITH | IN | BETWEEN</tt> For complete descriptions of all
--   comparison operators, see <a>Condition</a> .
sScanFilter :: Lens' Scan (HashMap Text Condition)

-- | <i>Important:</i> This is a legacy parameter, for backward
--   compatibility. New applications should use <i>ProjectionExpression</i>
--   instead. Do not combine legacy parameters and expression parameters in
--   a single API call; otherwise, DynamoDB will return a
--   <i>ValidationException</i> exception. This parameter allows you to
--   retrieve attributes of type List or Map; however, it cannot retrieve
--   individual elements within a List or a Map. The names of one or more
--   attributes to retrieve. If no attribute names are provided, then all
--   attributes will be returned. If any of the requested attributes are
--   not found, they will not appear in the result. Note that
--   <i>AttributesToGet</i> has no effect on provisioned throughput
--   consumption. DynamoDB determines capacity units consumed based on item
--   size, not on the amount of data that is returned to an application.
sAttributesToGet :: Lens' Scan (Maybe (NonEmpty Text))

-- | For a parallel <i>Scan</i> request, <i>TotalSegments</i> represents
--   the total number of segments into which the <i>Scan</i> operation will
--   be divided. The value of <i>TotalSegments</i> corresponds to the
--   number of application workers that will perform the parallel scan. For
--   example, if you want to use four application threads to scan a table
--   or an index, specify a <i>TotalSegments</i> value of 4. The value for
--   <i>TotalSegments</i> must be greater than or equal to 1, and less than
--   or equal to 1000000. If you specify a <i>TotalSegments</i> value of 1,
--   the <i>Scan</i> operation will be sequential rather than parallel. If
--   you specify <i>TotalSegments</i> , you must also specify
--   <i>Segment</i> .
sTotalSegments :: Lens' Scan (Maybe Natural)

-- | One or more substitution tokens for attribute names in an expression.
--   The following are some use cases for using
--   <i>ExpressionAttributeNames</i> : * To access an attribute whose name
--   conflicts with a DynamoDB reserved word. * To create a placeholder for
--   repeating occurrences of an attribute name in an expression. * To
--   prevent special characters in an attribute name from being
--   misinterpreted in an expression. Use the <b>#</b> character in an
--   expression to dereference an attribute name. For example, consider the
--   following attribute name: * <tt>Percentile</tt> The name of this
--   attribute conflicts with a reserved word, so it cannot be used
--   directly in an expression. (For the complete list of reserved words,
--   see <a>Reserved Words</a> in the <i>Amazon DynamoDB Developer
--   Guide</i> ). To work around this, you could specify the following for
--   <i>ExpressionAttributeNames</i> : * <tt>{"#P":<a>Percentile</a>}</tt>
--   You could then use this substitution in an expression, as in this
--   example: * <tt>#P = :val</tt> For more information on expression
--   attribute names, see <a>Accessing Item Attributes</a> in the <i>Amazon
--   DynamoDB Developer Guide</i> .
sExpressionAttributeNames :: Lens' Scan (HashMap Text Text)

-- | A string that contains conditions that DynamoDB applies after the
--   <i>Scan</i> operation, but before the data is returned to you. Items
--   that do not satisfy the <i>FilterExpression</i> criteria are not
--   returned. For more information, see <a>Filter Expressions</a> in the
--   <i>Amazon DynamoDB Developer Guide</i> .
sFilterExpression :: Lens' Scan (Maybe Text)

-- | A Boolean value that determines the read consistency model during the
--   scan: * If <i>ConsistentRead</i> is <tt>false</tt> , then the data
--   returned from <i>Scan</i> might not contain the results from other
--   recently completed write operations (PutItem, UpdateItem or
--   DeleteItem). * If <i>ConsistentRead</i> is <tt>true</tt> , then all of
--   the write operations that completed before the <i>Scan</i> began are
--   guaranteed to be contained in the <i>Scan</i> response. The default
--   setting for <i>ConsistentRead</i> is <tt>false</tt> . The
--   <i>ConsistentRead</i> parameter is not supported on global secondary
--   indexes. If you scan a global secondary index with
--   <i>ConsistentRead</i> set to true, you will receive a
--   <i>ValidationException</i> .
sConsistentRead :: Lens' Scan (Maybe Bool)

-- | One or more values that can be substituted in an expression. Use the
--   <b>:</b> (colon) character in an expression to dereference an
--   attribute value. For example, suppose that you wanted to check whether
--   the value of the <i>ProductStatus</i> attribute was one of the
--   following: <tt>Available | Backordered | Discontinued</tt> You would
--   first need to specify <i>ExpressionAttributeValues</i> as follows:
--   <tt>{ ":avail":{<a>S</a>:<a>Available</a>},
--   ":back":{<a>S</a>:<a>Backordered</a>},
--   ":disc":{<a>S</a>:<a>Discontinued</a>} }</tt> You could then use these
--   values in an expression, such as this: <tt>ProductStatus IN (:avail,
--   :back, :disc)</tt> For more information on expression attribute
--   values, see <a>Specifying Conditions</a> in the <i>Amazon DynamoDB
--   Developer Guide</i> .
sExpressionAttributeValues :: Lens' Scan (HashMap Text AttributeValue)

-- | Undocumented member.
sReturnConsumedCapacity :: Lens' Scan (Maybe ReturnConsumedCapacity)

-- | The maximum number of items to evaluate (not necessarily the number of
--   matching items). If DynamoDB processes the number of items up to the
--   limit while processing the results, it stops the operation and returns
--   the matching values up to that point, and a key in
--   <i>LastEvaluatedKey</i> to apply in a subsequent operation, so that
--   you can pick up where you left off. Also, if the processed data set
--   size exceeds 1 MB before DynamoDB reaches this limit, it stops the
--   operation and returns the matching values up to the limit, and a key
--   in <i>LastEvaluatedKey</i> to apply in a subsequent operation to
--   continue the operation. For more information, see <a>Query and
--   Scan</a> in the <i>Amazon DynamoDB Developer Guide</i> .
sLimit :: Lens' Scan (Maybe Natural)

-- | The attributes to be returned in the result. You can retrieve all item
--   attributes, specific item attributes, or the count of matching items.
--   * <tt>ALL_ATTRIBUTES</tt> - Returns all of the item attributes. *
--   <tt>ALL_PROJECTED_ATTRIBUTES</tt> - Allowed only when querying an
--   index. Retrieves all attributes that have been projected into the
--   index. If the index is configured to project all attributes, this
--   return value is equivalent to specifying <tt>ALL_ATTRIBUTES</tt> . *
--   <tt>COUNT</tt> - Returns the number of matching items, rather than the
--   matching items themselves. * <tt>SPECIFIC_ATTRIBUTES</tt> - Returns
--   only the attributes listed in <i>AttributesToGet</i> . This return
--   value is equivalent to specifying <i>AttributesToGet</i> without
--   specifying any value for <i>Select</i> . If neither <i>Select</i> nor
--   <i>AttributesToGet</i> are specified, DynamoDB defaults to
--   <tt>ALL_ATTRIBUTES</tt> . You cannot use both <i>AttributesToGet</i>
--   and <i>Select</i> together in a single request, unless the value for
--   <i>Select</i> is <tt>SPECIFIC_ATTRIBUTES</tt> . (This usage is
--   equivalent to specifying <i>AttributesToGet</i> without any value for
--   <i>Select</i> .)
sSelect :: Lens' Scan (Maybe Select)

-- | For a parallel <i>Scan</i> request, <i>Segment</i> identifies an
--   individual segment to be scanned by an application worker. Segment IDs
--   are zero-based, so the first segment is always 0. For example, if you
--   want to use four application threads to scan a table or an index, then
--   the first thread specifies a <i>Segment</i> value of 0, the second
--   thread specifies 1, and so on. The value of <i>LastEvaluatedKey</i>
--   returned from a parallel <i>Scan</i> request must be used as
--   <i>ExclusiveStartKey</i> with the same segment ID in a subsequent
--   <i>Scan</i> operation. The value for <i>Segment</i> must be greater
--   than or equal to 0, and less than the value provided for
--   <i>TotalSegments</i> . If you provide <i>Segment</i> , you must also
--   provide <i>TotalSegments</i> .
sSegment :: Lens' Scan (Maybe Natural)

-- | <i>Important:</i> This is a legacy parameter, for backward
--   compatibility. New applications should use <i>FilterExpression</i>
--   instead. Do not combine legacy parameters and expression parameters in
--   a single API call; otherwise, DynamoDB will return a
--   <i>ValidationException</i> exception. A logical operator to apply to
--   the conditions in a <i>ScanFilter</i> map: * <tt>AND</tt> - If all of
--   the conditions evaluate to true, then the entire map evaluates to
--   true. * <tt>OR</tt> - If at least one of the conditions evaluate to
--   true, then the entire map evaluates to true. If you omit
--   <i>ConditionalOperator</i> , then <tt>AND</tt> is the default. The
--   operation will succeed only if the entire map evaluates to true.
sConditionalOperator :: Lens' Scan (Maybe ConditionalOperator)

-- | The primary key of the first item that this operation will evaluate.
--   Use the value that was returned for <i>LastEvaluatedKey</i> in the
--   previous operation. The data type for <i>ExclusiveStartKey</i> must be
--   String, Number or Binary. No set data types are allowed. In a parallel
--   scan, a <i>Scan</i> request that includes <i>ExclusiveStartKey</i>
--   must specify the same segment whose previous <i>Scan</i> returned the
--   corresponding value of <i>LastEvaluatedKey</i> .
sExclusiveStartKey :: Lens' Scan (HashMap Text AttributeValue)

-- | The name of a secondary index to scan. This index can be any local
--   secondary index or global secondary index. Note that if you use the
--   <tt>IndexName</tt> parameter, you must also provide <tt>TableName</tt>
--   .
sIndexName :: Lens' Scan (Maybe Text)

-- | The name of the table containing the requested items; or, if you
--   provide <tt>IndexName</tt> , the name of the table to which that index
--   belongs.
sTableName :: Lens' Scan Text

-- | Creates a value of <a>ScanResponse</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>srsLastEvaluatedKey</a> - The primary key of the item where the
--   operation stopped, inclusive of the previous result set. Use this
--   value to start a new operation, excluding this value in the new
--   request. If <i>LastEvaluatedKey</i> is empty, then the "last page" of
--   results has been processed and there is no more data to be retrieved.
--   If <i>LastEvaluatedKey</i> is not empty, it does not necessarily mean
--   that there is more data in the result set. The only way to know when
--   you have reached the end of the result set is when
--   <i>LastEvaluatedKey</i> is empty.</li>
--   <li><a>srsCount</a> - The number of items in the response. If you set
--   <i>ScanFilter</i> in the request, then <i>Count</i> is the number of
--   items returned after the filter was applied, and <i>ScannedCount</i>
--   is the number of matching items before the filter was applied. If you
--   did not use a filter in the request, then <i>Count</i> is the same as
--   <i>ScannedCount</i> .</li>
--   <li><a>srsScannedCount</a> - The number of items evaluated, before any
--   <i>ScanFilter</i> is applied. A high <i>ScannedCount</i> value with
--   few, or no, <i>Count</i> results indicates an inefficient <i>Scan</i>
--   operation. For more information, see <a>Count and ScannedCount</a> in
--   the <i>Amazon DynamoDB Developer Guide</i> . If you did not use a
--   filter in the request, then <i>ScannedCount</i> is the same as
--   <i>Count</i> .</li>
--   <li><a>srsItems</a> - An array of item attributes that match the scan
--   criteria. Each element in this array consists of an attribute name and
--   the value for that attribute.</li>
--   <li><a>srsConsumedCapacity</a> - Undocumented member.</li>
--   <li><a>srsResponseStatus</a> - -- | The response status code.</li>
--   </ul>
scanResponse :: Int -> ScanResponse

-- | Represents the output of a <i>Scan</i> operation.
--   
--   <i>See:</i> <a>scanResponse</a> smart constructor.
data ScanResponse

-- | The primary key of the item where the operation stopped, inclusive of
--   the previous result set. Use this value to start a new operation,
--   excluding this value in the new request. If <i>LastEvaluatedKey</i> is
--   empty, then the "last page" of results has been processed and there is
--   no more data to be retrieved. If <i>LastEvaluatedKey</i> is not empty,
--   it does not necessarily mean that there is more data in the result
--   set. The only way to know when you have reached the end of the result
--   set is when <i>LastEvaluatedKey</i> is empty.
srsLastEvaluatedKey :: Lens' ScanResponse (HashMap Text AttributeValue)

-- | The number of items in the response. If you set <i>ScanFilter</i> in
--   the request, then <i>Count</i> is the number of items returned after
--   the filter was applied, and <i>ScannedCount</i> is the number of
--   matching items before the filter was applied. If you did not use a
--   filter in the request, then <i>Count</i> is the same as
--   <i>ScannedCount</i> .
srsCount :: Lens' ScanResponse (Maybe Int)

-- | The number of items evaluated, before any <i>ScanFilter</i> is
--   applied. A high <i>ScannedCount</i> value with few, or no,
--   <i>Count</i> results indicates an inefficient <i>Scan</i> operation.
--   For more information, see <a>Count and ScannedCount</a> in the
--   <i>Amazon DynamoDB Developer Guide</i> . If you did not use a filter
--   in the request, then <i>ScannedCount</i> is the same as <i>Count</i> .
srsScannedCount :: Lens' ScanResponse (Maybe Int)

-- | An array of item attributes that match the scan criteria. Each element
--   in this array consists of an attribute name and the value for that
--   attribute.
srsItems :: Lens' ScanResponse [HashMap Text AttributeValue]

-- | Undocumented member.
srsConsumedCapacity :: Lens' ScanResponse (Maybe ConsumedCapacity)

-- | <ul>
--   <li>- | The response status code.</li>
--   </ul>
srsResponseStatus :: Lens' ScanResponse Int
instance GHC.Generics.Generic Network.AWS.DynamoDB.Scan.ScanResponse
instance Data.Data.Data Network.AWS.DynamoDB.Scan.ScanResponse
instance GHC.Show.Show Network.AWS.DynamoDB.Scan.ScanResponse
instance GHC.Read.Read Network.AWS.DynamoDB.Scan.ScanResponse
instance GHC.Classes.Eq Network.AWS.DynamoDB.Scan.ScanResponse
instance GHC.Generics.Generic Network.AWS.DynamoDB.Scan.Scan
instance Data.Data.Data Network.AWS.DynamoDB.Scan.Scan
instance GHC.Show.Show Network.AWS.DynamoDB.Scan.Scan
instance GHC.Read.Read Network.AWS.DynamoDB.Scan.Scan
instance GHC.Classes.Eq Network.AWS.DynamoDB.Scan.Scan
instance Network.AWS.Pager.AWSPager Network.AWS.DynamoDB.Scan.Scan
instance Network.AWS.Types.AWSRequest Network.AWS.DynamoDB.Scan.Scan
instance Data.Hashable.Class.Hashable Network.AWS.DynamoDB.Scan.Scan
instance Control.DeepSeq.NFData Network.AWS.DynamoDB.Scan.Scan
instance Network.AWS.Data.Headers.ToHeaders Network.AWS.DynamoDB.Scan.Scan
instance Data.Aeson.Types.ToJSON.ToJSON Network.AWS.DynamoDB.Scan.Scan
instance Network.AWS.Data.Path.ToPath Network.AWS.DynamoDB.Scan.Scan
instance Network.AWS.Data.Query.ToQuery Network.AWS.DynamoDB.Scan.Scan
instance Control.DeepSeq.NFData Network.AWS.DynamoDB.Scan.ScanResponse


-- | A <i>Query</i> operation uses the primary key of a table or a
--   secondary index to directly access items from that table or index.
--   
--   Use the <i>KeyConditionExpression</i> parameter to provide a specific
--   value for the partition key. The <i>Query</i> operation will return
--   all of the items from the table or index with that partition key
--   value. You can optionally narrow the scope of the <i>Query</i>
--   operation by specifying a sort key value and a comparison operator in
--   <i>KeyConditionExpression</i> . You can use the
--   <i>ScanIndexForward</i> parameter to get results in forward or reverse
--   order, by sort key.
--   
--   Queries that do not return results consume the minimum number of read
--   capacity units for that type of read operation.
--   
--   If the total number of items meeting the query criteria exceeds the
--   result set size limit of 1 MB, the query stops and results are
--   returned to the user with the <i>LastEvaluatedKey</i> element to
--   continue the query in a subsequent operation. Unlike a <i>Scan</i>
--   operation, a <i>Query</i> operation never returns both an empty result
--   set and a <i>LastEvaluatedKey</i> value. <i>LastEvaluatedKey</i> is
--   only provided if you have used the <i>Limit</i> parameter, or if the
--   result set exceeds 1 MB (prior to applying a filter).
--   
--   You can query a table, a local secondary index, or a global secondary
--   index. For a query on a table or on a local secondary index, you can
--   set the <i>ConsistentRead</i> parameter to <tt>true</tt> and obtain a
--   strongly consistent result. Global secondary indexes support
--   eventually consistent reads only, so do not specify
--   <i>ConsistentRead</i> when querying a global secondary index.
--   
--   This operation returns paginated results.
module Network.AWS.DynamoDB.Query

-- | Creates a value of <a>Query</a> with the minimum fields required to
--   make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>qKeyConditions</a> - <i>Important:</i> This is a legacy
--   parameter, for backward compatibility. New applications should use
--   <i>KeyConditionExpression</i> instead. Do not combine legacy
--   parameters and expression parameters in a single API call; otherwise,
--   DynamoDB will return a <i>ValidationException</i> exception. The
--   selection criteria for the query. For a query on a table, you can have
--   conditions only on the table primary key attributes. You must provide
--   the partition key name and value as an <tt>EQ</tt> condition. You can
--   optionally provide a second condition, referring to the sort key. For
--   a query on an index, you can have conditions only on the index key
--   attributes. You must provide the index partition key name and value as
--   an <tt>EQ</tt> condition. You can optionally provide a second
--   condition, referring to the index sort key. Each <i>KeyConditions</i>
--   element consists of an attribute name to compare, along with the
--   following: * <i>AttributeValueList</i> - One or more values to
--   evaluate against the supplied attribute. The number of values in the
--   list depends on the <i>ComparisonOperator</i> being used. For type
--   Number, value comparisons are numeric. String value comparisons for
--   greater than, equals, or less than are based on ASCII character code
--   values. For example, <tt>a</tt> is greater than <tt>A</tt> , and
--   <tt>a</tt> is greater than <tt>B</tt> . For a list of code values, see
--   <a>http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters</a> .
--   For Binary, DynamoDB treats each byte of the binary data as unsigned
--   when it compares binary values. * <i>ComparisonOperator</i> - A
--   comparator for evaluating attributes, for example, equals, greater
--   than, less than, and so on. For <i>KeyConditions</i> , only the
--   following comparison operators are supported: <tt>EQ | LE | LT | GE |
--   GT | BEGINS_WITH | BETWEEN</tt> The following are descriptions of
--   these comparison operators. * <tt>EQ</tt> : Equal.
--   <i>AttributeValueList</i> can contain only one <i>AttributeValue</i>
--   of type String, Number, or Binary (not a set type). If an item
--   contains an <i>AttributeValue</i> element of a different type than the
--   one specified in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LE</tt> : Less than or equal.
--   <i>AttributeValueList</i> can contain only one <i>AttributeValue</i>
--   element of type String, Number, or Binary (not a set type). If an item
--   contains an <i>AttributeValue</i> element of a different type than the
--   one provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LT</tt> : Less than. <i>AttributeValueList</i> can
--   contain only one <i>AttributeValue</i> of type String, Number, or
--   Binary (not a set type). If an item contains an <i>AttributeValue</i>
--   element of a different type than the one provided in the request, the
--   value does not match. For example, <tt>{<a>S</a>:"6"}</tt> does not
--   equal <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GE</tt> :
--   Greater than or equal. <i>AttributeValueList</i> can contain only one
--   <i>AttributeValue</i> element of type String, Number, or Binary (not a
--   set type). If an item contains an <i>AttributeValue</i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GT</tt> :
--   Greater than. <i>AttributeValueList</i> can contain only one
--   <i>AttributeValue</i> element of type String, Number, or Binary (not a
--   set type). If an item contains an <i>AttributeValue</i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . *
--   <tt>BEGINS_WITH</tt> : Checks for a prefix. <i>AttributeValueList</i>
--   can contain only one <i>AttributeValue</i> of type String or Binary
--   (not a Number or a set type). The target attribute of the comparison
--   must be of type String or Binary (not a Number or a set type). *
--   <tt>BETWEEN</tt> : Greater than or equal to the first value, and less
--   than or equal to the second value. <i>AttributeValueList</i> must
--   contain two <i>AttributeValue</i> elements of the same type, either
--   String, Number, or Binary (not a set type). A target attribute matches
--   if the target value is greater than, or equal to, the first element
--   and less than, or equal to, the second element. If an item contains an
--   <i>AttributeValue</i> element of a different type than the one
--   provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not compare to <tt>{<a>N</a>:"6"}</tt> .
--   Also, <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6",
--   "2", "1"]}</tt> For usage examples of <i>AttributeValueList</i> and
--   <i>ComparisonOperator</i> , see <a>Legacy Conditional Parameters</a>
--   in the <i>Amazon DynamoDB Developer Guide</i> .</li>
--   <li><a>qProjectionExpression</a> - A string that identifies one or
--   more attributes to retrieve from the table. These attributes can
--   include scalars, sets, or elements of a JSON document. The attributes
--   in the expression must be separated by commas. If no attribute names
--   are specified, then all attributes will be returned. If any of the
--   requested attributes are not found, they will not appear in the
--   result. For more information, see <a>Accessing Item Attributes</a> in
--   the <i>Amazon DynamoDB Developer Guide</i> .</li>
--   <li><a>qAttributesToGet</a> - <i>Important:</i> This is a legacy
--   parameter, for backward compatibility. New applications should use
--   <i>ProjectionExpression</i> instead. Do not combine legacy parameters
--   and expression parameters in a single API call; otherwise, DynamoDB
--   will return a <i>ValidationException</i> exception. This parameter
--   allows you to retrieve attributes of type List or Map; however, it
--   cannot retrieve individual elements within a List or a Map. The names
--   of one or more attributes to retrieve. If no attribute names are
--   provided, then all attributes will be returned. If any of the
--   requested attributes are not found, they will not appear in the
--   result. Note that <i>AttributesToGet</i> has no effect on provisioned
--   throughput consumption. DynamoDB determines capacity units consumed
--   based on item size, not on the amount of data that is returned to an
--   application. You cannot use both <i>AttributesToGet</i> and
--   <i>Select</i> together in a <i>Query</i> request, <i>unless</i> the
--   value for <i>Select</i> is <tt>SPECIFIC_ATTRIBUTES</tt> . (This usage
--   is equivalent to specifying <i>AttributesToGet</i> without any value
--   for <i>Select</i> .) If you query a local secondary index and request
--   only attributes that are projected into that index, the operation will
--   read only the index and not the table. If any of the requested
--   attributes are not projected into the local secondary index, DynamoDB
--   will fetch each of these attributes from the parent table. This extra
--   fetching incurs additional throughput cost and latency. If you query a
--   global secondary index, you can only request attributes that are
--   projected into the index. Global secondary index queries cannot fetch
--   attributes from the parent table.</li>
--   <li><a>qExpressionAttributeNames</a> - One or more substitution tokens
--   for attribute names in an expression. The following are some use cases
--   for using <i>ExpressionAttributeNames</i> : * To access an attribute
--   whose name conflicts with a DynamoDB reserved word. * To create a
--   placeholder for repeating occurrences of an attribute name in an
--   expression. * To prevent special characters in an attribute name from
--   being misinterpreted in an expression. Use the <b>#</b> character in
--   an expression to dereference an attribute name. For example, consider
--   the following attribute name: * <tt>Percentile</tt> The name of this
--   attribute conflicts with a reserved word, so it cannot be used
--   directly in an expression. (For the complete list of reserved words,
--   see <a>Reserved Words</a> in the <i>Amazon DynamoDB Developer
--   Guide</i> ). To work around this, you could specify the following for
--   <i>ExpressionAttributeNames</i> : * <tt>{"#P":<a>Percentile</a>}</tt>
--   You could then use this substitution in an expression, as in this
--   example: * <tt>#P = :val</tt> For more information on expression
--   attribute names, see <a>Accessing Item Attributes</a> in the <i>Amazon
--   DynamoDB Developer Guide</i> .</li>
--   <li><a>qFilterExpression</a> - A string that contains conditions that
--   DynamoDB applies after the <i>Query</i> operation, but before the data
--   is returned to you. Items that do not satisfy the
--   <i>FilterExpression</i> criteria are not returned. For more
--   information, see <a>Filter Expressions</a> in the <i>Amazon DynamoDB
--   Developer Guide</i> .</li>
--   <li><a>qQueryFilter</a> - <i>Important:</i> This is a legacy
--   parameter, for backward compatibility. New applications should use
--   <i>FilterExpression</i> instead. Do not combine legacy parameters and
--   expression parameters in a single API call; otherwise, DynamoDB will
--   return a <i>ValidationException</i> exception. 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. If you provide more than one condition in the
--   <i>QueryFilter</i> map, then by default all of the conditions must
--   evaluate to true. In other words, the conditions are ANDed together.
--   (You can use the <i>ConditionalOperator</i> 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
--   <i>QueryFilter</i> does not allow key attributes. You cannot define a
--   filter condition on a partition key or a sort key. Each
--   <i>QueryFilter</i> element consists of an attribute name to compare,
--   along with the following: * <i>AttributeValueList</i> - One or more
--   values to evaluate against the supplied attribute. The number of
--   values in the list depends on the operator specified in
--   <i>ComparisonOperator</i> . For type Number, value comparisons are
--   numeric. String value comparisons for greater than, equals, or less
--   than are based on ASCII character code values. For example, <tt>a</tt>
--   is greater than <tt>A</tt> , and <tt>a</tt> is greater than <tt>B</tt>
--   . For a list of code values, see
--   <a>http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters</a> .
--   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 <a>JSON Data Format</a> in the <i>Amazon
--   DynamoDB Developer Guide</i> . * <i>ComparisonOperator</i> - A
--   comparator for evaluating attributes. For example, equals, greater
--   than, less than, etc. The following comparison operators are
--   available: <tt>EQ | NE | LE | LT | GE | GT | NOT_NULL | NULL |
--   CONTAINS | NOT_CONTAINS | BEGINS_WITH | IN | BETWEEN</tt> For complete
--   descriptions of all comparison operators, see the <a>Condition</a>
--   data type.</li>
--   <li><a>qConsistentRead</a> - Determines the read consistency model: If
--   set to <tt>true</tt> , then the operation uses strongly consistent
--   reads; otherwise, the operation uses eventually consistent reads.
--   Strongly consistent reads are not supported on global secondary
--   indexes. If you query a global secondary index with
--   <i>ConsistentRead</i> set to <tt>true</tt> , you will receive a
--   <i>ValidationException</i> .</li>
--   <li><a>qExpressionAttributeValues</a> - One or more values that can be
--   substituted in an expression. Use the <b>:</b> (colon) character in an
--   expression to dereference an attribute value. For example, suppose
--   that you wanted to check whether the value of the <i>ProductStatus</i>
--   attribute was one of the following: <tt>Available | Backordered |
--   Discontinued</tt> You would first need to specify
--   <i>ExpressionAttributeValues</i> as follows: <tt>{
--   ":avail":{<a>S</a>:<a>Available</a>},
--   ":back":{<a>S</a>:<a>Backordered</a>},
--   ":disc":{<a>S</a>:<a>Discontinued</a>} }</tt> You could then use these
--   values in an expression, such as this: <tt>ProductStatus IN (:avail,
--   :back, :disc)</tt> For more information on expression attribute
--   values, see <a>Specifying Conditions</a> in the <i>Amazon DynamoDB
--   Developer Guide</i> .</li>
--   <li><a>qReturnConsumedCapacity</a> - Undocumented member.</li>
--   <li><a>qScanIndexForward</a> - Specifies the order for index
--   traversal: If <tt>true</tt> (default), the traversal is performed in
--   ascending order; if <tt>false</tt> , the traversal is performed in
--   descending order. Items with the same partition key value are stored
--   in sorted order by sort key. If the sort key data type is Number, the
--   results are stored in numeric order. For type String, the results are
--   stored in order of ASCII character code values. For type Binary,
--   DynamoDB treats each byte of the binary data as unsigned. If
--   <i>ScanIndexForward</i> is <tt>true</tt> , DynamoDB returns the
--   results in the order in which they are stored (by sort key value).
--   This is the default behavior. If <i>ScanIndexForward</i> is
--   <tt>false</tt> , DynamoDB reads the results in reverse order by sort
--   key value, and then returns the results to the client.</li>
--   <li><a>qLimit</a> - The maximum number of items to evaluate (not
--   necessarily the number of matching items). If DynamoDB processes the
--   number of items up to the limit while processing the results, it stops
--   the operation and returns the matching values up to that point, and a
--   key in <i>LastEvaluatedKey</i> to apply in a subsequent operation, so
--   that you can pick up where you left off. Also, if the processed data
--   set size exceeds 1 MB before DynamoDB reaches this limit, it stops the
--   operation and returns the matching values up to the limit, and a key
--   in <i>LastEvaluatedKey</i> to apply in a subsequent operation to
--   continue the operation. For more information, see <a>Query and
--   Scan</a> in the <i>Amazon DynamoDB Developer Guide</i> .</li>
--   <li><a>qSelect</a> - The attributes to be returned in the result. You
--   can retrieve all item attributes, specific item attributes, the count
--   of matching items, or in the case of an index, some or all of the
--   attributes projected into the index. * <tt>ALL_ATTRIBUTES</tt> -
--   Returns all of the item attributes from the specified table or index.
--   If you query a local secondary index, then for each matching item in
--   the index DynamoDB will fetch the entire item from the parent table.
--   If the index is configured to project all item attributes, then all of
--   the data can be obtained from the local secondary index, and no
--   fetching is required. * <tt>ALL_PROJECTED_ATTRIBUTES</tt> - Allowed
--   only when querying an index. Retrieves all attributes that have been
--   projected into the index. If the index is configured to project all
--   attributes, this return value is equivalent to specifying
--   <tt>ALL_ATTRIBUTES</tt> . * <tt>COUNT</tt> - Returns the number of
--   matching items, rather than the matching items themselves. *
--   <tt>SPECIFIC_ATTRIBUTES</tt> - Returns only the attributes listed in
--   <i>AttributesToGet</i> . This return value is equivalent to specifying
--   <i>AttributesToGet</i> without specifying any value for <i>Select</i>
--   . If you query a local secondary index and request only attributes
--   that are projected into that index, the operation will read only the
--   index and not the table. If any of the requested attributes are not
--   projected into the local secondary index, DynamoDB will fetch each of
--   these attributes from the parent table. This extra fetching incurs
--   additional throughput cost and latency. If you query a global
--   secondary index, you can only request attributes that are projected
--   into the index. Global secondary index queries cannot fetch attributes
--   from the parent table. If neither <i>Select</i> nor
--   <i>AttributesToGet</i> are specified, DynamoDB defaults to
--   <tt>ALL_ATTRIBUTES</tt> when accessing a table, and
--   <tt>ALL_PROJECTED_ATTRIBUTES</tt> when accessing an index. You cannot
--   use both <i>Select</i> and <i>AttributesToGet</i> together in a single
--   request, unless the value for <i>Select</i> is
--   <tt>SPECIFIC_ATTRIBUTES</tt> . (This usage is equivalent to specifying
--   <i>AttributesToGet</i> without any value for <i>Select</i> .)</li>
--   <li><a>qKeyConditionExpression</a> - The condition that specifies the
--   key value(s) for items to be retrieved by the <i>Query</i> action. The
--   condition must perform an equality test on a single partition key
--   value. The condition can also perform one of several comparison tests
--   on a single sort key value. <i>Query</i> can use
--   <i>KeyConditionExpression</i> to retrieve one item with a given
--   partition key value and sort key value, or several items that have the
--   same partition key value but different sort key values. The partition
--   key equality test is required, and must be specified in the following
--   format: <tt>partitionKeyName</tt> <i>=</i> <tt>:partitionkeyval</tt>
--   If you also want to provide a condition for the sort key, it must be
--   combined using <i>AND</i> with the condition for the sort key.
--   Following is an example, using the <b>=</b> comparison operator for
--   the sort key: <tt>partitionKeyName</tt> <i>=</i>
--   <tt>:partitionkeyval</tt> <i>AND</i> <tt>sortKeyName</tt> <i>=</i>
--   <tt>:sortkeyval</tt> Valid comparisons for the sort key condition are
--   as follows: * <tt>sortKeyName</tt> <i>=</i> <tt>:sortkeyval</tt> -
--   true if the sort key value is equal to <tt>:sortkeyval</tt> . *
--   <tt>sortKeyName</tt> <i>&lt;</i> <tt>:sortkeyval</tt> - true if the
--   sort key value is less than <tt>:sortkeyval</tt> . *
--   <tt>sortKeyName</tt> <i>&lt;=</i> <tt>:sortkeyval</tt> - true if the
--   sort key value is less than or equal to <tt>:sortkeyval</tt> . *
--   <tt>sortKeyName</tt> <i>&gt;</i> <tt>:sortkeyval</tt> - true if the
--   sort key value is greater than <tt>:sortkeyval</tt> . *
--   <tt>sortKeyName</tt> <i>&gt;= </i> <tt>:sortkeyval</tt> - true if the
--   sort key value is greater than or equal to <tt>:sortkeyval</tt> . *
--   <tt>sortKeyName</tt> <i>BETWEEN</i> <tt>:sortkeyval1</tt> <i>AND</i>
--   <tt>:sortkeyval2</tt> - true if the sort key value is greater than or
--   equal to <tt>:sortkeyval1</tt> , and less than or equal to
--   <tt>:sortkeyval2</tt> . * <i>begins_with (</i> <tt>sortKeyName</tt> ,
--   <tt>:sortkeyval</tt> <i>)</i> - true if the sort key value begins with
--   a particular operand. (You cannot use this function with a sort key
--   that is of type Number.) Note that the function name
--   <tt>begins_with</tt> is case-sensitive. Use the
--   <i>ExpressionAttributeValues</i> parameter to replace tokens such as
--   <tt>:partitionval</tt> and <tt>:sortval</tt> with actual values at
--   runtime. You can optionally use the <i>ExpressionAttributeNames</i>
--   parameter to replace the names of the partition key and sort key with
--   placeholder tokens. This option might be necessary if an attribute
--   name conflicts with a DynamoDB reserved word. For example, the
--   following <i>KeyConditionExpression</i> parameter causes an error
--   because <i>Size</i> is a reserved word: * <tt>Size = :myval</tt> To
--   work around this, define a placeholder (such a <tt>#S</tt> ) to
--   represent the attribute name <i>Size</i> .
--   <i>KeyConditionExpression</i> then is as follows: * <tt>#S =
--   :myval</tt> For a list of reserved words, see <a>Reserved Words</a> in
--   the <i>Amazon DynamoDB Developer Guide</i> . For more information on
--   <i>ExpressionAttributeNames</i> and <i>ExpressionAttributeValues</i> ,
--   see <a>Using Placeholders for Attribute Names and Values</a> in the
--   <i>Amazon DynamoDB Developer Guide</i> .</li>
--   <li><a>qConditionalOperator</a> - <i>Important:</i> This is a legacy
--   parameter, for backward compatibility. New applications should use
--   <i>FilterExpression</i> instead. Do not combine legacy parameters and
--   expression parameters in a single API call; otherwise, DynamoDB will
--   return a <i>ValidationException</i> exception. A logical operator to
--   apply to the conditions in a <i>QueryFilter</i> map: * <tt>AND</tt> -
--   If all of the conditions evaluate to true, then the entire map
--   evaluates to true. * <tt>OR</tt> - If at least one of the conditions
--   evaluate to true, then the entire map evaluates to true. If you omit
--   <i>ConditionalOperator</i> , then <tt>AND</tt> is the default. The
--   operation will succeed only if the entire map evaluates to true.</li>
--   <li><a>qExclusiveStartKey</a> - The primary key of the first item that
--   this operation will evaluate. Use the value that was returned for
--   <i>LastEvaluatedKey</i> in the previous operation. The data type for
--   <i>ExclusiveStartKey</i> must be String, Number or Binary. No set data
--   types are allowed.</li>
--   <li><a>qIndexName</a> - The name of an index to query. This index can
--   be any local secondary index or global secondary index on the table.
--   Note that if you use the <i>IndexName</i> parameter, you must also
--   provide <i>TableName.</i></li>
--   <li><a>qTableName</a> - The name of the table containing the requested
--   items.</li>
--   </ul>
query :: Text -> Query

-- | Represents the input of a <i>Query</i> operation.
--   
--   <i>See:</i> <a>query</a> smart constructor.
data Query

-- | <i>Important:</i> This is a legacy parameter, for backward
--   compatibility. New applications should use
--   <i>KeyConditionExpression</i> instead. Do not combine legacy
--   parameters and expression parameters in a single API call; otherwise,
--   DynamoDB will return a <i>ValidationException</i> exception. The
--   selection criteria for the query. For a query on a table, you can have
--   conditions only on the table primary key attributes. You must provide
--   the partition key name and value as an <tt>EQ</tt> condition. You can
--   optionally provide a second condition, referring to the sort key. For
--   a query on an index, you can have conditions only on the index key
--   attributes. You must provide the index partition key name and value as
--   an <tt>EQ</tt> condition. You can optionally provide a second
--   condition, referring to the index sort key. Each <i>KeyConditions</i>
--   element consists of an attribute name to compare, along with the
--   following: * <i>AttributeValueList</i> - One or more values to
--   evaluate against the supplied attribute. The number of values in the
--   list depends on the <i>ComparisonOperator</i> being used. For type
--   Number, value comparisons are numeric. String value comparisons for
--   greater than, equals, or less than are based on ASCII character code
--   values. For example, <tt>a</tt> is greater than <tt>A</tt> , and
--   <tt>a</tt> is greater than <tt>B</tt> . For a list of code values, see
--   <a>http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters</a> .
--   For Binary, DynamoDB treats each byte of the binary data as unsigned
--   when it compares binary values. * <i>ComparisonOperator</i> - A
--   comparator for evaluating attributes, for example, equals, greater
--   than, less than, and so on. For <i>KeyConditions</i> , only the
--   following comparison operators are supported: <tt>EQ | LE | LT | GE |
--   GT | BEGINS_WITH | BETWEEN</tt> The following are descriptions of
--   these comparison operators. * <tt>EQ</tt> : Equal.
--   <i>AttributeValueList</i> can contain only one <i>AttributeValue</i>
--   of type String, Number, or Binary (not a set type). If an item
--   contains an <i>AttributeValue</i> element of a different type than the
--   one specified in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LE</tt> : Less than or equal.
--   <i>AttributeValueList</i> can contain only one <i>AttributeValue</i>
--   element of type String, Number, or Binary (not a set type). If an item
--   contains an <i>AttributeValue</i> element of a different type than the
--   one provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LT</tt> : Less than. <i>AttributeValueList</i> can
--   contain only one <i>AttributeValue</i> of type String, Number, or
--   Binary (not a set type). If an item contains an <i>AttributeValue</i>
--   element of a different type than the one provided in the request, the
--   value does not match. For example, <tt>{<a>S</a>:"6"}</tt> does not
--   equal <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GE</tt> :
--   Greater than or equal. <i>AttributeValueList</i> can contain only one
--   <i>AttributeValue</i> element of type String, Number, or Binary (not a
--   set type). If an item contains an <i>AttributeValue</i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GT</tt> :
--   Greater than. <i>AttributeValueList</i> can contain only one
--   <i>AttributeValue</i> element of type String, Number, or Binary (not a
--   set type). If an item contains an <i>AttributeValue</i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . *
--   <tt>BEGINS_WITH</tt> : Checks for a prefix. <i>AttributeValueList</i>
--   can contain only one <i>AttributeValue</i> of type String or Binary
--   (not a Number or a set type). The target attribute of the comparison
--   must be of type String or Binary (not a Number or a set type). *
--   <tt>BETWEEN</tt> : Greater than or equal to the first value, and less
--   than or equal to the second value. <i>AttributeValueList</i> must
--   contain two <i>AttributeValue</i> elements of the same type, either
--   String, Number, or Binary (not a set type). A target attribute matches
--   if the target value is greater than, or equal to, the first element
--   and less than, or equal to, the second element. If an item contains an
--   <i>AttributeValue</i> element of a different type than the one
--   provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not compare to <tt>{<a>N</a>:"6"}</tt> .
--   Also, <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6",
--   "2", "1"]}</tt> For usage examples of <i>AttributeValueList</i> and
--   <i>ComparisonOperator</i> , see <a>Legacy Conditional Parameters</a>
--   in the <i>Amazon DynamoDB Developer Guide</i> .
qKeyConditions :: Lens' Query (HashMap Text Condition)

-- | A string that identifies one or more attributes to retrieve from the
--   table. These attributes can include scalars, sets, or elements of a
--   JSON document. The attributes in the expression must be separated by
--   commas. If no attribute names are specified, then all attributes will
--   be returned. If any of the requested attributes are not found, they
--   will not appear in the result. For more information, see <a>Accessing
--   Item Attributes</a> in the <i>Amazon DynamoDB Developer Guide</i> .
qProjectionExpression :: Lens' Query (Maybe Text)

-- | <i>Important:</i> This is a legacy parameter, for backward
--   compatibility. New applications should use <i>ProjectionExpression</i>
--   instead. Do not combine legacy parameters and expression parameters in
--   a single API call; otherwise, DynamoDB will return a
--   <i>ValidationException</i> exception. This parameter allows you to
--   retrieve attributes of type List or Map; however, it cannot retrieve
--   individual elements within a List or a Map. The names of one or more
--   attributes to retrieve. If no attribute names are provided, then all
--   attributes will be returned. If any of the requested attributes are
--   not found, they will not appear in the result. Note that
--   <i>AttributesToGet</i> has no effect on provisioned throughput
--   consumption. DynamoDB determines capacity units consumed based on item
--   size, not on the amount of data that is returned to an application.
--   You cannot use both <i>AttributesToGet</i> and <i>Select</i> together
--   in a <i>Query</i> request, <i>unless</i> the value for <i>Select</i>
--   is <tt>SPECIFIC_ATTRIBUTES</tt> . (This usage is equivalent to
--   specifying <i>AttributesToGet</i> without any value for <i>Select</i>
--   .) If you query a local secondary index and request only attributes
--   that are projected into that index, the operation will read only the
--   index and not the table. If any of the requested attributes are not
--   projected into the local secondary index, DynamoDB will fetch each of
--   these attributes from the parent table. This extra fetching incurs
--   additional throughput cost and latency. If you query a global
--   secondary index, you can only request attributes that are projected
--   into the index. Global secondary index queries cannot fetch attributes
--   from the parent table.
qAttributesToGet :: Lens' Query (Maybe (NonEmpty Text))

-- | One or more substitution tokens for attribute names in an expression.
--   The following are some use cases for using
--   <i>ExpressionAttributeNames</i> : * To access an attribute whose name
--   conflicts with a DynamoDB reserved word. * To create a placeholder for
--   repeating occurrences of an attribute name in an expression. * To
--   prevent special characters in an attribute name from being
--   misinterpreted in an expression. Use the <b>#</b> character in an
--   expression to dereference an attribute name. For example, consider the
--   following attribute name: * <tt>Percentile</tt> The name of this
--   attribute conflicts with a reserved word, so it cannot be used
--   directly in an expression. (For the complete list of reserved words,
--   see <a>Reserved Words</a> in the <i>Amazon DynamoDB Developer
--   Guide</i> ). To work around this, you could specify the following for
--   <i>ExpressionAttributeNames</i> : * <tt>{"#P":<a>Percentile</a>}</tt>
--   You could then use this substitution in an expression, as in this
--   example: * <tt>#P = :val</tt> For more information on expression
--   attribute names, see <a>Accessing Item Attributes</a> in the <i>Amazon
--   DynamoDB Developer Guide</i> .
qExpressionAttributeNames :: Lens' Query (HashMap Text Text)

-- | A string that contains conditions that DynamoDB applies after the
--   <i>Query</i> operation, but before the data is returned to you. Items
--   that do not satisfy the <i>FilterExpression</i> criteria are not
--   returned. For more information, see <a>Filter Expressions</a> in the
--   <i>Amazon DynamoDB Developer Guide</i> .
qFilterExpression :: Lens' Query (Maybe Text)

-- | <i>Important:</i> This is a legacy parameter, for backward
--   compatibility. New applications should use <i>FilterExpression</i>
--   instead. Do not combine legacy parameters and expression parameters in
--   a single API call; otherwise, DynamoDB will return a
--   <i>ValidationException</i> exception. 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. If you provide more than one condition in the <i>QueryFilter</i>
--   map, then by default all of the conditions must evaluate to true. In
--   other words, the conditions are ANDed together. (You can use the
--   <i>ConditionalOperator</i> 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 <i>QueryFilter</i> does not
--   allow key attributes. You cannot define a filter condition on a
--   partition key or a sort key. Each <i>QueryFilter</i> element consists
--   of an attribute name to compare, along with the following: *
--   <i>AttributeValueList</i> - One or more values to evaluate against the
--   supplied attribute. The number of values in the list depends on the
--   operator specified in <i>ComparisonOperator</i> . For type Number,
--   value comparisons are numeric. String value comparisons for greater
--   than, equals, or less than are based on ASCII character code values.
--   For example, <tt>a</tt> is greater than <tt>A</tt> , and <tt>a</tt> is
--   greater than <tt>B</tt> . For a list of code values, see
--   <a>http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters</a> .
--   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 <a>JSON Data Format</a> in the <i>Amazon
--   DynamoDB Developer Guide</i> . * <i>ComparisonOperator</i> - A
--   comparator for evaluating attributes. For example, equals, greater
--   than, less than, etc. The following comparison operators are
--   available: <tt>EQ | NE | LE | LT | GE | GT | NOT_NULL | NULL |
--   CONTAINS | NOT_CONTAINS | BEGINS_WITH | IN | BETWEEN</tt> For complete
--   descriptions of all comparison operators, see the <a>Condition</a>
--   data type.
qQueryFilter :: Lens' Query (HashMap Text Condition)

-- | Determines the read consistency model: If set to <tt>true</tt> , then
--   the operation uses strongly consistent reads; otherwise, the operation
--   uses eventually consistent reads. Strongly consistent reads are not
--   supported on global secondary indexes. If you query a global secondary
--   index with <i>ConsistentRead</i> set to <tt>true</tt> , you will
--   receive a <i>ValidationException</i> .
qConsistentRead :: Lens' Query (Maybe Bool)

-- | One or more values that can be substituted in an expression. Use the
--   <b>:</b> (colon) character in an expression to dereference an
--   attribute value. For example, suppose that you wanted to check whether
--   the value of the <i>ProductStatus</i> attribute was one of the
--   following: <tt>Available | Backordered | Discontinued</tt> You would
--   first need to specify <i>ExpressionAttributeValues</i> as follows:
--   <tt>{ ":avail":{<a>S</a>:<a>Available</a>},
--   ":back":{<a>S</a>:<a>Backordered</a>},
--   ":disc":{<a>S</a>:<a>Discontinued</a>} }</tt> You could then use these
--   values in an expression, such as this: <tt>ProductStatus IN (:avail,
--   :back, :disc)</tt> For more information on expression attribute
--   values, see <a>Specifying Conditions</a> in the <i>Amazon DynamoDB
--   Developer Guide</i> .
qExpressionAttributeValues :: Lens' Query (HashMap Text AttributeValue)

-- | Undocumented member.
qReturnConsumedCapacity :: Lens' Query (Maybe ReturnConsumedCapacity)

-- | Specifies the order for index traversal: If <tt>true</tt> (default),
--   the traversal is performed in ascending order; if <tt>false</tt> , the
--   traversal is performed in descending order. Items with the same
--   partition key value are stored in sorted order by sort key. If the
--   sort key data type is Number, the results are stored in numeric order.
--   For type String, the results are stored in order of ASCII character
--   code values. For type Binary, DynamoDB treats each byte of the binary
--   data as unsigned. If <i>ScanIndexForward</i> is <tt>true</tt> ,
--   DynamoDB returns the results in the order in which they are stored (by
--   sort key value). This is the default behavior. If
--   <i>ScanIndexForward</i> is <tt>false</tt> , DynamoDB reads the results
--   in reverse order by sort key value, and then returns the results to
--   the client.
qScanIndexForward :: Lens' Query (Maybe Bool)

-- | The maximum number of items to evaluate (not necessarily the number of
--   matching items). If DynamoDB processes the number of items up to the
--   limit while processing the results, it stops the operation and returns
--   the matching values up to that point, and a key in
--   <i>LastEvaluatedKey</i> to apply in a subsequent operation, so that
--   you can pick up where you left off. Also, if the processed data set
--   size exceeds 1 MB before DynamoDB reaches this limit, it stops the
--   operation and returns the matching values up to the limit, and a key
--   in <i>LastEvaluatedKey</i> to apply in a subsequent operation to
--   continue the operation. For more information, see <a>Query and
--   Scan</a> in the <i>Amazon DynamoDB Developer Guide</i> .
qLimit :: Lens' Query (Maybe Natural)

-- | The attributes to be returned in the result. You can retrieve all item
--   attributes, specific item attributes, the count of matching items, or
--   in the case of an index, some or all of the attributes projected into
--   the index. * <tt>ALL_ATTRIBUTES</tt> - Returns all of the item
--   attributes from the specified table or index. If you query a local
--   secondary index, then for each matching item in the index DynamoDB
--   will fetch the entire item from the parent table. If the index is
--   configured to project all item attributes, then all of the data can be
--   obtained from the local secondary index, and no fetching is required.
--   * <tt>ALL_PROJECTED_ATTRIBUTES</tt> - Allowed only when querying an
--   index. Retrieves all attributes that have been projected into the
--   index. If the index is configured to project all attributes, this
--   return value is equivalent to specifying <tt>ALL_ATTRIBUTES</tt> . *
--   <tt>COUNT</tt> - Returns the number of matching items, rather than the
--   matching items themselves. * <tt>SPECIFIC_ATTRIBUTES</tt> - Returns
--   only the attributes listed in <i>AttributesToGet</i> . This return
--   value is equivalent to specifying <i>AttributesToGet</i> without
--   specifying any value for <i>Select</i> . If you query a local
--   secondary index and request only attributes that are projected into
--   that index, the operation will read only the index and not the table.
--   If any of the requested attributes are not projected into the local
--   secondary index, DynamoDB will fetch each of these attributes from the
--   parent table. This extra fetching incurs additional throughput cost
--   and latency. If you query a global secondary index, you can only
--   request attributes that are projected into the index. Global secondary
--   index queries cannot fetch attributes from the parent table. If
--   neither <i>Select</i> nor <i>AttributesToGet</i> are specified,
--   DynamoDB defaults to <tt>ALL_ATTRIBUTES</tt> when accessing a table,
--   and <tt>ALL_PROJECTED_ATTRIBUTES</tt> when accessing an index. You
--   cannot use both <i>Select</i> and <i>AttributesToGet</i> together in a
--   single request, unless the value for <i>Select</i> is
--   <tt>SPECIFIC_ATTRIBUTES</tt> . (This usage is equivalent to specifying
--   <i>AttributesToGet</i> without any value for <i>Select</i> .)
qSelect :: Lens' Query (Maybe Select)

-- | The condition that specifies the key value(s) for items to be
--   retrieved by the <i>Query</i> action. The condition must perform an
--   equality test on a single partition key value. The condition can also
--   perform one of several comparison tests on a single sort key value.
--   <i>Query</i> can use <i>KeyConditionExpression</i> to retrieve one
--   item with a given partition key value and sort key value, or several
--   items that have the same partition key value but different sort key
--   values. The partition key equality test is required, and must be
--   specified in the following format: <tt>partitionKeyName</tt> <i>=</i>
--   <tt>:partitionkeyval</tt> If you also want to provide a condition for
--   the sort key, it must be combined using <i>AND</i> with the condition
--   for the sort key. Following is an example, using the <b>=</b>
--   comparison operator for the sort key: <tt>partitionKeyName</tt>
--   <i>=</i> <tt>:partitionkeyval</tt> <i>AND</i> <tt>sortKeyName</tt>
--   <i>=</i> <tt>:sortkeyval</tt> Valid comparisons for the sort key
--   condition are as follows: * <tt>sortKeyName</tt> <i>=</i>
--   <tt>:sortkeyval</tt> - true if the sort key value is equal to
--   <tt>:sortkeyval</tt> . * <tt>sortKeyName</tt> <i>&lt;</i>
--   <tt>:sortkeyval</tt> - true if the sort key value is less than
--   <tt>:sortkeyval</tt> . * <tt>sortKeyName</tt> <i>&lt;=</i>
--   <tt>:sortkeyval</tt> - true if the sort key value is less than or
--   equal to <tt>:sortkeyval</tt> . * <tt>sortKeyName</tt> <i>&gt;</i>
--   <tt>:sortkeyval</tt> - true if the sort key value is greater than
--   <tt>:sortkeyval</tt> . * <tt>sortKeyName</tt> <i>&gt;= </i>
--   <tt>:sortkeyval</tt> - true if the sort key value is greater than or
--   equal to <tt>:sortkeyval</tt> . * <tt>sortKeyName</tt> <i>BETWEEN</i>
--   <tt>:sortkeyval1</tt> <i>AND</i> <tt>:sortkeyval2</tt> - true if the
--   sort key value is greater than or equal to <tt>:sortkeyval1</tt> , and
--   less than or equal to <tt>:sortkeyval2</tt> . * <i>begins_with (</i>
--   <tt>sortKeyName</tt> , <tt>:sortkeyval</tt> <i>)</i> - true if the
--   sort key value begins with a particular operand. (You cannot use this
--   function with a sort key that is of type Number.) Note that the
--   function name <tt>begins_with</tt> is case-sensitive. Use the
--   <i>ExpressionAttributeValues</i> parameter to replace tokens such as
--   <tt>:partitionval</tt> and <tt>:sortval</tt> with actual values at
--   runtime. You can optionally use the <i>ExpressionAttributeNames</i>
--   parameter to replace the names of the partition key and sort key with
--   placeholder tokens. This option might be necessary if an attribute
--   name conflicts with a DynamoDB reserved word. For example, the
--   following <i>KeyConditionExpression</i> parameter causes an error
--   because <i>Size</i> is a reserved word: * <tt>Size = :myval</tt> To
--   work around this, define a placeholder (such a <tt>#S</tt> ) to
--   represent the attribute name <i>Size</i> .
--   <i>KeyConditionExpression</i> then is as follows: * <tt>#S =
--   :myval</tt> For a list of reserved words, see <a>Reserved Words</a> in
--   the <i>Amazon DynamoDB Developer Guide</i> . For more information on
--   <i>ExpressionAttributeNames</i> and <i>ExpressionAttributeValues</i> ,
--   see <a>Using Placeholders for Attribute Names and Values</a> in the
--   <i>Amazon DynamoDB Developer Guide</i> .
qKeyConditionExpression :: Lens' Query (Maybe Text)

-- | <i>Important:</i> This is a legacy parameter, for backward
--   compatibility. New applications should use <i>FilterExpression</i>
--   instead. Do not combine legacy parameters and expression parameters in
--   a single API call; otherwise, DynamoDB will return a
--   <i>ValidationException</i> exception. A logical operator to apply to
--   the conditions in a <i>QueryFilter</i> map: * <tt>AND</tt> - If all of
--   the conditions evaluate to true, then the entire map evaluates to
--   true. * <tt>OR</tt> - If at least one of the conditions evaluate to
--   true, then the entire map evaluates to true. If you omit
--   <i>ConditionalOperator</i> , then <tt>AND</tt> is the default. The
--   operation will succeed only if the entire map evaluates to true.
qConditionalOperator :: Lens' Query (Maybe ConditionalOperator)

-- | The primary key of the first item that this operation will evaluate.
--   Use the value that was returned for <i>LastEvaluatedKey</i> in the
--   previous operation. The data type for <i>ExclusiveStartKey</i> must be
--   String, Number or Binary. No set data types are allowed.
qExclusiveStartKey :: Lens' Query (HashMap Text AttributeValue)

-- | The name of an index to query. This index can be any local secondary
--   index or global secondary index on the table. Note that if you use the
--   <i>IndexName</i> parameter, you must also provide <i>TableName.</i>
qIndexName :: Lens' Query (Maybe Text)

-- | The name of the table containing the requested items.
qTableName :: Lens' Query Text

-- | Creates a value of <a>QueryResponse</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>qrsLastEvaluatedKey</a> - The primary key of the item where the
--   operation stopped, inclusive of the previous result set. Use this
--   value to start a new operation, excluding this value in the new
--   request. If <i>LastEvaluatedKey</i> is empty, then the "last page" of
--   results has been processed and there is no more data to be retrieved.
--   If <i>LastEvaluatedKey</i> is not empty, it does not necessarily mean
--   that there is more data in the result set. The only way to know when
--   you have reached the end of the result set is when
--   <i>LastEvaluatedKey</i> is empty.</li>
--   <li><a>qrsCount</a> - The number of items in the response. If you used
--   a <i>QueryFilter</i> in the request, then <i>Count</i> is the number
--   of items returned after the filter was applied, and
--   <i>ScannedCount</i> is the number of matching items before the filter
--   was applied. If you did not use a filter in the request, then
--   <i>Count</i> and <i>ScannedCount</i> are the same.</li>
--   <li><a>qrsScannedCount</a> - The number of items evaluated, before any
--   <i>QueryFilter</i> is applied. A high <i>ScannedCount</i> value with
--   few, or no, <i>Count</i> results indicates an inefficient <i>Query</i>
--   operation. For more information, see <a>Count and ScannedCount</a> in
--   the <i>Amazon DynamoDB Developer Guide</i> . If you did not use a
--   filter in the request, then <i>ScannedCount</i> is the same as
--   <i>Count</i> .</li>
--   <li><a>qrsItems</a> - An array of item attributes that match the query
--   criteria. Each element in this array consists of an attribute name and
--   the value for that attribute.</li>
--   <li><a>qrsConsumedCapacity</a> - Undocumented member.</li>
--   <li><a>qrsResponseStatus</a> - -- | The response status code.</li>
--   </ul>
queryResponse :: Int -> QueryResponse

-- | Represents the output of a <i>Query</i> operation.
--   
--   <i>See:</i> <a>queryResponse</a> smart constructor.
data QueryResponse

-- | The primary key of the item where the operation stopped, inclusive of
--   the previous result set. Use this value to start a new operation,
--   excluding this value in the new request. If <i>LastEvaluatedKey</i> is
--   empty, then the "last page" of results has been processed and there is
--   no more data to be retrieved. If <i>LastEvaluatedKey</i> is not empty,
--   it does not necessarily mean that there is more data in the result
--   set. The only way to know when you have reached the end of the result
--   set is when <i>LastEvaluatedKey</i> is empty.
qrsLastEvaluatedKey :: Lens' QueryResponse (HashMap Text AttributeValue)

-- | The number of items in the response. If you used a <i>QueryFilter</i>
--   in the request, then <i>Count</i> is the number of items returned
--   after the filter was applied, and <i>ScannedCount</i> is the number of
--   matching items before the filter was applied. If you did not use a
--   filter in the request, then <i>Count</i> and <i>ScannedCount</i> are
--   the same.
qrsCount :: Lens' QueryResponse (Maybe Int)

-- | The number of items evaluated, before any <i>QueryFilter</i> is
--   applied. A high <i>ScannedCount</i> value with few, or no,
--   <i>Count</i> results indicates an inefficient <i>Query</i> operation.
--   For more information, see <a>Count and ScannedCount</a> in the
--   <i>Amazon DynamoDB Developer Guide</i> . If you did not use a filter
--   in the request, then <i>ScannedCount</i> is the same as <i>Count</i> .
qrsScannedCount :: Lens' QueryResponse (Maybe Int)

-- | An array of item attributes that match the query criteria. Each
--   element in this array consists of an attribute name and the value for
--   that attribute.
qrsItems :: Lens' QueryResponse [HashMap Text AttributeValue]

-- | Undocumented member.
qrsConsumedCapacity :: Lens' QueryResponse (Maybe ConsumedCapacity)

-- | <ul>
--   <li>- | The response status code.</li>
--   </ul>
qrsResponseStatus :: Lens' QueryResponse Int
instance GHC.Generics.Generic Network.AWS.DynamoDB.Query.QueryResponse
instance Data.Data.Data Network.AWS.DynamoDB.Query.QueryResponse
instance GHC.Show.Show Network.AWS.DynamoDB.Query.QueryResponse
instance GHC.Read.Read Network.AWS.DynamoDB.Query.QueryResponse
instance GHC.Classes.Eq Network.AWS.DynamoDB.Query.QueryResponse
instance GHC.Generics.Generic Network.AWS.DynamoDB.Query.Query
instance Data.Data.Data Network.AWS.DynamoDB.Query.Query
instance GHC.Show.Show Network.AWS.DynamoDB.Query.Query
instance GHC.Read.Read Network.AWS.DynamoDB.Query.Query
instance GHC.Classes.Eq Network.AWS.DynamoDB.Query.Query
instance Network.AWS.Pager.AWSPager Network.AWS.DynamoDB.Query.Query
instance Network.AWS.Types.AWSRequest Network.AWS.DynamoDB.Query.Query
instance Data.Hashable.Class.Hashable Network.AWS.DynamoDB.Query.Query
instance Control.DeepSeq.NFData Network.AWS.DynamoDB.Query.Query
instance Network.AWS.Data.Headers.ToHeaders Network.AWS.DynamoDB.Query.Query
instance Data.Aeson.Types.ToJSON.ToJSON Network.AWS.DynamoDB.Query.Query
instance Network.AWS.Data.Path.ToPath Network.AWS.DynamoDB.Query.Query
instance Network.AWS.Data.Query.ToQuery Network.AWS.DynamoDB.Query.Query
instance Control.DeepSeq.NFData Network.AWS.DynamoDB.Query.QueryResponse


-- | Creates a new item, or replaces an old item with a new item. If an
--   item that has the same primary key as the new item already exists in
--   the specified table, the new item completely replaces the existing
--   item. You can perform a conditional put operation (add a new item if
--   one with the specified primary key doesn't exist), or replace an
--   existing item if it has certain attribute values.
--   
--   In addition to putting an item, you can also return the item's
--   attribute values in the same operation, using the <i>ReturnValues</i>
--   parameter.
--   
--   When you add an item, the primary key attribute(s) are the only
--   required attributes. Attribute values cannot be null. String and
--   Binary type attributes must have lengths greater than zero. Set type
--   attributes cannot be empty. Requests with empty values will be
--   rejected with a <i>ValidationException</i> exception.
--   
--   You can request that <i>PutItem</i> return either a copy of the
--   original item (before the update) or a copy of the updated item (after
--   the update). For more information, see the <i>ReturnValues</i>
--   description below.
--   
--   For more information about using this API, see <a>Working with
--   Items</a> in the <i>Amazon DynamoDB Developer Guide</i> .
module Network.AWS.DynamoDB.PutItem

-- | Creates a value of <a>PutItem</a> with the minimum fields required to
--   make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>piExpressionAttributeNames</a> - One or more substitution
--   tokens for attribute names in an expression. The following are some
--   use cases for using <i>ExpressionAttributeNames</i> : * To access an
--   attribute whose name conflicts with a DynamoDB reserved word. * To
--   create a placeholder for repeating occurrences of an attribute name in
--   an expression. * To prevent special characters in an attribute name
--   from being misinterpreted in an expression. Use the <b>#</b> character
--   in an expression to dereference an attribute name. For example,
--   consider the following attribute name: * <tt>Percentile</tt> The name
--   of this attribute conflicts with a reserved word, so it cannot be used
--   directly in an expression. (For the complete list of reserved words,
--   see <a>Reserved Words</a> in the <i>Amazon DynamoDB Developer
--   Guide</i> ). To work around this, you could specify the following for
--   <i>ExpressionAttributeNames</i> : * <tt>{"#P":<a>Percentile</a>}</tt>
--   You could then use this substitution in an expression, as in this
--   example: * <tt>#P = :val</tt> For more information on expression
--   attribute names, see <a>Accessing Item Attributes</a> in the <i>Amazon
--   DynamoDB Developer Guide</i> .</li>
--   <li><a>piReturnValues</a> - Use <i>ReturnValues</i> if you want to get
--   the item attributes as they appeared before they were updated with the
--   <i>PutItem</i> request. For <i>PutItem</i> , the valid values are: *
--   <tt>NONE</tt> - If <i>ReturnValues</i> is not specified, or if its
--   value is <tt>NONE</tt> , then nothing is returned. (This setting is
--   the default for <i>ReturnValues</i> .) * <tt>ALL_OLD</tt> - If
--   <i>PutItem</i> overwrote an attribute name-value pair, then the
--   content of the old item is returned.</li>
--   <li><a>piExpressionAttributeValues</a> - One or more values that can
--   be substituted in an expression. Use the <b>:</b> (colon) character in
--   an expression to dereference an attribute value. For example, suppose
--   that you wanted to check whether the value of the <i>ProductStatus</i>
--   attribute was one of the following: <tt>Available | Backordered |
--   Discontinued</tt> You would first need to specify
--   <i>ExpressionAttributeValues</i> as follows: <tt>{
--   ":avail":{<a>S</a>:<a>Available</a>},
--   ":back":{<a>S</a>:<a>Backordered</a>},
--   ":disc":{<a>S</a>:<a>Discontinued</a>} }</tt> You could then use these
--   values in an expression, such as this: <tt>ProductStatus IN (:avail,
--   :back, :disc)</tt> For more information on expression attribute
--   values, see <a>Specifying Conditions</a> in the <i>Amazon DynamoDB
--   Developer Guide</i> .</li>
--   <li><a>piReturnConsumedCapacity</a> - Undocumented member.</li>
--   <li><a>piReturnItemCollectionMetrics</a> - Determines whether item
--   collection metrics are returned. If set to <tt>SIZE</tt> , the
--   response includes statistics about item collections, if any, that were
--   modified during the operation are returned in the response. If set to
--   <tt>NONE</tt> (the default), no statistics are returned.</li>
--   <li><a>piConditionExpression</a> - A condition that must be satisfied
--   in order for a conditional <i>PutItem</i> operation to succeed. An
--   expression can contain any of the following: * Functions:
--   <tt>attribute_exists | attribute_not_exists | attribute_type |
--   contains | begins_with | size</tt> These function names are
--   case-sensitive. * Comparison operators: <tt>= | &lt;&gt; | &lt; | &gt;
--   | &lt;= | &gt;= | BETWEEN | IN</tt> * Logical operators: <tt>AND | OR
--   | NOT</tt> For more information on condition expressions, see
--   <a>Specifying Conditions</a> in the <i>Amazon DynamoDB Developer
--   Guide</i> .</li>
--   <li><a>piConditionalOperator</a> - <i>Important:</i> This is a legacy
--   parameter, for backward compatibility. New applications should use
--   <i>ConditionExpression</i> instead. Do not combine legacy parameters
--   and expression parameters in a single API call; otherwise, DynamoDB
--   will return a <i>ValidationException</i> exception. A logical operator
--   to apply to the conditions in the <i>Expected</i> map: * <tt>AND</tt>
--   - If all of the conditions evaluate to true, then the entire map
--   evaluates to true. * <tt>OR</tt> - If at least one of the conditions
--   evaluate to true, then the entire map evaluates to true. If you omit
--   <i>ConditionalOperator</i> , then <tt>AND</tt> is the default. The
--   operation will succeed only if the entire map evaluates to true.</li>
--   <li><a>piExpected</a> - <i>Important:</i> This is a legacy parameter,
--   for backward compatibility. New applications should use
--   <i>ConditionExpression</i> instead. Do not combine legacy parameters
--   and expression parameters in a single API call; otherwise, DynamoDB
--   will return a <i>ValidationException</i> exception. A map of
--   attribute<i>condition pairs. </i>Expected<i> provides a conditional
--   block for the </i>PutItem<i> operation. Each element of
--   </i>Expected<i> consists of an attribute name, a comparison operator,
--   and one or more values. DynamoDB compares the attribute with the
--   value(s) you supplied, using the comparison operator. For each
--   </i>Expected<i> element, the result of the evaluation is either true
--   or false. If you specify more than one element in the </i>Expected<i>
--   map, then by default all of the conditions must evaluate to true. In
--   other words, the conditions are ANDed together. (You can use the
--   </i>ConditionalOperator<i> 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.) If the </i>Expected<i> map evaluates
--   to true, then the conditional operation succeeds; otherwise, it fails.
--   </i>Expected<i> contains the following: * </i>AttributeValueList<i> -
--   One or more values to evaluate against the supplied attribute. The
--   number of values in the list depends on the </i>ComparisonOperator<i>
--   being used. For type Number, value comparisons are numeric. String
--   value comparisons for greater than, equals, or less than are based on
--   ASCII character code values. For example, <tt>a</tt> is greater than
--   <tt>A</tt> , and <tt>a</tt> is greater than <tt>B</tt> . For a list of
--   code values, see
--   &lt;http:</i><i>en.wikipedia.org</i>wiki<i>ASCII#ASCII_printable_characters
--   http:</i><i>en.wikipedia.org</i>wiki<i>ASCII#ASCII_printable_characters&gt;
--   . For type Binary, DynamoDB treats each byte of the binary data as
--   unsigned when it compares binary values. * </i>ComparisonOperator<i> -
--   A comparator for evaluating attributes in the
--   </i>AttributeValueList<i> . When performing the comparison, DynamoDB
--   uses strongly consistent reads. The following comparison operators are
--   available: <tt>EQ | NE | LE | LT | GE | GT | NOT_NULL | NULL |
--   CONTAINS | NOT_CONTAINS | BEGINS_WITH | IN | BETWEEN</tt> The
--   following are descriptions of each comparison operator. * <tt>EQ</tt>
--   : Equal. <tt>EQ</tt> is supported for all datatypes, including lists
--   and maps. </i>AttributeValueList<i> can contain only one
--   </i>AttributeValue<i> element of type String, Number, Binary, String
--   Set, Number Set, or Binary Set. If an item contains an
--   </i>AttributeValue<i> element of a different type than the one
--   provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>NE</tt> : Not equal. <tt>NE</tt> is supported for
--   all datatypes, including lists and maps. </i>AttributeValueList<i> can
--   contain only one </i>AttributeValue<i> of type String, Number, Binary,
--   String Set, Number Set, or Binary Set. If an item contains an
--   </i>AttributeValue<i> of a different type than the one provided in the
--   request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LE</tt> : Less than or equal.
--   </i>AttributeValueList<i> can contain only one </i>AttributeValue<i>
--   element of type String, Number, or Binary (not a set type). If an item
--   contains an </i>AttributeValue<i> element of a different type than the
--   one provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LT</tt> : Less than. </i>AttributeValueList<i> can
--   contain only one </i>AttributeValue<i> of type String, Number, or
--   Binary (not a set type). If an item contains an </i>AttributeValue<i>
--   element of a different type than the one provided in the request, the
--   value does not match. For example, <tt>{<a>S</a>:"6"}</tt> does not
--   equal <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GE</tt> :
--   Greater than or equal. </i>AttributeValueList<i> can contain only one
--   </i>AttributeValue<i> element of type String, Number, or Binary (not a
--   set type). If an item contains an </i>AttributeValue<i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GT</tt> :
--   Greater than. </i>AttributeValueList<i> can contain only one
--   </i>AttributeValue<i> element of type String, Number, or Binary (not a
--   set type). If an item contains an </i>AttributeValue<i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>NOT_NULL</tt>
--   : The attribute exists. <tt>NOT_NULL</tt> is supported for all
--   datatypes, including lists and maps. * <tt>NULL</tt> : The attribute
--   does not exist. <tt>NULL</tt> is supported for all datatypes,
--   including lists and maps. * <tt>CONTAINS</tt> : Checks for a
--   subsequence, or value in a set. </i>AttributeValueList<i> can contain
--   only one </i>AttributeValue<i> element of type String, Number, or
--   Binary (not a set type). If the target attribute of the comparison is
--   of type String, then the operator checks for a substring match. If the
--   target attribute of the comparison is of type Binary, then the
--   operator looks for a subsequence of the target that matches the input.
--   If the target attribute of the comparison is a set ("<tt>SS</tt> ",
--   "<tt>NS</tt> ", or "<tt>BS</tt> "), then the operator evaluates to
--   true if it finds an exact match with any member of the set. CONTAINS
--   is supported for lists: When evaluating "<tt>a CONTAINS b</tt> ",
--   "<tt>a</tt> " can be a list; however, "<tt>b</tt> " cannot be a set, a
--   map, or a list. * <tt>NOT_CONTAINS</tt> : Checks for absence of a
--   subsequence, or absence of a value in a set. </i>AttributeValueList<i>
--   can contain only one </i>AttributeValue<i> element of type String,
--   Number, or Binary (not a set type). If the target attribute of the
--   comparison is a String, then the operator checks for the absence of a
--   substring match. If the target attribute of the comparison is Binary,
--   then the operator checks for the absence of a subsequence of the
--   target that matches the input. If the target attribute of the
--   comparison is a set ("<tt>SS</tt> ", "<tt>NS</tt> ", or "<tt>BS</tt>
--   "), then the operator evaluates to true if it </i>does not<i> find an
--   exact match with any member of the set. NOT_CONTAINS is supported for
--   lists: When evaluating "<tt>a NOT CONTAINS b</tt> ", "<tt>a</tt> " can
--   be a list; however, "<tt>b</tt> " cannot be a set, a map, or a list. *
--   <tt>BEGINS_WITH</tt> : Checks for a prefix. </i>AttributeValueList<i>
--   can contain only one </i>AttributeValue<i> of type String or Binary
--   (not a Number or a set type). The target attribute of the comparison
--   must be of type String or Binary (not a Number or a set type). *
--   <tt>IN</tt> : Checks for matching elements within two sets.
--   </i>AttributeValueList<i> can contain one or more
--   </i>AttributeValue<i> elements of type String, Number, or Binary (not
--   a set type). These attributes are compared against an existing set
--   type attribute of an item. If any elements of the input set are
--   present in the item attribute, the expression evaluates to true. *
--   <tt>BETWEEN</tt> : Greater than or equal to the first value, and less
--   than or equal to the second value. </i>AttributeValueList<i> must
--   contain two </i>AttributeValue<i> elements of the same type, either
--   String, Number, or Binary (not a set type). A target attribute matches
--   if the target value is greater than, or equal to, the first element
--   and less than, or equal to, the second element. If an item contains an
--   </i>AttributeValue<i> element of a different type than the one
--   provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not compare to <tt>{<a>N</a>:"6"}</tt> .
--   Also, <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6",
--   "2", "1"]}</tt> For usage examples of </i>AttributeValueList<i> and
--   </i>ComparisonOperator<i> , see
--   &lt;http:</i><i>docs.aws.amazon.com</i>amazondynamodb<i>latest</i>developerguide<i>LegacyConditionalParameters.html
--   Legacy Conditional Parameters&gt; in the </i>Amazon DynamoDB Developer
--   Guide<i> . For backward compatibility with previous DynamoDB releases,
--   the following parameters can be used instead of
--   </i>AttributeValueList<i> and </i>ComparisonOperator<i> : *
--   </i>Value<i> - A value for DynamoDB to compare with an attribute. *
--   </i>Exists<i> - A Boolean value that causes DynamoDB to evaluate the
--   value before attempting the conditional operation: * If </i>Exists<i>
--   is <tt>true</tt> , DynamoDB will check to see if that attribute value
--   already exists in the table. If it is found, then the condition
--   evaluates to true; otherwise the condition evaluate to false. * If
--   </i>Exists<i> is <tt>false</tt> , DynamoDB assumes that the attribute
--   value does </i>not<i> exist in the table. If in fact the value does
--   not exist, then the assumption is valid and the condition evaluates to
--   true. If the value is found, despite the assumption that it does not
--   exist, the condition evaluates to false. Note that the default value
--   for </i>Exists<i> is <tt>true</tt> . The </i>Value<i> and
--   </i>Exists<i> parameters are incompatible with
--   </i>AttributeValueList<i> and </i>ComparisonOperator<i> . Note that if
--   you use both sets of parameters at once, DynamoDB will return a
--   </i>ValidationException/ exception.</li>
--   <li><a>piTableName</a> - The name of the table to contain the
--   item.</li>
--   <li><a>piItem</a> - A map of attribute name<i>value pairs, one for
--   each attribute. Only the primary key attributes are required; you can
--   optionally provide other attribute name-value pairs for the item. You
--   must provide all of the attributes for the primary key. For example,
--   with a simple primary key, you only need to provide a value for the
--   partition key. For a composite primary key, you must provide both
--   values for both the partition key and the sort key. If you specify any
--   attributes that are part of an index key, then the data types for
--   those attributes must match those of the schema in the table's
--   attribute definition. For more information about primary keys, see
--   &lt;http:</i><i>docs.aws.amazon.com</i>amazondynamodb<i>latest</i>developerguide<i>DataModel.html#DataModelPrimaryKey
--   Primary Key&gt; in the </i>Amazon DynamoDB Developer Guide<i> . Each
--   element in the </i>Item<i> map is an </i>AttributeValue/ object.</li>
--   </ul>
putItem :: Text -> PutItem

-- | Represents the input of a <i>PutItem</i> operation.
--   
--   <i>See:</i> <a>putItem</a> smart constructor.
data PutItem

-- | One or more substitution tokens for attribute names in an expression.
--   The following are some use cases for using
--   <i>ExpressionAttributeNames</i> : * To access an attribute whose name
--   conflicts with a DynamoDB reserved word. * To create a placeholder for
--   repeating occurrences of an attribute name in an expression. * To
--   prevent special characters in an attribute name from being
--   misinterpreted in an expression. Use the <b>#</b> character in an
--   expression to dereference an attribute name. For example, consider the
--   following attribute name: * <tt>Percentile</tt> The name of this
--   attribute conflicts with a reserved word, so it cannot be used
--   directly in an expression. (For the complete list of reserved words,
--   see <a>Reserved Words</a> in the <i>Amazon DynamoDB Developer
--   Guide</i> ). To work around this, you could specify the following for
--   <i>ExpressionAttributeNames</i> : * <tt>{"#P":<a>Percentile</a>}</tt>
--   You could then use this substitution in an expression, as in this
--   example: * <tt>#P = :val</tt> For more information on expression
--   attribute names, see <a>Accessing Item Attributes</a> in the <i>Amazon
--   DynamoDB Developer Guide</i> .
piExpressionAttributeNames :: Lens' PutItem (HashMap Text Text)

-- | Use <i>ReturnValues</i> if you want to get the item attributes as they
--   appeared before they were updated with the <i>PutItem</i> request. For
--   <i>PutItem</i> , the valid values are: * <tt>NONE</tt> - If
--   <i>ReturnValues</i> is not specified, or if its value is <tt>NONE</tt>
--   , then nothing is returned. (This setting is the default for
--   <i>ReturnValues</i> .) * <tt>ALL_OLD</tt> - If <i>PutItem</i>
--   overwrote an attribute name-value pair, then the content of the old
--   item is returned.
piReturnValues :: Lens' PutItem (Maybe ReturnValue)

-- | One or more values that can be substituted in an expression. Use the
--   <b>:</b> (colon) character in an expression to dereference an
--   attribute value. For example, suppose that you wanted to check whether
--   the value of the <i>ProductStatus</i> attribute was one of the
--   following: <tt>Available | Backordered | Discontinued</tt> You would
--   first need to specify <i>ExpressionAttributeValues</i> as follows:
--   <tt>{ ":avail":{<a>S</a>:<a>Available</a>},
--   ":back":{<a>S</a>:<a>Backordered</a>},
--   ":disc":{<a>S</a>:<a>Discontinued</a>} }</tt> You could then use these
--   values in an expression, such as this: <tt>ProductStatus IN (:avail,
--   :back, :disc)</tt> For more information on expression attribute
--   values, see <a>Specifying Conditions</a> in the <i>Amazon DynamoDB
--   Developer Guide</i> .
piExpressionAttributeValues :: Lens' PutItem (HashMap Text AttributeValue)

-- | Undocumented member.
piReturnConsumedCapacity :: Lens' PutItem (Maybe ReturnConsumedCapacity)

-- | Determines whether item collection metrics are returned. If set to
--   <tt>SIZE</tt> , the response includes statistics about item
--   collections, if any, that were modified during the operation are
--   returned in the response. If set to <tt>NONE</tt> (the default), no
--   statistics are returned.
piReturnItemCollectionMetrics :: Lens' PutItem (Maybe ReturnItemCollectionMetrics)

-- | A condition that must be satisfied in order for a conditional
--   <i>PutItem</i> operation to succeed. An expression can contain any of
--   the following: * Functions: <tt>attribute_exists |
--   attribute_not_exists | attribute_type | contains | begins_with |
--   size</tt> These function names are case-sensitive. * Comparison
--   operators: <tt>= | &lt;&gt; | &lt; | &gt; | &lt;= | &gt;= | BETWEEN |
--   IN</tt> * Logical operators: <tt>AND | OR | NOT</tt> For more
--   information on condition expressions, see <a>Specifying Conditions</a>
--   in the <i>Amazon DynamoDB Developer Guide</i> .
piConditionExpression :: Lens' PutItem (Maybe Text)

-- | <i>Important:</i> This is a legacy parameter, for backward
--   compatibility. New applications should use <i>ConditionExpression</i>
--   instead. Do not combine legacy parameters and expression parameters in
--   a single API call; otherwise, DynamoDB will return a
--   <i>ValidationException</i> exception. A logical operator to apply to
--   the conditions in the <i>Expected</i> map: * <tt>AND</tt> - If all of
--   the conditions evaluate to true, then the entire map evaluates to
--   true. * <tt>OR</tt> - If at least one of the conditions evaluate to
--   true, then the entire map evaluates to true. If you omit
--   <i>ConditionalOperator</i> , then <tt>AND</tt> is the default. The
--   operation will succeed only if the entire map evaluates to true.
piConditionalOperator :: Lens' PutItem (Maybe ConditionalOperator)

-- | <i>Important:</i> This is a legacy parameter, for backward
--   compatibility. New applications should use <i>ConditionExpression</i>
--   instead. Do not combine legacy parameters and expression parameters in
--   a single API call; otherwise, DynamoDB will return a
--   <i>ValidationException</i> exception. A map of attribute<i>condition
--   pairs. </i>Expected<i> provides a conditional block for the
--   </i>PutItem<i> operation. Each element of </i>Expected<i> consists of
--   an attribute name, a comparison operator, and one or more values.
--   DynamoDB compares the attribute with the value(s) you supplied, using
--   the comparison operator. For each </i>Expected<i> element, the result
--   of the evaluation is either true or false. If you specify more than
--   one element in the </i>Expected<i> map, then by default all of the
--   conditions must evaluate to true. In other words, the conditions are
--   ANDed together. (You can use the </i>ConditionalOperator<i> 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.) If the
--   </i>Expected<i> map evaluates to true, then the conditional operation
--   succeeds; otherwise, it fails. </i>Expected<i> contains the following:
--   * </i>AttributeValueList<i> - One or more values to evaluate against
--   the supplied attribute. The number of values in the list depends on
--   the </i>ComparisonOperator<i> being used. For type Number, value
--   comparisons are numeric. String value comparisons for greater than,
--   equals, or less than are based on ASCII character code values. For
--   example, <tt>a</tt> is greater than <tt>A</tt> , and <tt>a</tt> is
--   greater than <tt>B</tt> . For a list of code values, see
--   &lt;http:</i><i>en.wikipedia.org</i>wiki<i>ASCII#ASCII_printable_characters
--   http:</i><i>en.wikipedia.org</i>wiki<i>ASCII#ASCII_printable_characters&gt;
--   . For type Binary, DynamoDB treats each byte of the binary data as
--   unsigned when it compares binary values. * </i>ComparisonOperator<i> -
--   A comparator for evaluating attributes in the
--   </i>AttributeValueList<i> . When performing the comparison, DynamoDB
--   uses strongly consistent reads. The following comparison operators are
--   available: <tt>EQ | NE | LE | LT | GE | GT | NOT_NULL | NULL |
--   CONTAINS | NOT_CONTAINS | BEGINS_WITH | IN | BETWEEN</tt> The
--   following are descriptions of each comparison operator. * <tt>EQ</tt>
--   : Equal. <tt>EQ</tt> is supported for all datatypes, including lists
--   and maps. </i>AttributeValueList<i> can contain only one
--   </i>AttributeValue<i> element of type String, Number, Binary, String
--   Set, Number Set, or Binary Set. If an item contains an
--   </i>AttributeValue<i> element of a different type than the one
--   provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>NE</tt> : Not equal. <tt>NE</tt> is supported for
--   all datatypes, including lists and maps. </i>AttributeValueList<i> can
--   contain only one </i>AttributeValue<i> of type String, Number, Binary,
--   String Set, Number Set, or Binary Set. If an item contains an
--   </i>AttributeValue<i> of a different type than the one provided in the
--   request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LE</tt> : Less than or equal.
--   </i>AttributeValueList<i> can contain only one </i>AttributeValue<i>
--   element of type String, Number, or Binary (not a set type). If an item
--   contains an </i>AttributeValue<i> element of a different type than the
--   one provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LT</tt> : Less than. </i>AttributeValueList<i> can
--   contain only one </i>AttributeValue<i> of type String, Number, or
--   Binary (not a set type). If an item contains an </i>AttributeValue<i>
--   element of a different type than the one provided in the request, the
--   value does not match. For example, <tt>{<a>S</a>:"6"}</tt> does not
--   equal <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GE</tt> :
--   Greater than or equal. </i>AttributeValueList<i> can contain only one
--   </i>AttributeValue<i> element of type String, Number, or Binary (not a
--   set type). If an item contains an </i>AttributeValue<i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GT</tt> :
--   Greater than. </i>AttributeValueList<i> can contain only one
--   </i>AttributeValue<i> element of type String, Number, or Binary (not a
--   set type). If an item contains an </i>AttributeValue<i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>NOT_NULL</tt>
--   : The attribute exists. <tt>NOT_NULL</tt> is supported for all
--   datatypes, including lists and maps. * <tt>NULL</tt> : The attribute
--   does not exist. <tt>NULL</tt> is supported for all datatypes,
--   including lists and maps. * <tt>CONTAINS</tt> : Checks for a
--   subsequence, or value in a set. </i>AttributeValueList<i> can contain
--   only one </i>AttributeValue<i> element of type String, Number, or
--   Binary (not a set type). If the target attribute of the comparison is
--   of type String, then the operator checks for a substring match. If the
--   target attribute of the comparison is of type Binary, then the
--   operator looks for a subsequence of the target that matches the input.
--   If the target attribute of the comparison is a set ("<tt>SS</tt> ",
--   "<tt>NS</tt> ", or "<tt>BS</tt> "), then the operator evaluates to
--   true if it finds an exact match with any member of the set. CONTAINS
--   is supported for lists: When evaluating "<tt>a CONTAINS b</tt> ",
--   "<tt>a</tt> " can be a list; however, "<tt>b</tt> " cannot be a set, a
--   map, or a list. * <tt>NOT_CONTAINS</tt> : Checks for absence of a
--   subsequence, or absence of a value in a set. </i>AttributeValueList<i>
--   can contain only one </i>AttributeValue<i> element of type String,
--   Number, or Binary (not a set type). If the target attribute of the
--   comparison is a String, then the operator checks for the absence of a
--   substring match. If the target attribute of the comparison is Binary,
--   then the operator checks for the absence of a subsequence of the
--   target that matches the input. If the target attribute of the
--   comparison is a set ("<tt>SS</tt> ", "<tt>NS</tt> ", or "<tt>BS</tt>
--   "), then the operator evaluates to true if it </i>does not<i> find an
--   exact match with any member of the set. NOT_CONTAINS is supported for
--   lists: When evaluating "<tt>a NOT CONTAINS b</tt> ", "<tt>a</tt> " can
--   be a list; however, "<tt>b</tt> " cannot be a set, a map, or a list. *
--   <tt>BEGINS_WITH</tt> : Checks for a prefix. </i>AttributeValueList<i>
--   can contain only one </i>AttributeValue<i> of type String or Binary
--   (not a Number or a set type). The target attribute of the comparison
--   must be of type String or Binary (not a Number or a set type). *
--   <tt>IN</tt> : Checks for matching elements within two sets.
--   </i>AttributeValueList<i> can contain one or more
--   </i>AttributeValue<i> elements of type String, Number, or Binary (not
--   a set type). These attributes are compared against an existing set
--   type attribute of an item. If any elements of the input set are
--   present in the item attribute, the expression evaluates to true. *
--   <tt>BETWEEN</tt> : Greater than or equal to the first value, and less
--   than or equal to the second value. </i>AttributeValueList<i> must
--   contain two </i>AttributeValue<i> elements of the same type, either
--   String, Number, or Binary (not a set type). A target attribute matches
--   if the target value is greater than, or equal to, the first element
--   and less than, or equal to, the second element. If an item contains an
--   </i>AttributeValue<i> element of a different type than the one
--   provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not compare to <tt>{<a>N</a>:"6"}</tt> .
--   Also, <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6",
--   "2", "1"]}</tt> For usage examples of </i>AttributeValueList<i> and
--   </i>ComparisonOperator<i> , see
--   &lt;http:</i><i>docs.aws.amazon.com</i>amazondynamodb<i>latest</i>developerguide<i>LegacyConditionalParameters.html
--   Legacy Conditional Parameters&gt; in the </i>Amazon DynamoDB Developer
--   Guide<i> . For backward compatibility with previous DynamoDB releases,
--   the following parameters can be used instead of
--   </i>AttributeValueList<i> and </i>ComparisonOperator<i> : *
--   </i>Value<i> - A value for DynamoDB to compare with an attribute. *
--   </i>Exists<i> - A Boolean value that causes DynamoDB to evaluate the
--   value before attempting the conditional operation: * If </i>Exists<i>
--   is <tt>true</tt> , DynamoDB will check to see if that attribute value
--   already exists in the table. If it is found, then the condition
--   evaluates to true; otherwise the condition evaluate to false. * If
--   </i>Exists<i> is <tt>false</tt> , DynamoDB assumes that the attribute
--   value does </i>not<i> exist in the table. If in fact the value does
--   not exist, then the assumption is valid and the condition evaluates to
--   true. If the value is found, despite the assumption that it does not
--   exist, the condition evaluates to false. Note that the default value
--   for </i>Exists<i> is <tt>true</tt> . The </i>Value<i> and
--   </i>Exists<i> parameters are incompatible with
--   </i>AttributeValueList<i> and </i>ComparisonOperator<i> . Note that if
--   you use both sets of parameters at once, DynamoDB will return a
--   </i>ValidationException/ exception.
piExpected :: Lens' PutItem (HashMap Text ExpectedAttributeValue)

-- | The name of the table to contain the item.
piTableName :: Lens' PutItem Text

-- | A map of attribute name<i>value pairs, one for each attribute. Only
--   the primary key attributes are required; you can optionally provide
--   other attribute name-value pairs for the item. You must provide all of
--   the attributes for the primary key. For example, with a simple primary
--   key, you only need to provide a value for the partition key. For a
--   composite primary key, you must provide both values for both the
--   partition key and the sort key. If you specify any attributes that are
--   part of an index key, then the data types for those attributes must
--   match those of the schema in the table's attribute definition. For
--   more information about primary keys, see
--   &lt;http:</i><i>docs.aws.amazon.com</i>amazondynamodb<i>latest</i>developerguide<i>DataModel.html#DataModelPrimaryKey
--   Primary Key&gt; in the </i>Amazon DynamoDB Developer Guide<i> . Each
--   element in the </i>Item<i> map is an </i>AttributeValue/ object.
piItem :: Lens' PutItem (HashMap Text AttributeValue)

-- | Creates a value of <a>PutItemResponse</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>pirsItemCollectionMetrics</a> - Information about item
--   collections, if any, that were affected by the operation.
--   <i>ItemCollectionMetrics</i> is only returned if the request asked for
--   it. If the table does not have any local secondary indexes, this
--   information is not returned in the response. Each
--   <i>ItemCollectionMetrics</i> element consists of: *
--   <i>ItemCollectionKey</i> - The partition key value of the item
--   collection. This is the same as the partition key value of the item
--   itself. * <i>SizeEstimateRange</i> - An estimate of item collection
--   size, in gigabytes. This value is a two-element array containing a
--   lower bound and an upper bound for the estimate. The estimate includes
--   the size of all the items in the table, plus the size of all
--   attributes projected into all of the local secondary indexes on that
--   table. Use this estimate to measure whether a local secondary index is
--   approaching its size limit. The estimate is subject to change over
--   time; therefore, do not rely on the precision or accuracy of the
--   estimate.</li>
--   <li><a>pirsConsumedCapacity</a> - Undocumented member.</li>
--   <li><a>pirsAttributes</a> - The attribute values as they appeared
--   before the <i>PutItem</i> operation, but only if <i>ReturnValues</i>
--   is specified as <tt>ALL_OLD</tt> in the request. Each element consists
--   of an attribute name and an attribute value.</li>
--   <li><a>pirsResponseStatus</a> - -- | The response status code.</li>
--   </ul>
putItemResponse :: Int -> PutItemResponse

-- | Represents the output of a <i>PutItem</i> operation.
--   
--   <i>See:</i> <a>putItemResponse</a> smart constructor.
data PutItemResponse

-- | Information about item collections, if any, that were affected by the
--   operation. <i>ItemCollectionMetrics</i> is only returned if the
--   request asked for it. If the table does not have any local secondary
--   indexes, this information is not returned in the response. Each
--   <i>ItemCollectionMetrics</i> element consists of: *
--   <i>ItemCollectionKey</i> - The partition key value of the item
--   collection. This is the same as the partition key value of the item
--   itself. * <i>SizeEstimateRange</i> - An estimate of item collection
--   size, in gigabytes. This value is a two-element array containing a
--   lower bound and an upper bound for the estimate. The estimate includes
--   the size of all the items in the table, plus the size of all
--   attributes projected into all of the local secondary indexes on that
--   table. Use this estimate to measure whether a local secondary index is
--   approaching its size limit. The estimate is subject to change over
--   time; therefore, do not rely on the precision or accuracy of the
--   estimate.
pirsItemCollectionMetrics :: Lens' PutItemResponse (Maybe ItemCollectionMetrics)

-- | Undocumented member.
pirsConsumedCapacity :: Lens' PutItemResponse (Maybe ConsumedCapacity)

-- | The attribute values as they appeared before the <i>PutItem</i>
--   operation, but only if <i>ReturnValues</i> is specified as
--   <tt>ALL_OLD</tt> in the request. Each element consists of an attribute
--   name and an attribute value.
pirsAttributes :: Lens' PutItemResponse (HashMap Text AttributeValue)

-- | <ul>
--   <li>- | The response status code.</li>
--   </ul>
pirsResponseStatus :: Lens' PutItemResponse Int
instance GHC.Generics.Generic Network.AWS.DynamoDB.PutItem.PutItemResponse
instance Data.Data.Data Network.AWS.DynamoDB.PutItem.PutItemResponse
instance GHC.Show.Show Network.AWS.DynamoDB.PutItem.PutItemResponse
instance GHC.Read.Read Network.AWS.DynamoDB.PutItem.PutItemResponse
instance GHC.Classes.Eq Network.AWS.DynamoDB.PutItem.PutItemResponse
instance GHC.Generics.Generic Network.AWS.DynamoDB.PutItem.PutItem
instance Data.Data.Data Network.AWS.DynamoDB.PutItem.PutItem
instance GHC.Show.Show Network.AWS.DynamoDB.PutItem.PutItem
instance GHC.Read.Read Network.AWS.DynamoDB.PutItem.PutItem
instance GHC.Classes.Eq Network.AWS.DynamoDB.PutItem.PutItem
instance Network.AWS.Types.AWSRequest Network.AWS.DynamoDB.PutItem.PutItem
instance Data.Hashable.Class.Hashable Network.AWS.DynamoDB.PutItem.PutItem
instance Control.DeepSeq.NFData Network.AWS.DynamoDB.PutItem.PutItem
instance Network.AWS.Data.Headers.ToHeaders Network.AWS.DynamoDB.PutItem.PutItem
instance Data.Aeson.Types.ToJSON.ToJSON Network.AWS.DynamoDB.PutItem.PutItem
instance Network.AWS.Data.Path.ToPath Network.AWS.DynamoDB.PutItem.PutItem
instance Network.AWS.Data.Query.ToQuery Network.AWS.DynamoDB.PutItem.PutItem
instance Control.DeepSeq.NFData Network.AWS.DynamoDB.PutItem.PutItemResponse


-- | Returns an array of table names associated with the current account
--   and endpoint. The output from <i>ListTables</i> is paginated, with
--   each page returning a maximum of 100 table names.
--   
--   This operation returns paginated results.
module Network.AWS.DynamoDB.ListTables

-- | Creates a value of <a>ListTables</a> with the minimum fields required
--   to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>ltExclusiveStartTableName</a> - The first table name that this
--   operation will evaluate. Use the value that was returned for
--   <i>LastEvaluatedTableName</i> in a previous operation, so that you can
--   obtain the next page of results.</li>
--   <li><a>ltLimit</a> - A maximum number of table names to return. If
--   this parameter is not specified, the limit is 100.</li>
--   </ul>
listTables :: ListTables

-- | Represents the input of a <i>ListTables</i> operation.
--   
--   <i>See:</i> <a>listTables</a> smart constructor.
data ListTables

-- | The first table name that this operation will evaluate. Use the value
--   that was returned for <i>LastEvaluatedTableName</i> in a previous
--   operation, so that you can obtain the next page of results.
ltExclusiveStartTableName :: Lens' ListTables (Maybe Text)

-- | A maximum number of table names to return. If this parameter is not
--   specified, the limit is 100.
ltLimit :: Lens' ListTables (Maybe Natural)

-- | Creates a value of <a>ListTablesResponse</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>ltrsLastEvaluatedTableName</a> - The name of the last table in
--   the current page of results. Use this value as the
--   <i>ExclusiveStartTableName</i> in a new request to obtain the next
--   page of results, until all the table names are returned. If you do not
--   receive a <i>LastEvaluatedTableName</i> value in the response, this
--   means that there are no more table names to be retrieved.</li>
--   <li><a>ltrsTableNames</a> - The names of the tables associated with
--   the current account at the current endpoint. The maximum size of this
--   array is 100. If <i>LastEvaluatedTableName</i> also appears in the
--   output, you can use this value as the <i>ExclusiveStartTableName</i>
--   parameter in a subsequent <i>ListTables</i> request and obtain the
--   next page of results.</li>
--   <li><a>ltrsResponseStatus</a> - -- | The response status code.</li>
--   </ul>
listTablesResponse :: Int -> ListTablesResponse

-- | Represents the output of a <i>ListTables</i> operation.
--   
--   <i>See:</i> <a>listTablesResponse</a> smart constructor.
data ListTablesResponse

-- | The name of the last table in the current page of results. Use this
--   value as the <i>ExclusiveStartTableName</i> in a new request to obtain
--   the next page of results, until all the table names are returned. If
--   you do not receive a <i>LastEvaluatedTableName</i> value in the
--   response, this means that there are no more table names to be
--   retrieved.
ltrsLastEvaluatedTableName :: Lens' ListTablesResponse (Maybe Text)

-- | The names of the tables associated with the current account at the
--   current endpoint. The maximum size of this array is 100. If
--   <i>LastEvaluatedTableName</i> also appears in the output, you can use
--   this value as the <i>ExclusiveStartTableName</i> parameter in a
--   subsequent <i>ListTables</i> request and obtain the next page of
--   results.
ltrsTableNames :: Lens' ListTablesResponse [Text]

-- | <ul>
--   <li>- | The response status code.</li>
--   </ul>
ltrsResponseStatus :: Lens' ListTablesResponse Int
instance GHC.Generics.Generic Network.AWS.DynamoDB.ListTables.ListTablesResponse
instance Data.Data.Data Network.AWS.DynamoDB.ListTables.ListTablesResponse
instance GHC.Show.Show Network.AWS.DynamoDB.ListTables.ListTablesResponse
instance GHC.Read.Read Network.AWS.DynamoDB.ListTables.ListTablesResponse
instance GHC.Classes.Eq Network.AWS.DynamoDB.ListTables.ListTablesResponse
instance GHC.Generics.Generic Network.AWS.DynamoDB.ListTables.ListTables
instance Data.Data.Data Network.AWS.DynamoDB.ListTables.ListTables
instance GHC.Show.Show Network.AWS.DynamoDB.ListTables.ListTables
instance GHC.Read.Read Network.AWS.DynamoDB.ListTables.ListTables
instance GHC.Classes.Eq Network.AWS.DynamoDB.ListTables.ListTables
instance Network.AWS.Pager.AWSPager Network.AWS.DynamoDB.ListTables.ListTables
instance Network.AWS.Types.AWSRequest Network.AWS.DynamoDB.ListTables.ListTables
instance Data.Hashable.Class.Hashable Network.AWS.DynamoDB.ListTables.ListTables
instance Control.DeepSeq.NFData Network.AWS.DynamoDB.ListTables.ListTables
instance Network.AWS.Data.Headers.ToHeaders Network.AWS.DynamoDB.ListTables.ListTables
instance Data.Aeson.Types.ToJSON.ToJSON Network.AWS.DynamoDB.ListTables.ListTables
instance Network.AWS.Data.Path.ToPath Network.AWS.DynamoDB.ListTables.ListTables
instance Network.AWS.Data.Query.ToQuery Network.AWS.DynamoDB.ListTables.ListTables
instance Control.DeepSeq.NFData Network.AWS.DynamoDB.ListTables.ListTablesResponse


-- | The <i>GetItem</i> operation returns a set of attributes for the item
--   with the given primary key. If there is no matching item,
--   <i>GetItem</i> does not return any data.
--   
--   <i>GetItem</i> provides an eventually consistent read by default. If
--   your application requires a strongly consistent read, set
--   <i>ConsistentRead</i> to <tt>true</tt> . Although a strongly
--   consistent read might take more time than an eventually consistent
--   read, it always returns the last updated value.
module Network.AWS.DynamoDB.GetItem

-- | Creates a value of <a>GetItem</a> with the minimum fields required to
--   make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>giProjectionExpression</a> - A string that identifies one or
--   more attributes to retrieve from the table. These attributes can
--   include scalars, sets, or elements of a JSON document. The attributes
--   in the expression must be separated by commas. If no attribute names
--   are specified, then all attributes will be returned. If any of the
--   requested attributes are not found, they will not appear in the
--   result. For more information, see <a>Accessing Item Attributes</a> in
--   the <i>Amazon DynamoDB Developer Guide</i> .</li>
--   <li><a>giAttributesToGet</a> - <i>Important:</i> This is a legacy
--   parameter, for backward compatibility. New applications should use
--   <i>ProjectionExpression</i> instead. Do not combine legacy parameters
--   and expression parameters in a single API call; otherwise, DynamoDB
--   will return a <i>ValidationException</i> exception. This parameter
--   allows you to retrieve attributes of type List or Map; however, it
--   cannot retrieve individual elements within a List or a Map. The names
--   of one or more attributes to retrieve. If no attribute names are
--   provided, then all attributes will be returned. If any of the
--   requested attributes are not found, they will not appear in the
--   result. Note that <i>AttributesToGet</i> has no effect on provisioned
--   throughput consumption. DynamoDB determines capacity units consumed
--   based on item size, not on the amount of data that is returned to an
--   application.</li>
--   <li><a>giExpressionAttributeNames</a> - One or more substitution
--   tokens for attribute names in an expression. The following are some
--   use cases for using <i>ExpressionAttributeNames</i> : * To access an
--   attribute whose name conflicts with a DynamoDB reserved word. * To
--   create a placeholder for repeating occurrences of an attribute name in
--   an expression. * To prevent special characters in an attribute name
--   from being misinterpreted in an expression. Use the <b>#</b> character
--   in an expression to dereference an attribute name. For example,
--   consider the following attribute name: * <tt>Percentile</tt> The name
--   of this attribute conflicts with a reserved word, so it cannot be used
--   directly in an expression. (For the complete list of reserved words,
--   see <a>Reserved Words</a> in the <i>Amazon DynamoDB Developer
--   Guide</i> ). To work around this, you could specify the following for
--   <i>ExpressionAttributeNames</i> : * <tt>{"#P":<a>Percentile</a>}</tt>
--   You could then use this substitution in an expression, as in this
--   example: * <tt>#P = :val</tt> For more information on expression
--   attribute names, see <a>Accessing Item Attributes</a> in the <i>Amazon
--   DynamoDB Developer Guide</i> .</li>
--   <li><a>giConsistentRead</a> - Determines the read consistency model:
--   If set to <tt>true</tt> , then the operation uses strongly consistent
--   reads; otherwise, the operation uses eventually consistent reads.</li>
--   <li><a>giReturnConsumedCapacity</a> - Undocumented member.</li>
--   <li><a>giTableName</a> - The name of the table containing the
--   requested item.</li>
--   <li><a>giKey</a> - A map of attribute names to <i>AttributeValue</i>
--   objects, representing the primary key of the item to retrieve. For the
--   primary key, you must provide all of the attributes. For example, with
--   a simple primary key, you only need to provide a value for the
--   partition key. For a composite primary key, you must provide values
--   for both the partition key and the sort key.</li>
--   </ul>
getItem :: Text -> GetItem

-- | Represents the input of a <i>GetItem</i> operation.
--   
--   <i>See:</i> <a>getItem</a> smart constructor.
data GetItem

-- | A string that identifies one or more attributes to retrieve from the
--   table. These attributes can include scalars, sets, or elements of a
--   JSON document. The attributes in the expression must be separated by
--   commas. If no attribute names are specified, then all attributes will
--   be returned. If any of the requested attributes are not found, they
--   will not appear in the result. For more information, see <a>Accessing
--   Item Attributes</a> in the <i>Amazon DynamoDB Developer Guide</i> .
giProjectionExpression :: Lens' GetItem (Maybe Text)

-- | <i>Important:</i> This is a legacy parameter, for backward
--   compatibility. New applications should use <i>ProjectionExpression</i>
--   instead. Do not combine legacy parameters and expression parameters in
--   a single API call; otherwise, DynamoDB will return a
--   <i>ValidationException</i> exception. This parameter allows you to
--   retrieve attributes of type List or Map; however, it cannot retrieve
--   individual elements within a List or a Map. The names of one or more
--   attributes to retrieve. If no attribute names are provided, then all
--   attributes will be returned. If any of the requested attributes are
--   not found, they will not appear in the result. Note that
--   <i>AttributesToGet</i> has no effect on provisioned throughput
--   consumption. DynamoDB determines capacity units consumed based on item
--   size, not on the amount of data that is returned to an application.
giAttributesToGet :: Lens' GetItem (Maybe (NonEmpty Text))

-- | One or more substitution tokens for attribute names in an expression.
--   The following are some use cases for using
--   <i>ExpressionAttributeNames</i> : * To access an attribute whose name
--   conflicts with a DynamoDB reserved word. * To create a placeholder for
--   repeating occurrences of an attribute name in an expression. * To
--   prevent special characters in an attribute name from being
--   misinterpreted in an expression. Use the <b>#</b> character in an
--   expression to dereference an attribute name. For example, consider the
--   following attribute name: * <tt>Percentile</tt> The name of this
--   attribute conflicts with a reserved word, so it cannot be used
--   directly in an expression. (For the complete list of reserved words,
--   see <a>Reserved Words</a> in the <i>Amazon DynamoDB Developer
--   Guide</i> ). To work around this, you could specify the following for
--   <i>ExpressionAttributeNames</i> : * <tt>{"#P":<a>Percentile</a>}</tt>
--   You could then use this substitution in an expression, as in this
--   example: * <tt>#P = :val</tt> For more information on expression
--   attribute names, see <a>Accessing Item Attributes</a> in the <i>Amazon
--   DynamoDB Developer Guide</i> .
giExpressionAttributeNames :: Lens' GetItem (HashMap Text Text)

-- | Determines the read consistency model: If set to <tt>true</tt> , then
--   the operation uses strongly consistent reads; otherwise, the operation
--   uses eventually consistent reads.
giConsistentRead :: Lens' GetItem (Maybe Bool)

-- | Undocumented member.
giReturnConsumedCapacity :: Lens' GetItem (Maybe ReturnConsumedCapacity)

-- | The name of the table containing the requested item.
giTableName :: Lens' GetItem Text

-- | A map of attribute names to <i>AttributeValue</i> objects,
--   representing the primary key of the item to retrieve. For the primary
--   key, you must provide all of the attributes. For example, with a
--   simple primary key, you only need to provide a value for the partition
--   key. For a composite primary key, you must provide values for both the
--   partition key and the sort key.
giKey :: Lens' GetItem (HashMap Text AttributeValue)

-- | Creates a value of <a>GetItemResponse</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>girsConsumedCapacity</a> - Undocumented member.</li>
--   <li><a>girsItem</a> - A map of attribute names to
--   <i>AttributeValue</i> objects, as specified by <i>AttributesToGet</i>
--   .</li>
--   <li><a>girsResponseStatus</a> - -- | The response status code.</li>
--   </ul>
getItemResponse :: Int -> GetItemResponse

-- | Represents the output of a <i>GetItem</i> operation.
--   
--   <i>See:</i> <a>getItemResponse</a> smart constructor.
data GetItemResponse

-- | Undocumented member.
girsConsumedCapacity :: Lens' GetItemResponse (Maybe ConsumedCapacity)

-- | A map of attribute names to <i>AttributeValue</i> objects, as
--   specified by <i>AttributesToGet</i> .
girsItem :: Lens' GetItemResponse (HashMap Text AttributeValue)

-- | <ul>
--   <li>- | The response status code.</li>
--   </ul>
girsResponseStatus :: Lens' GetItemResponse Int
instance GHC.Generics.Generic Network.AWS.DynamoDB.GetItem.GetItemResponse
instance Data.Data.Data Network.AWS.DynamoDB.GetItem.GetItemResponse
instance GHC.Show.Show Network.AWS.DynamoDB.GetItem.GetItemResponse
instance GHC.Read.Read Network.AWS.DynamoDB.GetItem.GetItemResponse
instance GHC.Classes.Eq Network.AWS.DynamoDB.GetItem.GetItemResponse
instance GHC.Generics.Generic Network.AWS.DynamoDB.GetItem.GetItem
instance Data.Data.Data Network.AWS.DynamoDB.GetItem.GetItem
instance GHC.Show.Show Network.AWS.DynamoDB.GetItem.GetItem
instance GHC.Read.Read Network.AWS.DynamoDB.GetItem.GetItem
instance GHC.Classes.Eq Network.AWS.DynamoDB.GetItem.GetItem
instance Network.AWS.Types.AWSRequest Network.AWS.DynamoDB.GetItem.GetItem
instance Data.Hashable.Class.Hashable Network.AWS.DynamoDB.GetItem.GetItem
instance Control.DeepSeq.NFData Network.AWS.DynamoDB.GetItem.GetItem
instance Network.AWS.Data.Headers.ToHeaders Network.AWS.DynamoDB.GetItem.GetItem
instance Data.Aeson.Types.ToJSON.ToJSON Network.AWS.DynamoDB.GetItem.GetItem
instance Network.AWS.Data.Path.ToPath Network.AWS.DynamoDB.GetItem.GetItem
instance Network.AWS.Data.Query.ToQuery Network.AWS.DynamoDB.GetItem.GetItem
instance Control.DeepSeq.NFData Network.AWS.DynamoDB.GetItem.GetItemResponse


-- | Returns information about the table, including the current status of
--   the table, when it was created, the primary key schema, and any
--   indexes on the table.
module Network.AWS.DynamoDB.DescribeTable

-- | Creates a value of <a>DescribeTable</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>dTableName</a> - The name of the table to describe.</li>
--   </ul>
describeTable :: Text -> DescribeTable

-- | Represents the input of a <i>DescribeTable</i> operation.
--   
--   <i>See:</i> <a>describeTable</a> smart constructor.
data DescribeTable

-- | The name of the table to describe.
dTableName :: Lens' DescribeTable Text

-- | Creates a value of <a>DescribeTableResponse</a> with the minimum
--   fields required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>drsTable</a> - Undocumented member.</li>
--   <li><a>drsResponseStatus</a> - -- | The response status code.</li>
--   </ul>
describeTableResponse :: Int -> DescribeTableResponse

-- | Represents the output of a <i>DescribeTable</i> operation.
--   
--   <i>See:</i> <a>describeTableResponse</a> smart constructor.
data DescribeTableResponse

-- | Undocumented member.
drsTable :: Lens' DescribeTableResponse (Maybe TableDescription)

-- | <ul>
--   <li>- | The response status code.</li>
--   </ul>
drsResponseStatus :: Lens' DescribeTableResponse Int
instance GHC.Generics.Generic Network.AWS.DynamoDB.DescribeTable.DescribeTableResponse
instance Data.Data.Data Network.AWS.DynamoDB.DescribeTable.DescribeTableResponse
instance GHC.Show.Show Network.AWS.DynamoDB.DescribeTable.DescribeTableResponse
instance GHC.Read.Read Network.AWS.DynamoDB.DescribeTable.DescribeTableResponse
instance GHC.Classes.Eq Network.AWS.DynamoDB.DescribeTable.DescribeTableResponse
instance GHC.Generics.Generic Network.AWS.DynamoDB.DescribeTable.DescribeTable
instance Data.Data.Data Network.AWS.DynamoDB.DescribeTable.DescribeTable
instance GHC.Show.Show Network.AWS.DynamoDB.DescribeTable.DescribeTable
instance GHC.Read.Read Network.AWS.DynamoDB.DescribeTable.DescribeTable
instance GHC.Classes.Eq Network.AWS.DynamoDB.DescribeTable.DescribeTable
instance Network.AWS.Types.AWSRequest Network.AWS.DynamoDB.DescribeTable.DescribeTable
instance Data.Hashable.Class.Hashable Network.AWS.DynamoDB.DescribeTable.DescribeTable
instance Control.DeepSeq.NFData Network.AWS.DynamoDB.DescribeTable.DescribeTable
instance Network.AWS.Data.Headers.ToHeaders Network.AWS.DynamoDB.DescribeTable.DescribeTable
instance Data.Aeson.Types.ToJSON.ToJSON Network.AWS.DynamoDB.DescribeTable.DescribeTable
instance Network.AWS.Data.Path.ToPath Network.AWS.DynamoDB.DescribeTable.DescribeTable
instance Network.AWS.Data.Query.ToQuery Network.AWS.DynamoDB.DescribeTable.DescribeTable
instance Control.DeepSeq.NFData Network.AWS.DynamoDB.DescribeTable.DescribeTableResponse


module Network.AWS.DynamoDB.Waiters

-- | Polls <a>DescribeTable</a> every 20 seconds until a successful state
--   is reached. An error is returned after 25 failed checks.
tableNotExists :: Wait DescribeTable

-- | Polls <a>DescribeTable</a> every 20 seconds until a successful state
--   is reached. An error is returned after 25 failed checks.
tableExists :: Wait DescribeTable


-- | Returns the current provisioned-capacity limits for your AWS account
--   in a region, both for the region as a whole and for any one DynamoDB
--   table that you create there.
--   
--   When you establish an AWS account, the account has initial limits on
--   the maximum read capacity units and write capacity units that you can
--   provision across all of your DynamoDB tables in a given region. Also,
--   there are per-table limits that apply when you create a table there.
--   For more information, see <a>Limits</a> page in the <i>Amazon DynamoDB
--   Developer Guide</i> .
--   
--   Although you can increase these limits by filing a case at <a>AWS
--   Support Center</a> , obtaining the increase is not instantaneous. The
--   <i>DescribeLimits</i> API lets you write code to compare the capacity
--   you are currently using to those limits imposed by your account so
--   that you have enough time to apply for an increase before you hit a
--   limit.
--   
--   For example, you could use one of the AWS SDKs to do the following:
--   
--   <ul>
--   <li>Call <i>DescribeLimits</i> for a particular region to obtain your
--   current account limits on provisioned capacity there.</li>
--   <li>Create a variable to hold the aggregate read capacity units
--   provisioned for all your tables in that region, and one to hold the
--   aggregate write capacity units. Zero them both.</li>
--   <li>Call <i>ListTables</i> to obtain a list of all your DynamoDB
--   tables.</li>
--   <li>For each table name listed by <i>ListTables</i> , do the
--   following:</li>
--   <li>Call <i>DescribeTable</i> with the table name.</li>
--   <li>Use the data returned by <i>DescribeTable</i> to add the read
--   capacity units and write capacity units provisioned for the table
--   itself to your variables.</li>
--   <li>If the table has one or more global secondary indexes (GSIs), loop
--   over these GSIs and add their provisioned capacity values to your
--   variables as well.</li>
--   <li>Report the account limits for that region returned by
--   <i>DescribeLimits</i> , along with the total current provisioned
--   capacity levels you have calculated.</li>
--   </ul>
--   
--   This will let you see whether you are getting close to your
--   account-level limits.
--   
--   The per-table limits apply only when you are creating a new table.
--   They restrict the sum of the provisioned capacity of the new table
--   itself and all its global secondary indexes.
--   
--   For existing tables and their GSIs, DynamoDB will not let you increase
--   provisioned capacity extremely rapidly, but the only upper limit that
--   applies is that the aggregate provisioned capacity over all your
--   tables and GSIs cannot exceed either of the per-account limits.
--   
--   The <i>DescribeLimits</i> Request element has no content.
module Network.AWS.DynamoDB.DescribeLimits

-- | Creates a value of <a>DescribeLimits</a> with the minimum fields
--   required to make a request.
describeLimits :: DescribeLimits

-- | Represents the input of a <i>DescribeLimits</i> operation. Has no
--   content.
--   
--   <i>See:</i> <a>describeLimits</a> smart constructor.
data DescribeLimits

-- | Creates a value of <a>DescribeLimitsResponse</a> with the minimum
--   fields required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>dlrsTableMaxWriteCapacityUnits</a> - The maximum write capacity
--   units that your account allows you to provision for a new table that
--   you are creating in this region, including the write capacity units
--   provisioned for its global secondary indexes (GSIs).</li>
--   <li><a>dlrsTableMaxReadCapacityUnits</a> - The maximum read capacity
--   units that your account allows you to provision for a new table that
--   you are creating in this region, including the read capacity units
--   provisioned for its global secondary indexes (GSIs).</li>
--   <li><a>dlrsAccountMaxWriteCapacityUnits</a> - The maximum total write
--   capacity units that your account allows you to provision across all of
--   your tables in this region.</li>
--   <li><a>dlrsAccountMaxReadCapacityUnits</a> - The maximum total read
--   capacity units that your account allows you to provision across all of
--   your tables in this region.</li>
--   <li><a>dlrsResponseStatus</a> - -- | The response status code.</li>
--   </ul>
describeLimitsResponse :: Int -> DescribeLimitsResponse

-- | Represents the output of a <i>DescribeLimits</i> operation.
--   
--   <i>See:</i> <a>describeLimitsResponse</a> smart constructor.
data DescribeLimitsResponse

-- | The maximum write capacity units that your account allows you to
--   provision for a new table that you are creating in this region,
--   including the write capacity units provisioned for its global
--   secondary indexes (GSIs).
dlrsTableMaxWriteCapacityUnits :: Lens' DescribeLimitsResponse (Maybe Natural)

-- | The maximum read capacity units that your account allows you to
--   provision for a new table that you are creating in this region,
--   including the read capacity units provisioned for its global secondary
--   indexes (GSIs).
dlrsTableMaxReadCapacityUnits :: Lens' DescribeLimitsResponse (Maybe Natural)

-- | The maximum total write capacity units that your account allows you to
--   provision across all of your tables in this region.
dlrsAccountMaxWriteCapacityUnits :: Lens' DescribeLimitsResponse (Maybe Natural)

-- | The maximum total read capacity units that your account allows you to
--   provision across all of your tables in this region.
dlrsAccountMaxReadCapacityUnits :: Lens' DescribeLimitsResponse (Maybe Natural)

-- | <ul>
--   <li>- | The response status code.</li>
--   </ul>
dlrsResponseStatus :: Lens' DescribeLimitsResponse Int
instance GHC.Generics.Generic Network.AWS.DynamoDB.DescribeLimits.DescribeLimitsResponse
instance Data.Data.Data Network.AWS.DynamoDB.DescribeLimits.DescribeLimitsResponse
instance GHC.Show.Show Network.AWS.DynamoDB.DescribeLimits.DescribeLimitsResponse
instance GHC.Read.Read Network.AWS.DynamoDB.DescribeLimits.DescribeLimitsResponse
instance GHC.Classes.Eq Network.AWS.DynamoDB.DescribeLimits.DescribeLimitsResponse
instance GHC.Generics.Generic Network.AWS.DynamoDB.DescribeLimits.DescribeLimits
instance Data.Data.Data Network.AWS.DynamoDB.DescribeLimits.DescribeLimits
instance GHC.Show.Show Network.AWS.DynamoDB.DescribeLimits.DescribeLimits
instance GHC.Read.Read Network.AWS.DynamoDB.DescribeLimits.DescribeLimits
instance GHC.Classes.Eq Network.AWS.DynamoDB.DescribeLimits.DescribeLimits
instance Network.AWS.Types.AWSRequest Network.AWS.DynamoDB.DescribeLimits.DescribeLimits
instance Data.Hashable.Class.Hashable Network.AWS.DynamoDB.DescribeLimits.DescribeLimits
instance Control.DeepSeq.NFData Network.AWS.DynamoDB.DescribeLimits.DescribeLimits
instance Network.AWS.Data.Headers.ToHeaders Network.AWS.DynamoDB.DescribeLimits.DescribeLimits
instance Data.Aeson.Types.ToJSON.ToJSON Network.AWS.DynamoDB.DescribeLimits.DescribeLimits
instance Network.AWS.Data.Path.ToPath Network.AWS.DynamoDB.DescribeLimits.DescribeLimits
instance Network.AWS.Data.Query.ToQuery Network.AWS.DynamoDB.DescribeLimits.DescribeLimits
instance Control.DeepSeq.NFData Network.AWS.DynamoDB.DescribeLimits.DescribeLimitsResponse


-- | The <i>DeleteTable</i> operation deletes a table and all of its items.
--   After a <i>DeleteTable</i> request, the specified table is in the
--   <tt>DELETING</tt> state until DynamoDB completes the deletion. If the
--   table is in the <tt>ACTIVE</tt> state, you can delete it. If a table
--   is in <tt>CREATING</tt> or <tt>UPDATING</tt> states, then DynamoDB
--   returns a <i>ResourceInUseException</i> . If the specified table does
--   not exist, DynamoDB returns a <i>ResourceNotFoundException</i> . If
--   table is already in the <tt>DELETING</tt> state, no error is returned.
--   
--   When you delete a table, any indexes on that table are also deleted.
--   
--   If you have DynamoDB Streams enabled on the table, then the
--   corresponding stream on that table goes into the <tt>DISABLED</tt>
--   state, and the stream is automatically deleted after 24 hours.
--   
--   Use the <i>DescribeTable</i> API to check the status of the table.
module Network.AWS.DynamoDB.DeleteTable

-- | Creates a value of <a>DeleteTable</a> with the minimum fields required
--   to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>dtTableName</a> - The name of the table to delete.</li>
--   </ul>
deleteTable :: Text -> DeleteTable

-- | Represents the input of a <i>DeleteTable</i> operation.
--   
--   <i>See:</i> <a>deleteTable</a> smart constructor.
data DeleteTable

-- | The name of the table to delete.
dtTableName :: Lens' DeleteTable Text

-- | Creates a value of <a>DeleteTableResponse</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>dtrsTableDescription</a> - Undocumented member.</li>
--   <li><a>dtrsResponseStatus</a> - -- | The response status code.</li>
--   </ul>
deleteTableResponse :: Int -> DeleteTableResponse

-- | Represents the output of a <i>DeleteTable</i> operation.
--   
--   <i>See:</i> <a>deleteTableResponse</a> smart constructor.
data DeleteTableResponse

-- | Undocumented member.
dtrsTableDescription :: Lens' DeleteTableResponse (Maybe TableDescription)

-- | <ul>
--   <li>- | The response status code.</li>
--   </ul>
dtrsResponseStatus :: Lens' DeleteTableResponse Int
instance GHC.Generics.Generic Network.AWS.DynamoDB.DeleteTable.DeleteTableResponse
instance Data.Data.Data Network.AWS.DynamoDB.DeleteTable.DeleteTableResponse
instance GHC.Show.Show Network.AWS.DynamoDB.DeleteTable.DeleteTableResponse
instance GHC.Read.Read Network.AWS.DynamoDB.DeleteTable.DeleteTableResponse
instance GHC.Classes.Eq Network.AWS.DynamoDB.DeleteTable.DeleteTableResponse
instance GHC.Generics.Generic Network.AWS.DynamoDB.DeleteTable.DeleteTable
instance Data.Data.Data Network.AWS.DynamoDB.DeleteTable.DeleteTable
instance GHC.Show.Show Network.AWS.DynamoDB.DeleteTable.DeleteTable
instance GHC.Read.Read Network.AWS.DynamoDB.DeleteTable.DeleteTable
instance GHC.Classes.Eq Network.AWS.DynamoDB.DeleteTable.DeleteTable
instance Network.AWS.Types.AWSRequest Network.AWS.DynamoDB.DeleteTable.DeleteTable
instance Data.Hashable.Class.Hashable Network.AWS.DynamoDB.DeleteTable.DeleteTable
instance Control.DeepSeq.NFData Network.AWS.DynamoDB.DeleteTable.DeleteTable
instance Network.AWS.Data.Headers.ToHeaders Network.AWS.DynamoDB.DeleteTable.DeleteTable
instance Data.Aeson.Types.ToJSON.ToJSON Network.AWS.DynamoDB.DeleteTable.DeleteTable
instance Network.AWS.Data.Path.ToPath Network.AWS.DynamoDB.DeleteTable.DeleteTable
instance Network.AWS.Data.Query.ToQuery Network.AWS.DynamoDB.DeleteTable.DeleteTable
instance Control.DeepSeq.NFData Network.AWS.DynamoDB.DeleteTable.DeleteTableResponse


-- | Deletes a single item in a table by primary key. You can perform a
--   conditional delete operation that deletes the item if it exists, or if
--   it has an expected attribute value.
--   
--   In addition to deleting an item, you can also return the item's
--   attribute values in the same operation, using the <i>ReturnValues</i>
--   parameter.
--   
--   Unless you specify conditions, the <i>DeleteItem</i> is an idempotent
--   operation; running it multiple times on the same item or attribute
--   does <i>not</i> result in an error response.
--   
--   Conditional deletes are useful for deleting items only if specific
--   conditions are met. If those conditions are met, DynamoDB performs the
--   delete. Otherwise, the item is not deleted.
module Network.AWS.DynamoDB.DeleteItem

-- | Creates a value of <a>DeleteItem</a> with the minimum fields required
--   to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>diExpressionAttributeNames</a> - One or more substitution
--   tokens for attribute names in an expression. The following are some
--   use cases for using <i>ExpressionAttributeNames</i> : * To access an
--   attribute whose name conflicts with a DynamoDB reserved word. * To
--   create a placeholder for repeating occurrences of an attribute name in
--   an expression. * To prevent special characters in an attribute name
--   from being misinterpreted in an expression. Use the <b>#</b> character
--   in an expression to dereference an attribute name. For example,
--   consider the following attribute name: * <tt>Percentile</tt> The name
--   of this attribute conflicts with a reserved word, so it cannot be used
--   directly in an expression. (For the complete list of reserved words,
--   see <a>Reserved Words</a> in the <i>Amazon DynamoDB Developer
--   Guide</i> ). To work around this, you could specify the following for
--   <i>ExpressionAttributeNames</i> : * <tt>{"#P":<a>Percentile</a>}</tt>
--   You could then use this substitution in an expression, as in this
--   example: * <tt>#P = :val</tt> For more information on expression
--   attribute names, see <a>Accessing Item Attributes</a> in the <i>Amazon
--   DynamoDB Developer Guide</i> .</li>
--   <li><a>diReturnValues</a> - Use <i>ReturnValues</i> if you want to get
--   the item attributes as they appeared before they were deleted. For
--   <i>DeleteItem</i> , the valid values are: * <tt>NONE</tt> - If
--   <i>ReturnValues</i> is not specified, or if its value is <tt>NONE</tt>
--   , then nothing is returned. (This setting is the default for
--   <i>ReturnValues</i> .) * <tt>ALL_OLD</tt> - The content of the old
--   item is returned.</li>
--   <li><a>diExpressionAttributeValues</a> - One or more values that can
--   be substituted in an expression. Use the <b>:</b> (colon) character in
--   an expression to dereference an attribute value. For example, suppose
--   that you wanted to check whether the value of the <i>ProductStatus</i>
--   attribute was one of the following: <tt>Available | Backordered |
--   Discontinued</tt> You would first need to specify
--   <i>ExpressionAttributeValues</i> as follows: <tt>{
--   ":avail":{<a>S</a>:<a>Available</a>},
--   ":back":{<a>S</a>:<a>Backordered</a>},
--   ":disc":{<a>S</a>:<a>Discontinued</a>} }</tt> You could then use these
--   values in an expression, such as this: <tt>ProductStatus IN (:avail,
--   :back, :disc)</tt> For more information on expression attribute
--   values, see <a>Specifying Conditions</a> in the <i>Amazon DynamoDB
--   Developer Guide</i> .</li>
--   <li><a>diReturnConsumedCapacity</a> - Undocumented member.</li>
--   <li><a>diReturnItemCollectionMetrics</a> - Determines whether item
--   collection metrics are returned. If set to <tt>SIZE</tt> , the
--   response includes statistics about item collections, if any, that were
--   modified during the operation are returned in the response. If set to
--   <tt>NONE</tt> (the default), no statistics are returned.</li>
--   <li><a>diConditionExpression</a> - A condition that must be satisfied
--   in order for a conditional <i>DeleteItem</i> to succeed. An expression
--   can contain any of the following: * Functions: <tt>attribute_exists |
--   attribute_not_exists | attribute_type | contains | begins_with |
--   size</tt> These function names are case-sensitive. * Comparison
--   operators: <tt>= | &lt;&gt; | &lt; | &gt; | &lt;= | &gt;= | BETWEEN |
--   IN</tt> * Logical operators: <tt>AND | OR | NOT</tt> For more
--   information on condition expressions, see <a>Specifying Conditions</a>
--   in the <i>Amazon DynamoDB Developer Guide</i> .</li>
--   <li><a>diConditionalOperator</a> - <i>Important:</i> This is a legacy
--   parameter, for backward compatibility. New applications should use
--   <i>ConditionExpression</i> instead. Do not combine legacy parameters
--   and expression parameters in a single API call; otherwise, DynamoDB
--   will return a <i>ValidationException</i> exception. A logical operator
--   to apply to the conditions in the <i>Expected</i> map: * <tt>AND</tt>
--   - If all of the conditions evaluate to true, then the entire map
--   evaluates to true. * <tt>OR</tt> - If at least one of the conditions
--   evaluate to true, then the entire map evaluates to true. If you omit
--   <i>ConditionalOperator</i> , then <tt>AND</tt> is the default. The
--   operation will succeed only if the entire map evaluates to true.</li>
--   <li><a>diExpected</a> - <i>Important:</i> This is a legacy parameter,
--   for backward compatibility. New applications should use
--   <i>ConditionExpression</i> instead. Do not combine legacy parameters
--   and expression parameters in a single API call; otherwise, DynamoDB
--   will return a <i>ValidationException</i> exception. A map of
--   attribute<i>condition pairs. </i>Expected<i> provides a conditional
--   block for the </i>DeleteItem<i> operation. Each element of
--   </i>Expected<i> consists of an attribute name, a comparison operator,
--   and one or more values. DynamoDB compares the attribute with the
--   value(s) you supplied, using the comparison operator. For each
--   </i>Expected<i> element, the result of the evaluation is either true
--   or false. If you specify more than one element in the </i>Expected<i>
--   map, then by default all of the conditions must evaluate to true. In
--   other words, the conditions are ANDed together. (You can use the
--   </i>ConditionalOperator<i> 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.) If the </i>Expected<i> map evaluates
--   to true, then the conditional operation succeeds; otherwise, it fails.
--   </i>Expected<i> contains the following: * </i>AttributeValueList<i> -
--   One or more values to evaluate against the supplied attribute. The
--   number of values in the list depends on the </i>ComparisonOperator<i>
--   being used. For type Number, value comparisons are numeric. String
--   value comparisons for greater than, equals, or less than are based on
--   ASCII character code values. For example, <tt>a</tt> is greater than
--   <tt>A</tt> , and <tt>a</tt> is greater than <tt>B</tt> . For a list of
--   code values, see
--   &lt;http:</i><i>en.wikipedia.org</i>wiki<i>ASCII#ASCII_printable_characters
--   http:</i><i>en.wikipedia.org</i>wiki<i>ASCII#ASCII_printable_characters&gt;
--   . For type Binary, DynamoDB treats each byte of the binary data as
--   unsigned when it compares binary values. * </i>ComparisonOperator<i> -
--   A comparator for evaluating attributes in the
--   </i>AttributeValueList<i> . When performing the comparison, DynamoDB
--   uses strongly consistent reads. The following comparison operators are
--   available: <tt>EQ | NE | LE | LT | GE | GT | NOT_NULL | NULL |
--   CONTAINS | NOT_CONTAINS | BEGINS_WITH | IN | BETWEEN</tt> The
--   following are descriptions of each comparison operator. * <tt>EQ</tt>
--   : Equal. <tt>EQ</tt> is supported for all datatypes, including lists
--   and maps. </i>AttributeValueList<i> can contain only one
--   </i>AttributeValue<i> element of type String, Number, Binary, String
--   Set, Number Set, or Binary Set. If an item contains an
--   </i>AttributeValue<i> element of a different type than the one
--   provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>NE</tt> : Not equal. <tt>NE</tt> is supported for
--   all datatypes, including lists and maps. </i>AttributeValueList<i> can
--   contain only one </i>AttributeValue<i> of type String, Number, Binary,
--   String Set, Number Set, or Binary Set. If an item contains an
--   </i>AttributeValue<i> of a different type than the one provided in the
--   request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LE</tt> : Less than or equal.
--   </i>AttributeValueList<i> can contain only one </i>AttributeValue<i>
--   element of type String, Number, or Binary (not a set type). If an item
--   contains an </i>AttributeValue<i> element of a different type than the
--   one provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LT</tt> : Less than. </i>AttributeValueList<i> can
--   contain only one </i>AttributeValue<i> of type String, Number, or
--   Binary (not a set type). If an item contains an </i>AttributeValue<i>
--   element of a different type than the one provided in the request, the
--   value does not match. For example, <tt>{<a>S</a>:"6"}</tt> does not
--   equal <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GE</tt> :
--   Greater than or equal. </i>AttributeValueList<i> can contain only one
--   </i>AttributeValue<i> element of type String, Number, or Binary (not a
--   set type). If an item contains an </i>AttributeValue<i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GT</tt> :
--   Greater than. </i>AttributeValueList<i> can contain only one
--   </i>AttributeValue<i> element of type String, Number, or Binary (not a
--   set type). If an item contains an </i>AttributeValue<i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>NOT_NULL</tt>
--   : The attribute exists. <tt>NOT_NULL</tt> is supported for all
--   datatypes, including lists and maps. * <tt>NULL</tt> : The attribute
--   does not exist. <tt>NULL</tt> is supported for all datatypes,
--   including lists and maps. * <tt>CONTAINS</tt> : Checks for a
--   subsequence, or value in a set. </i>AttributeValueList<i> can contain
--   only one </i>AttributeValue<i> element of type String, Number, or
--   Binary (not a set type). If the target attribute of the comparison is
--   of type String, then the operator checks for a substring match. If the
--   target attribute of the comparison is of type Binary, then the
--   operator looks for a subsequence of the target that matches the input.
--   If the target attribute of the comparison is a set ("<tt>SS</tt> ",
--   "<tt>NS</tt> ", or "<tt>BS</tt> "), then the operator evaluates to
--   true if it finds an exact match with any member of the set. CONTAINS
--   is supported for lists: When evaluating "<tt>a CONTAINS b</tt> ",
--   "<tt>a</tt> " can be a list; however, "<tt>b</tt> " cannot be a set, a
--   map, or a list. * <tt>NOT_CONTAINS</tt> : Checks for absence of a
--   subsequence, or absence of a value in a set. </i>AttributeValueList<i>
--   can contain only one </i>AttributeValue<i> element of type String,
--   Number, or Binary (not a set type). If the target attribute of the
--   comparison is a String, then the operator checks for the absence of a
--   substring match. If the target attribute of the comparison is Binary,
--   then the operator checks for the absence of a subsequence of the
--   target that matches the input. If the target attribute of the
--   comparison is a set ("<tt>SS</tt> ", "<tt>NS</tt> ", or "<tt>BS</tt>
--   "), then the operator evaluates to true if it </i>does not<i> find an
--   exact match with any member of the set. NOT_CONTAINS is supported for
--   lists: When evaluating "<tt>a NOT CONTAINS b</tt> ", "<tt>a</tt> " can
--   be a list; however, "<tt>b</tt> " cannot be a set, a map, or a list. *
--   <tt>BEGINS_WITH</tt> : Checks for a prefix. </i>AttributeValueList<i>
--   can contain only one </i>AttributeValue<i> of type String or Binary
--   (not a Number or a set type). The target attribute of the comparison
--   must be of type String or Binary (not a Number or a set type). *
--   <tt>IN</tt> : Checks for matching elements within two sets.
--   </i>AttributeValueList<i> can contain one or more
--   </i>AttributeValue<i> elements of type String, Number, or Binary (not
--   a set type). These attributes are compared against an existing set
--   type attribute of an item. If any elements of the input set are
--   present in the item attribute, the expression evaluates to true. *
--   <tt>BETWEEN</tt> : Greater than or equal to the first value, and less
--   than or equal to the second value. </i>AttributeValueList<i> must
--   contain two </i>AttributeValue<i> elements of the same type, either
--   String, Number, or Binary (not a set type). A target attribute matches
--   if the target value is greater than, or equal to, the first element
--   and less than, or equal to, the second element. If an item contains an
--   </i>AttributeValue<i> element of a different type than the one
--   provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not compare to <tt>{<a>N</a>:"6"}</tt> .
--   Also, <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6",
--   "2", "1"]}</tt> For usage examples of </i>AttributeValueList<i> and
--   </i>ComparisonOperator<i> , see
--   &lt;http:</i><i>docs.aws.amazon.com</i>amazondynamodb<i>latest</i>developerguide<i>LegacyConditionalParameters.html
--   Legacy Conditional Parameters&gt; in the </i>Amazon DynamoDB Developer
--   Guide<i> . For backward compatibility with previous DynamoDB releases,
--   the following parameters can be used instead of
--   </i>AttributeValueList<i> and </i>ComparisonOperator<i> : *
--   </i>Value<i> - A value for DynamoDB to compare with an attribute. *
--   </i>Exists<i> - A Boolean value that causes DynamoDB to evaluate the
--   value before attempting the conditional operation: * If </i>Exists<i>
--   is <tt>true</tt> , DynamoDB will check to see if that attribute value
--   already exists in the table. If it is found, then the condition
--   evaluates to true; otherwise the condition evaluate to false. * If
--   </i>Exists<i> is <tt>false</tt> , DynamoDB assumes that the attribute
--   value does </i>not<i> exist in the table. If in fact the value does
--   not exist, then the assumption is valid and the condition evaluates to
--   true. If the value is found, despite the assumption that it does not
--   exist, the condition evaluates to false. Note that the default value
--   for </i>Exists<i> is <tt>true</tt> . The </i>Value<i> and
--   </i>Exists<i> parameters are incompatible with
--   </i>AttributeValueList<i> and </i>ComparisonOperator<i> . Note that if
--   you use both sets of parameters at once, DynamoDB will return a
--   </i>ValidationException/ exception.</li>
--   <li><a>diTableName</a> - The name of the table from which to delete
--   the item.</li>
--   <li><a>diKey</a> - A map of attribute names to <i>AttributeValue</i>
--   objects, representing the primary key of the item to delete. For the
--   primary key, you must provide all of the attributes. For example, with
--   a simple primary key, you only need to provide a value for the
--   partition key. For a composite primary key, you must provide values
--   for both the partition key and the sort key.</li>
--   </ul>
deleteItem :: Text -> DeleteItem

-- | Represents the input of a <i>DeleteItem</i> operation.
--   
--   <i>See:</i> <a>deleteItem</a> smart constructor.
data DeleteItem

-- | One or more substitution tokens for attribute names in an expression.
--   The following are some use cases for using
--   <i>ExpressionAttributeNames</i> : * To access an attribute whose name
--   conflicts with a DynamoDB reserved word. * To create a placeholder for
--   repeating occurrences of an attribute name in an expression. * To
--   prevent special characters in an attribute name from being
--   misinterpreted in an expression. Use the <b>#</b> character in an
--   expression to dereference an attribute name. For example, consider the
--   following attribute name: * <tt>Percentile</tt> The name of this
--   attribute conflicts with a reserved word, so it cannot be used
--   directly in an expression. (For the complete list of reserved words,
--   see <a>Reserved Words</a> in the <i>Amazon DynamoDB Developer
--   Guide</i> ). To work around this, you could specify the following for
--   <i>ExpressionAttributeNames</i> : * <tt>{"#P":<a>Percentile</a>}</tt>
--   You could then use this substitution in an expression, as in this
--   example: * <tt>#P = :val</tt> For more information on expression
--   attribute names, see <a>Accessing Item Attributes</a> in the <i>Amazon
--   DynamoDB Developer Guide</i> .
diExpressionAttributeNames :: Lens' DeleteItem (HashMap Text Text)

-- | Use <i>ReturnValues</i> if you want to get the item attributes as they
--   appeared before they were deleted. For <i>DeleteItem</i> , the valid
--   values are: * <tt>NONE</tt> - If <i>ReturnValues</i> is not specified,
--   or if its value is <tt>NONE</tt> , then nothing is returned. (This
--   setting is the default for <i>ReturnValues</i> .) * <tt>ALL_OLD</tt> -
--   The content of the old item is returned.
diReturnValues :: Lens' DeleteItem (Maybe ReturnValue)

-- | One or more values that can be substituted in an expression. Use the
--   <b>:</b> (colon) character in an expression to dereference an
--   attribute value. For example, suppose that you wanted to check whether
--   the value of the <i>ProductStatus</i> attribute was one of the
--   following: <tt>Available | Backordered | Discontinued</tt> You would
--   first need to specify <i>ExpressionAttributeValues</i> as follows:
--   <tt>{ ":avail":{<a>S</a>:<a>Available</a>},
--   ":back":{<a>S</a>:<a>Backordered</a>},
--   ":disc":{<a>S</a>:<a>Discontinued</a>} }</tt> You could then use these
--   values in an expression, such as this: <tt>ProductStatus IN (:avail,
--   :back, :disc)</tt> For more information on expression attribute
--   values, see <a>Specifying Conditions</a> in the <i>Amazon DynamoDB
--   Developer Guide</i> .
diExpressionAttributeValues :: Lens' DeleteItem (HashMap Text AttributeValue)

-- | Undocumented member.
diReturnConsumedCapacity :: Lens' DeleteItem (Maybe ReturnConsumedCapacity)

-- | Determines whether item collection metrics are returned. If set to
--   <tt>SIZE</tt> , the response includes statistics about item
--   collections, if any, that were modified during the operation are
--   returned in the response. If set to <tt>NONE</tt> (the default), no
--   statistics are returned.
diReturnItemCollectionMetrics :: Lens' DeleteItem (Maybe ReturnItemCollectionMetrics)

-- | A condition that must be satisfied in order for a conditional
--   <i>DeleteItem</i> to succeed. An expression can contain any of the
--   following: * Functions: <tt>attribute_exists | attribute_not_exists |
--   attribute_type | contains | begins_with | size</tt> These function
--   names are case-sensitive. * Comparison operators: <tt>= | &lt;&gt; |
--   &lt; | &gt; | &lt;= | &gt;= | BETWEEN | IN</tt> * Logical operators:
--   <tt>AND | OR | NOT</tt> For more information on condition expressions,
--   see <a>Specifying Conditions</a> in the <i>Amazon DynamoDB Developer
--   Guide</i> .
diConditionExpression :: Lens' DeleteItem (Maybe Text)

-- | <i>Important:</i> This is a legacy parameter, for backward
--   compatibility. New applications should use <i>ConditionExpression</i>
--   instead. Do not combine legacy parameters and expression parameters in
--   a single API call; otherwise, DynamoDB will return a
--   <i>ValidationException</i> exception. A logical operator to apply to
--   the conditions in the <i>Expected</i> map: * <tt>AND</tt> - If all of
--   the conditions evaluate to true, then the entire map evaluates to
--   true. * <tt>OR</tt> - If at least one of the conditions evaluate to
--   true, then the entire map evaluates to true. If you omit
--   <i>ConditionalOperator</i> , then <tt>AND</tt> is the default. The
--   operation will succeed only if the entire map evaluates to true.
diConditionalOperator :: Lens' DeleteItem (Maybe ConditionalOperator)

-- | <i>Important:</i> This is a legacy parameter, for backward
--   compatibility. New applications should use <i>ConditionExpression</i>
--   instead. Do not combine legacy parameters and expression parameters in
--   a single API call; otherwise, DynamoDB will return a
--   <i>ValidationException</i> exception. A map of attribute<i>condition
--   pairs. </i>Expected<i> provides a conditional block for the
--   </i>DeleteItem<i> operation. Each element of </i>Expected<i> consists
--   of an attribute name, a comparison operator, and one or more values.
--   DynamoDB compares the attribute with the value(s) you supplied, using
--   the comparison operator. For each </i>Expected<i> element, the result
--   of the evaluation is either true or false. If you specify more than
--   one element in the </i>Expected<i> map, then by default all of the
--   conditions must evaluate to true. In other words, the conditions are
--   ANDed together. (You can use the </i>ConditionalOperator<i> 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.) If the
--   </i>Expected<i> map evaluates to true, then the conditional operation
--   succeeds; otherwise, it fails. </i>Expected<i> contains the following:
--   * </i>AttributeValueList<i> - One or more values to evaluate against
--   the supplied attribute. The number of values in the list depends on
--   the </i>ComparisonOperator<i> being used. For type Number, value
--   comparisons are numeric. String value comparisons for greater than,
--   equals, or less than are based on ASCII character code values. For
--   example, <tt>a</tt> is greater than <tt>A</tt> , and <tt>a</tt> is
--   greater than <tt>B</tt> . For a list of code values, see
--   &lt;http:</i><i>en.wikipedia.org</i>wiki<i>ASCII#ASCII_printable_characters
--   http:</i><i>en.wikipedia.org</i>wiki<i>ASCII#ASCII_printable_characters&gt;
--   . For type Binary, DynamoDB treats each byte of the binary data as
--   unsigned when it compares binary values. * </i>ComparisonOperator<i> -
--   A comparator for evaluating attributes in the
--   </i>AttributeValueList<i> . When performing the comparison, DynamoDB
--   uses strongly consistent reads. The following comparison operators are
--   available: <tt>EQ | NE | LE | LT | GE | GT | NOT_NULL | NULL |
--   CONTAINS | NOT_CONTAINS | BEGINS_WITH | IN | BETWEEN</tt> The
--   following are descriptions of each comparison operator. * <tt>EQ</tt>
--   : Equal. <tt>EQ</tt> is supported for all datatypes, including lists
--   and maps. </i>AttributeValueList<i> can contain only one
--   </i>AttributeValue<i> element of type String, Number, Binary, String
--   Set, Number Set, or Binary Set. If an item contains an
--   </i>AttributeValue<i> element of a different type than the one
--   provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>NE</tt> : Not equal. <tt>NE</tt> is supported for
--   all datatypes, including lists and maps. </i>AttributeValueList<i> can
--   contain only one </i>AttributeValue<i> of type String, Number, Binary,
--   String Set, Number Set, or Binary Set. If an item contains an
--   </i>AttributeValue<i> of a different type than the one provided in the
--   request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LE</tt> : Less than or equal.
--   </i>AttributeValueList<i> can contain only one </i>AttributeValue<i>
--   element of type String, Number, or Binary (not a set type). If an item
--   contains an </i>AttributeValue<i> element of a different type than the
--   one provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LT</tt> : Less than. </i>AttributeValueList<i> can
--   contain only one </i>AttributeValue<i> of type String, Number, or
--   Binary (not a set type). If an item contains an </i>AttributeValue<i>
--   element of a different type than the one provided in the request, the
--   value does not match. For example, <tt>{<a>S</a>:"6"}</tt> does not
--   equal <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GE</tt> :
--   Greater than or equal. </i>AttributeValueList<i> can contain only one
--   </i>AttributeValue<i> element of type String, Number, or Binary (not a
--   set type). If an item contains an </i>AttributeValue<i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GT</tt> :
--   Greater than. </i>AttributeValueList<i> can contain only one
--   </i>AttributeValue<i> element of type String, Number, or Binary (not a
--   set type). If an item contains an </i>AttributeValue<i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>NOT_NULL</tt>
--   : The attribute exists. <tt>NOT_NULL</tt> is supported for all
--   datatypes, including lists and maps. * <tt>NULL</tt> : The attribute
--   does not exist. <tt>NULL</tt> is supported for all datatypes,
--   including lists and maps. * <tt>CONTAINS</tt> : Checks for a
--   subsequence, or value in a set. </i>AttributeValueList<i> can contain
--   only one </i>AttributeValue<i> element of type String, Number, or
--   Binary (not a set type). If the target attribute of the comparison is
--   of type String, then the operator checks for a substring match. If the
--   target attribute of the comparison is of type Binary, then the
--   operator looks for a subsequence of the target that matches the input.
--   If the target attribute of the comparison is a set ("<tt>SS</tt> ",
--   "<tt>NS</tt> ", or "<tt>BS</tt> "), then the operator evaluates to
--   true if it finds an exact match with any member of the set. CONTAINS
--   is supported for lists: When evaluating "<tt>a CONTAINS b</tt> ",
--   "<tt>a</tt> " can be a list; however, "<tt>b</tt> " cannot be a set, a
--   map, or a list. * <tt>NOT_CONTAINS</tt> : Checks for absence of a
--   subsequence, or absence of a value in a set. </i>AttributeValueList<i>
--   can contain only one </i>AttributeValue<i> element of type String,
--   Number, or Binary (not a set type). If the target attribute of the
--   comparison is a String, then the operator checks for the absence of a
--   substring match. If the target attribute of the comparison is Binary,
--   then the operator checks for the absence of a subsequence of the
--   target that matches the input. If the target attribute of the
--   comparison is a set ("<tt>SS</tt> ", "<tt>NS</tt> ", or "<tt>BS</tt>
--   "), then the operator evaluates to true if it </i>does not<i> find an
--   exact match with any member of the set. NOT_CONTAINS is supported for
--   lists: When evaluating "<tt>a NOT CONTAINS b</tt> ", "<tt>a</tt> " can
--   be a list; however, "<tt>b</tt> " cannot be a set, a map, or a list. *
--   <tt>BEGINS_WITH</tt> : Checks for a prefix. </i>AttributeValueList<i>
--   can contain only one </i>AttributeValue<i> of type String or Binary
--   (not a Number or a set type). The target attribute of the comparison
--   must be of type String or Binary (not a Number or a set type). *
--   <tt>IN</tt> : Checks for matching elements within two sets.
--   </i>AttributeValueList<i> can contain one or more
--   </i>AttributeValue<i> elements of type String, Number, or Binary (not
--   a set type). These attributes are compared against an existing set
--   type attribute of an item. If any elements of the input set are
--   present in the item attribute, the expression evaluates to true. *
--   <tt>BETWEEN</tt> : Greater than or equal to the first value, and less
--   than or equal to the second value. </i>AttributeValueList<i> must
--   contain two </i>AttributeValue<i> elements of the same type, either
--   String, Number, or Binary (not a set type). A target attribute matches
--   if the target value is greater than, or equal to, the first element
--   and less than, or equal to, the second element. If an item contains an
--   </i>AttributeValue<i> element of a different type than the one
--   provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not compare to <tt>{<a>N</a>:"6"}</tt> .
--   Also, <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6",
--   "2", "1"]}</tt> For usage examples of </i>AttributeValueList<i> and
--   </i>ComparisonOperator<i> , see
--   &lt;http:</i><i>docs.aws.amazon.com</i>amazondynamodb<i>latest</i>developerguide<i>LegacyConditionalParameters.html
--   Legacy Conditional Parameters&gt; in the </i>Amazon DynamoDB Developer
--   Guide<i> . For backward compatibility with previous DynamoDB releases,
--   the following parameters can be used instead of
--   </i>AttributeValueList<i> and </i>ComparisonOperator<i> : *
--   </i>Value<i> - A value for DynamoDB to compare with an attribute. *
--   </i>Exists<i> - A Boolean value that causes DynamoDB to evaluate the
--   value before attempting the conditional operation: * If </i>Exists<i>
--   is <tt>true</tt> , DynamoDB will check to see if that attribute value
--   already exists in the table. If it is found, then the condition
--   evaluates to true; otherwise the condition evaluate to false. * If
--   </i>Exists<i> is <tt>false</tt> , DynamoDB assumes that the attribute
--   value does </i>not<i> exist in the table. If in fact the value does
--   not exist, then the assumption is valid and the condition evaluates to
--   true. If the value is found, despite the assumption that it does not
--   exist, the condition evaluates to false. Note that the default value
--   for </i>Exists<i> is <tt>true</tt> . The </i>Value<i> and
--   </i>Exists<i> parameters are incompatible with
--   </i>AttributeValueList<i> and </i>ComparisonOperator<i> . Note that if
--   you use both sets of parameters at once, DynamoDB will return a
--   </i>ValidationException/ exception.
diExpected :: Lens' DeleteItem (HashMap Text ExpectedAttributeValue)

-- | The name of the table from which to delete the item.
diTableName :: Lens' DeleteItem Text

-- | A map of attribute names to <i>AttributeValue</i> objects,
--   representing the primary key of the item to delete. For the primary
--   key, you must provide all of the attributes. For example, with a
--   simple primary key, you only need to provide a value for the partition
--   key. For a composite primary key, you must provide values for both the
--   partition key and the sort key.
diKey :: Lens' DeleteItem (HashMap Text AttributeValue)

-- | Creates a value of <a>DeleteItemResponse</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>dirsItemCollectionMetrics</a> - Information about item
--   collections, if any, that were affected by the operation.
--   <i>ItemCollectionMetrics</i> is only returned if the request asked for
--   it. If the table does not have any local secondary indexes, this
--   information is not returned in the response. Each
--   <i>ItemCollectionMetrics</i> element consists of: *
--   <i>ItemCollectionKey</i> - The partition key value of the item
--   collection. This is the same as the partition key value of the item
--   itself. * <i>SizeEstimateRange</i> - An estimate of item collection
--   size, in gigabytes. This value is a two-element array containing a
--   lower bound and an upper bound for the estimate. The estimate includes
--   the size of all the items in the table, plus the size of all
--   attributes projected into all of the local secondary indexes on that
--   table. Use this estimate to measure whether a local secondary index is
--   approaching its size limit. The estimate is subject to change over
--   time; therefore, do not rely on the precision or accuracy of the
--   estimate.</li>
--   <li><a>dirsConsumedCapacity</a> - Undocumented member.</li>
--   <li><a>dirsAttributes</a> - A map of attribute names to
--   <i>AttributeValue</i> objects, representing the item as it appeared
--   before the <i>DeleteItem</i> operation. This map appears in the
--   response only if <i>ReturnValues</i> was specified as <tt>ALL_OLD</tt>
--   in the request.</li>
--   <li><a>dirsResponseStatus</a> - -- | The response status code.</li>
--   </ul>
deleteItemResponse :: Int -> DeleteItemResponse

-- | Represents the output of a <i>DeleteItem</i> operation.
--   
--   <i>See:</i> <a>deleteItemResponse</a> smart constructor.
data DeleteItemResponse

-- | Information about item collections, if any, that were affected by the
--   operation. <i>ItemCollectionMetrics</i> is only returned if the
--   request asked for it. If the table does not have any local secondary
--   indexes, this information is not returned in the response. Each
--   <i>ItemCollectionMetrics</i> element consists of: *
--   <i>ItemCollectionKey</i> - The partition key value of the item
--   collection. This is the same as the partition key value of the item
--   itself. * <i>SizeEstimateRange</i> - An estimate of item collection
--   size, in gigabytes. This value is a two-element array containing a
--   lower bound and an upper bound for the estimate. The estimate includes
--   the size of all the items in the table, plus the size of all
--   attributes projected into all of the local secondary indexes on that
--   table. Use this estimate to measure whether a local secondary index is
--   approaching its size limit. The estimate is subject to change over
--   time; therefore, do not rely on the precision or accuracy of the
--   estimate.
dirsItemCollectionMetrics :: Lens' DeleteItemResponse (Maybe ItemCollectionMetrics)

-- | Undocumented member.
dirsConsumedCapacity :: Lens' DeleteItemResponse (Maybe ConsumedCapacity)

-- | A map of attribute names to <i>AttributeValue</i> objects,
--   representing the item as it appeared before the <i>DeleteItem</i>
--   operation. This map appears in the response only if
--   <i>ReturnValues</i> was specified as <tt>ALL_OLD</tt> in the request.
dirsAttributes :: Lens' DeleteItemResponse (HashMap Text AttributeValue)

-- | <ul>
--   <li>- | The response status code.</li>
--   </ul>
dirsResponseStatus :: Lens' DeleteItemResponse Int
instance GHC.Generics.Generic Network.AWS.DynamoDB.DeleteItem.DeleteItemResponse
instance Data.Data.Data Network.AWS.DynamoDB.DeleteItem.DeleteItemResponse
instance GHC.Show.Show Network.AWS.DynamoDB.DeleteItem.DeleteItemResponse
instance GHC.Read.Read Network.AWS.DynamoDB.DeleteItem.DeleteItemResponse
instance GHC.Classes.Eq Network.AWS.DynamoDB.DeleteItem.DeleteItemResponse
instance GHC.Generics.Generic Network.AWS.DynamoDB.DeleteItem.DeleteItem
instance Data.Data.Data Network.AWS.DynamoDB.DeleteItem.DeleteItem
instance GHC.Show.Show Network.AWS.DynamoDB.DeleteItem.DeleteItem
instance GHC.Read.Read Network.AWS.DynamoDB.DeleteItem.DeleteItem
instance GHC.Classes.Eq Network.AWS.DynamoDB.DeleteItem.DeleteItem
instance Network.AWS.Types.AWSRequest Network.AWS.DynamoDB.DeleteItem.DeleteItem
instance Data.Hashable.Class.Hashable Network.AWS.DynamoDB.DeleteItem.DeleteItem
instance Control.DeepSeq.NFData Network.AWS.DynamoDB.DeleteItem.DeleteItem
instance Network.AWS.Data.Headers.ToHeaders Network.AWS.DynamoDB.DeleteItem.DeleteItem
instance Data.Aeson.Types.ToJSON.ToJSON Network.AWS.DynamoDB.DeleteItem.DeleteItem
instance Network.AWS.Data.Path.ToPath Network.AWS.DynamoDB.DeleteItem.DeleteItem
instance Network.AWS.Data.Query.ToQuery Network.AWS.DynamoDB.DeleteItem.DeleteItem
instance Control.DeepSeq.NFData Network.AWS.DynamoDB.DeleteItem.DeleteItemResponse


-- | The <i>CreateTable</i> operation adds a new table to your account. In
--   an AWS account, table names must be unique within each region. That
--   is, you can have two tables with same name if you create the tables in
--   different regions.
--   
--   <i>CreateTable</i> is an asynchronous operation. Upon receiving a
--   <i>CreateTable</i> request, DynamoDB immediately returns a response
--   with a <i>TableStatus</i> of <tt>CREATING</tt> . After the table is
--   created, DynamoDB sets the <i>TableStatus</i> to <tt>ACTIVE</tt> . You
--   can perform read and write operations only on an <tt>ACTIVE</tt>
--   table.
--   
--   You can optionally define secondary indexes on the new table, as part
--   of the <i>CreateTable</i> operation. If you want to create multiple
--   tables with secondary indexes on them, you must create the tables
--   sequentially. Only one table with secondary indexes can be in the
--   <tt>CREATING</tt> state at any given time.
--   
--   You can use the <i>DescribeTable</i> API to check the table status.
module Network.AWS.DynamoDB.CreateTable

-- | Creates a value of <a>CreateTable</a> with the minimum fields required
--   to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>ctGlobalSecondaryIndexes</a> - One or more global secondary
--   indexes (the maximum is five) to be created on the table. Each global
--   secondary index in the array includes the following: *
--   <i>IndexName</i> - The name of the global secondary index. Must be
--   unique only for this table. * <i>KeySchema</i> - Specifies the key
--   schema for the global secondary index. * <i>Projection</i> - Specifies
--   attributes that are copied (projected) from the table into the index.
--   These are in addition to the primary key attributes and index key
--   attributes, which are automatically projected. Each attribute
--   specification is composed of: * <i>ProjectionType</i> - One of the
--   following: * <tt>KEYS_ONLY</tt> - Only the index and primary keys are
--   projected into the index. * <tt>INCLUDE</tt> - Only the specified
--   table attributes are projected into the index. The list of projected
--   attributes are in <i>NonKeyAttributes</i> . * <tt>ALL</tt> - All of
--   the table attributes are projected into the index. *
--   <i>NonKeyAttributes</i> - A list of one or more non-key attribute
--   names that are projected into the secondary index. The total count of
--   attributes provided in <i>NonKeyAttributes</i> , summed across all of
--   the secondary indexes, must not exceed 20. If you project the same
--   attribute into two different indexes, this counts as two distinct
--   attributes when determining the total. * <i>ProvisionedThroughput</i>
--   - The provisioned throughput settings for the global secondary index,
--   consisting of read and write capacity units.</li>
--   <li><a>ctLocalSecondaryIndexes</a> - One or more local secondary
--   indexes (the maximum is five) to be created on the table. Each index
--   is scoped to a given partition key value. There is a 10 GB size limit
--   per partition key value; otherwise, the size of a local secondary
--   index is unconstrained. Each local secondary index in the array
--   includes the following: * <i>IndexName</i> - The name of the local
--   secondary index. Must be unique only for this table. *
--   <i>KeySchema</i> - Specifies the key schema for the local secondary
--   index. The key schema must begin with the same partition key as the
--   table. * <i>Projection</i> - Specifies attributes that are copied
--   (projected) from the table into the index. These are in addition to
--   the primary key attributes and index key attributes, which are
--   automatically projected. Each attribute specification is composed of:
--   * <i>ProjectionType</i> - One of the following: * <tt>KEYS_ONLY</tt> -
--   Only the index and primary keys are projected into the index. *
--   <tt>INCLUDE</tt> - Only the specified table attributes are projected
--   into the index. The list of projected attributes are in
--   <i>NonKeyAttributes</i> . * <tt>ALL</tt> - All of the table attributes
--   are projected into the index. * <i>NonKeyAttributes</i> - A list of
--   one or more non-key attribute names that are projected into the
--   secondary index. The total count of attributes provided in
--   <i>NonKeyAttributes</i> , summed across all of the secondary indexes,
--   must not exceed 20. If you project the same attribute into two
--   different indexes, this counts as two distinct attributes when
--   determining the total.</li>
--   <li><a>ctStreamSpecification</a> - The settings for DynamoDB Streams
--   on the table. These settings consist of: * <i>StreamEnabled</i> -
--   Indicates whether Streams is to be enabled (true) or disabled (false).
--   * <i>StreamViewType</i> - When an item in the table is modified,
--   <i>StreamViewType</i> determines what information is written to the
--   table's stream. Valid values for <i>StreamViewType</i> are: *
--   <i>KEYS_ONLY</i> - Only the key attributes of the modified item are
--   written to the stream. * <i>NEW_IMAGE</i> - The entire item, as it
--   appears after it was modified, is written to the stream. *
--   <i>OLD_IMAGE</i> - The entire item, as it appeared before it was
--   modified, is written to the stream. * <i>NEW_AND_OLD_IMAGES</i> - Both
--   the new and the old item images of the item are written to the
--   stream.</li>
--   <li><a>ctAttributeDefinitions</a> - An array of attributes that
--   describe the key schema for the table and indexes.</li>
--   <li><a>ctTableName</a> - The name of the table to create.</li>
--   <li><a>ctKeySchema</a> - Specifies the attributes that make up the
--   primary key for a table or an index. The attributes in
--   <i>KeySchema</i> must also be defined in the
--   <i>AttributeDefinitions</i> array. For more information, see <a>Data
--   Model</a> in the <i>Amazon DynamoDB Developer Guide</i> . Each
--   <i>KeySchemaElement</i> in the array is composed of: *
--   <i>AttributeName</i> - The name of this key attribute. *
--   <i>KeyType</i> - The role that the key attribute will assume: *
--   <tt>HASH</tt> - partition key * <tt>RANGE</tt> - sort key For a simple
--   primary key (partition key), you must provide exactly one element with
--   a <i>KeyType</i> of <tt>HASH</tt> . For a composite primary key
--   (partition key and sort key), you must provide exactly two elements,
--   in this order: The first element must have a <i>KeyType</i> of
--   <tt>HASH</tt> , and the second element must have a <i>KeyType</i> of
--   <tt>RANGE</tt> . For more information, see <a>Specifying the Primary
--   Key</a> in the <i>Amazon DynamoDB Developer Guide</i> .</li>
--   <li><a>ctProvisionedThroughput</a> - Undocumented member.</li>
--   </ul>
createTable :: Text -> NonEmpty KeySchemaElement -> ProvisionedThroughput -> CreateTable

-- | Represents the input of a <i>CreateTable</i> operation.
--   
--   <i>See:</i> <a>createTable</a> smart constructor.
data CreateTable

-- | One or more global secondary indexes (the maximum is five) to be
--   created on the table. Each global secondary index in the array
--   includes the following: * <i>IndexName</i> - The name of the global
--   secondary index. Must be unique only for this table. *
--   <i>KeySchema</i> - Specifies the key schema for the global secondary
--   index. * <i>Projection</i> - Specifies attributes that are copied
--   (projected) from the table into the index. These are in addition to
--   the primary key attributes and index key attributes, which are
--   automatically projected. Each attribute specification is composed of:
--   * <i>ProjectionType</i> - One of the following: * <tt>KEYS_ONLY</tt> -
--   Only the index and primary keys are projected into the index. *
--   <tt>INCLUDE</tt> - Only the specified table attributes are projected
--   into the index. The list of projected attributes are in
--   <i>NonKeyAttributes</i> . * <tt>ALL</tt> - All of the table attributes
--   are projected into the index. * <i>NonKeyAttributes</i> - A list of
--   one or more non-key attribute names that are projected into the
--   secondary index. The total count of attributes provided in
--   <i>NonKeyAttributes</i> , summed across all of the secondary indexes,
--   must not exceed 20. If you project the same attribute into two
--   different indexes, this counts as two distinct attributes when
--   determining the total. * <i>ProvisionedThroughput</i> - The
--   provisioned throughput settings for the global secondary index,
--   consisting of read and write capacity units.
ctGlobalSecondaryIndexes :: Lens' CreateTable [GlobalSecondaryIndex]

-- | One or more local secondary indexes (the maximum is five) to be
--   created on the table. Each index is scoped to a given partition key
--   value. There is a 10 GB size limit per partition key value; otherwise,
--   the size of a local secondary index is unconstrained. Each local
--   secondary index in the array includes the following: *
--   <i>IndexName</i> - The name of the local secondary index. Must be
--   unique only for this table. * <i>KeySchema</i> - Specifies the key
--   schema for the local secondary index. The key schema must begin with
--   the same partition key as the table. * <i>Projection</i> - Specifies
--   attributes that are copied (projected) from the table into the index.
--   These are in addition to the primary key attributes and index key
--   attributes, which are automatically projected. Each attribute
--   specification is composed of: * <i>ProjectionType</i> - One of the
--   following: * <tt>KEYS_ONLY</tt> - Only the index and primary keys are
--   projected into the index. * <tt>INCLUDE</tt> - Only the specified
--   table attributes are projected into the index. The list of projected
--   attributes are in <i>NonKeyAttributes</i> . * <tt>ALL</tt> - All of
--   the table attributes are projected into the index. *
--   <i>NonKeyAttributes</i> - A list of one or more non-key attribute
--   names that are projected into the secondary index. The total count of
--   attributes provided in <i>NonKeyAttributes</i> , summed across all of
--   the secondary indexes, must not exceed 20. If you project the same
--   attribute into two different indexes, this counts as two distinct
--   attributes when determining the total.
ctLocalSecondaryIndexes :: Lens' CreateTable [LocalSecondaryIndex]

-- | The settings for DynamoDB Streams on the table. These settings consist
--   of: * <i>StreamEnabled</i> - Indicates whether Streams is to be
--   enabled (true) or disabled (false). * <i>StreamViewType</i> - When an
--   item in the table is modified, <i>StreamViewType</i> determines what
--   information is written to the table's stream. Valid values for
--   <i>StreamViewType</i> are: * <i>KEYS_ONLY</i> - Only the key
--   attributes of the modified item are written to the stream. *
--   <i>NEW_IMAGE</i> - The entire item, as it appears after it was
--   modified, is written to the stream. * <i>OLD_IMAGE</i> - The entire
--   item, as it appeared before it was modified, is written to the stream.
--   * <i>NEW_AND_OLD_IMAGES</i> - Both the new and the old item images of
--   the item are written to the stream.
ctStreamSpecification :: Lens' CreateTable (Maybe StreamSpecification)

-- | An array of attributes that describe the key schema for the table and
--   indexes.
ctAttributeDefinitions :: Lens' CreateTable [AttributeDefinition]

-- | The name of the table to create.
ctTableName :: Lens' CreateTable Text

-- | Specifies the attributes that make up the primary key for a table or
--   an index. The attributes in <i>KeySchema</i> must also be defined in
--   the <i>AttributeDefinitions</i> array. For more information, see
--   <a>Data Model</a> in the <i>Amazon DynamoDB Developer Guide</i> . Each
--   <i>KeySchemaElement</i> in the array is composed of: *
--   <i>AttributeName</i> - The name of this key attribute. *
--   <i>KeyType</i> - The role that the key attribute will assume: *
--   <tt>HASH</tt> - partition key * <tt>RANGE</tt> - sort key For a simple
--   primary key (partition key), you must provide exactly one element with
--   a <i>KeyType</i> of <tt>HASH</tt> . For a composite primary key
--   (partition key and sort key), you must provide exactly two elements,
--   in this order: The first element must have a <i>KeyType</i> of
--   <tt>HASH</tt> , and the second element must have a <i>KeyType</i> of
--   <tt>RANGE</tt> . For more information, see <a>Specifying the Primary
--   Key</a> in the <i>Amazon DynamoDB Developer Guide</i> .
ctKeySchema :: Lens' CreateTable (NonEmpty KeySchemaElement)

-- | Undocumented member.
ctProvisionedThroughput :: Lens' CreateTable ProvisionedThroughput

-- | Creates a value of <a>CreateTableResponse</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>ctrsTableDescription</a> - Undocumented member.</li>
--   <li><a>ctrsResponseStatus</a> - -- | The response status code.</li>
--   </ul>
createTableResponse :: Int -> CreateTableResponse

-- | Represents the output of a <i>CreateTable</i> operation.
--   
--   <i>See:</i> <a>createTableResponse</a> smart constructor.
data CreateTableResponse

-- | Undocumented member.
ctrsTableDescription :: Lens' CreateTableResponse (Maybe TableDescription)

-- | <ul>
--   <li>- | The response status code.</li>
--   </ul>
ctrsResponseStatus :: Lens' CreateTableResponse Int
instance GHC.Generics.Generic Network.AWS.DynamoDB.CreateTable.CreateTableResponse
instance Data.Data.Data Network.AWS.DynamoDB.CreateTable.CreateTableResponse
instance GHC.Show.Show Network.AWS.DynamoDB.CreateTable.CreateTableResponse
instance GHC.Read.Read Network.AWS.DynamoDB.CreateTable.CreateTableResponse
instance GHC.Classes.Eq Network.AWS.DynamoDB.CreateTable.CreateTableResponse
instance GHC.Generics.Generic Network.AWS.DynamoDB.CreateTable.CreateTable
instance Data.Data.Data Network.AWS.DynamoDB.CreateTable.CreateTable
instance GHC.Show.Show Network.AWS.DynamoDB.CreateTable.CreateTable
instance GHC.Read.Read Network.AWS.DynamoDB.CreateTable.CreateTable
instance GHC.Classes.Eq Network.AWS.DynamoDB.CreateTable.CreateTable
instance Network.AWS.Types.AWSRequest Network.AWS.DynamoDB.CreateTable.CreateTable
instance Data.Hashable.Class.Hashable Network.AWS.DynamoDB.CreateTable.CreateTable
instance Control.DeepSeq.NFData Network.AWS.DynamoDB.CreateTable.CreateTable
instance Network.AWS.Data.Headers.ToHeaders Network.AWS.DynamoDB.CreateTable.CreateTable
instance Data.Aeson.Types.ToJSON.ToJSON Network.AWS.DynamoDB.CreateTable.CreateTable
instance Network.AWS.Data.Path.ToPath Network.AWS.DynamoDB.CreateTable.CreateTable
instance Network.AWS.Data.Query.ToQuery Network.AWS.DynamoDB.CreateTable.CreateTable
instance Control.DeepSeq.NFData Network.AWS.DynamoDB.CreateTable.CreateTableResponse


-- | The <i>BatchWriteItem</i> operation puts or deletes multiple items in
--   one or more tables. A single call to <i>BatchWriteItem</i> can write
--   up to 16 MB of data, which can comprise as many as 25 put or delete
--   requests. Individual items to be written can be as large as 400 KB.
--   
--   The individual <i>PutItem</i> and <i>DeleteItem</i> operations
--   specified in <i>BatchWriteItem</i> are atomic; however
--   <i>BatchWriteItem</i> as a whole is not. If any requested operations
--   fail because the table's provisioned throughput is exceeded or an
--   internal processing failure occurs, the failed operations are returned
--   in the <i>UnprocessedItems</i> response parameter. You can investigate
--   and optionally resend the requests. Typically, you would call
--   <i>BatchWriteItem</i> in a loop. Each iteration would check for
--   unprocessed items and submit a new <i>BatchWriteItem</i> request with
--   those unprocessed items until all items have been processed.
--   
--   Note that if <i>none</i> of the items can be processed due to
--   insufficient provisioned throughput on all of the tables in the
--   request, then <i>BatchWriteItem</i> will return a
--   <i>ProvisionedThroughputExceededException</i> .
--   
--   <i>Important:</i> If DynamoDB returns any unprocessed items, you
--   should retry the batch operation on those items. However, <i>we
--   strongly recommend that you use an exponential backoff algorithm</i> .
--   If you retry the batch operation immediately, the underlying read or
--   write requests can still fail due to throttling on the individual
--   tables. If you delay the batch operation using exponential backoff,
--   the individual requests in the batch are much more likely to succeed.
--   
--   For more information, see <a>Batch Operations and Error Handling</a>
--   in the <i>Amazon DynamoDB Developer Guide</i> .
--   
--   With <i>BatchWriteItem</i> , you can efficiently write or delete large
--   amounts of data, such as from Amazon Elastic MapReduce (EMR), or copy
--   data from another database into DynamoDB. In order to improve
--   performance with these large-scale operations, <i>BatchWriteItem</i>
--   does not behave in the same way as individual <i>PutItem</i> and
--   <i>DeleteItem</i> calls would. For example, you cannot specify
--   conditions on individual put and delete requests, and
--   <i>BatchWriteItem</i> does not return deleted items in the response.
--   
--   If you use a programming language that supports concurrency, you can
--   use threads to write items in parallel. Your application must include
--   the necessary logic to manage the threads. With languages that don't
--   support threading, you must update or delete the specified items one
--   at a time. In both situations, <i>BatchWriteItem</i> provides an
--   alternative where the API performs the specified put and delete
--   operations in parallel, giving you the power of the thread pool
--   approach without having to introduce complexity into your application.
--   
--   Parallel processing reduces latency, but each specified put and delete
--   request consumes the same number of write capacity units whether it is
--   processed in parallel or not. Delete operations on nonexistent items
--   consume one write capacity unit.
--   
--   If one or more of the following is true, DynamoDB rejects the entire
--   batch write operation:
--   
--   <ul>
--   <li>One or more tables specified in the <i>BatchWriteItem</i> request
--   does not exist.</li>
--   <li>Primary key attributes specified on an item in the request do not
--   match those in the corresponding table's primary key schema.</li>
--   <li>You try to perform multiple operations on the same item in the
--   same <i>BatchWriteItem</i> request. For example, you cannot put and
--   delete the same item in the same <i>BatchWriteItem</i> request.</li>
--   <li>There are more than 25 requests in the batch.</li>
--   <li>Any individual item in a batch exceeds 400 KB.</li>
--   <li>The total request size exceeds 16 MB.</li>
--   </ul>
module Network.AWS.DynamoDB.BatchWriteItem

-- | Creates a value of <a>BatchWriteItem</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>bwiReturnConsumedCapacity</a> - Undocumented member.</li>
--   <li><a>bwiReturnItemCollectionMetrics</a> - Determines whether item
--   collection metrics are returned. If set to <tt>SIZE</tt> , the
--   response includes statistics about item collections, if any, that were
--   modified during the operation are returned in the response. If set to
--   <tt>NONE</tt> (the default), no statistics are returned.</li>
--   <li><a>bwiRequestItems</a> - A map of one or more table names and, for
--   each table, a list of operations to be performed (<i>DeleteRequest</i>
--   or <i>PutRequest</i> ). Each element in the map consists of the
--   following: * <i>DeleteRequest</i> - Perform a <i>DeleteItem</i>
--   operation on the specified item. The item to be deleted is identified
--   by a <i>Key</i> subelement: * <i>Key</i> - A map of primary key
--   attribute values that uniquely identify the ! item. Each entry in this
--   map consists of an attribute name and an attribute value. For each
--   primary key, you must provide <i>all</i> of the key attributes. For
--   example, with a simple primary key, you only need to provide a value
--   for the partition key. For a composite primary key, you must provide
--   values for <i>both</i> the partition key and the sort key. *
--   <i>PutRequest</i> - Perform a <i>PutItem</i> operation on the
--   specified item. The item to be put is identified by an <i>Item</i>
--   subelement: * <i>Item</i> - A map of attributes and their values. Each
--   entry in this map consists of an attribute name and an attribute
--   value. Attribute values must not be null; string and binary type
--   attributes must have lengths greater than zero; and set type
--   attributes must not be empty. Requests that contain empty values will
--   be rejected with a <i>ValidationException</i> exception. If you
--   specify any attributes that are part of an index key, then the data
--   types for those attributes must match those of the schema in the
--   table's attribute definition.</li>
--   </ul>
batchWriteItem :: BatchWriteItem

-- | Represents the input of a <i>BatchWriteItem</i> operation.
--   
--   <i>See:</i> <a>batchWriteItem</a> smart constructor.
data BatchWriteItem

-- | Undocumented member.
bwiReturnConsumedCapacity :: Lens' BatchWriteItem (Maybe ReturnConsumedCapacity)

-- | Determines whether item collection metrics are returned. If set to
--   <tt>SIZE</tt> , the response includes statistics about item
--   collections, if any, that were modified during the operation are
--   returned in the response. If set to <tt>NONE</tt> (the default), no
--   statistics are returned.
bwiReturnItemCollectionMetrics :: Lens' BatchWriteItem (Maybe ReturnItemCollectionMetrics)

-- | A map of one or more table names and, for each table, a list of
--   operations to be performed (<i>DeleteRequest</i> or <i>PutRequest</i>
--   ). Each element in the map consists of the following: *
--   <i>DeleteRequest</i> - Perform a <i>DeleteItem</i> operation on the
--   specified item. The item to be deleted is identified by a <i>Key</i>
--   subelement: * <i>Key</i> - A map of primary key attribute values that
--   uniquely identify the ! item. Each entry in this map consists of an
--   attribute name and an attribute value. For each primary key, you must
--   provide <i>all</i> of the key attributes. For example, with a simple
--   primary key, you only need to provide a value for the partition key.
--   For a composite primary key, you must provide values for <i>both</i>
--   the partition key and the sort key. * <i>PutRequest</i> - Perform a
--   <i>PutItem</i> operation on the specified item. The item to be put is
--   identified by an <i>Item</i> subelement: * <i>Item</i> - A map of
--   attributes and their values. Each entry in this map consists of an
--   attribute name and an attribute value. Attribute values must not be
--   null; string and binary type attributes must have lengths greater than
--   zero; and set type attributes must not be empty. Requests that contain
--   empty values will be rejected with a <i>ValidationException</i>
--   exception. If you specify any attributes that are part of an index
--   key, then the data types for those attributes must match those of the
--   schema in the table's attribute definition.
bwiRequestItems :: Lens' BatchWriteItem (HashMap Text (NonEmpty WriteRequest))

-- | Creates a value of <a>BatchWriteItemResponse</a> with the minimum
--   fields required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>bwirsItemCollectionMetrics</a> - A list of tables that were
--   processed by <i>BatchWriteItem</i> and, for each table, information
--   about any item collections that were affected by individual
--   <i>DeleteItem</i> or <i>PutItem</i> operations. Each entry consists of
--   the following subelements: * <i>ItemCollectionKey</i> - The partition
--   key value of the item collection. This is the same as the partition
--   key value of the item. * <i>SizeEstimateRange</i> - An estimate of
--   item collection size, expressed in GB. This is a two-element array
--   containing a lower bound and an upper bound for the estimate. The
--   estimate includes the size of all the items in the table, plus the
--   size of all attributes projected into all of the local secondary
--   indexes on the table. Use this estimate to measure whether a local
--   secondary index is approaching its size limit. The estimate is subject
--   to change over time; therefore, do not rely on the precision or
--   accuracy of the estimate.</li>
--   <li><a>bwirsConsumedCapacity</a> - The capacity units consumed by the
--   operation. Each element consists of: * <i>TableName</i> - The table
--   that consumed the provisioned throughput. * <i>CapacityUnits</i> - The
--   total number of capacity units consumed.</li>
--   <li><a>bwirsUnprocessedItems</a> - A map of tables and requests
--   against those tables that were not processed. The
--   <i>UnprocessedItems</i> value is in the same form as
--   <i>RequestItems</i> , so you can provide this value directly to a
--   subsequent <i>BatchGetItem</i> operation. For more information, see
--   <i>RequestItems</i> in the Request Parameters section. Each
--   <i>UnprocessedItems</i> entry consists of a table name and, for that
--   table, a list of operations to perform (<i>DeleteRequest</i> or
--   <i>PutRequest</i> ). * <i>DeleteRequest</i> - Perform a
--   <i>DeleteItem</i> operation on the specified item. The item to be
--   deleted is identified by a <i>Key</i> subelement: * <i>Key</i> - A map
--   of primary key attribute values that uniquely identify the item. Each
--   entry in this map consists of an attribute name and an attribute
--   value. * <i>PutRequest</i> - Perform a <i>PutItem</i> operation on the
--   specified item. The item to be put is identified by an <i>Item</i>
--   subelement: * <i>Item</i> - A map of attributes and their values. Each
--   entry in this map consists of an attribute name and an attribute
--   value. Attribute values must not be null; string and binary type
--   attributes must have lengths greater than zero; and set type
--   attributes must not be empty. Requests that contain empty values will
--   be rejected with a <i>ValidationException</i> exception. If you
--   specify any attributes that are part of an index key, then the data
--   types for those attributes must match those of the schema in the
--   table's attribute definition. If there are no unprocessed items
--   remaining, the response contains an empty <i>UnprocessedItems</i>
--   map.</li>
--   <li><a>bwirsResponseStatus</a> - -- | The response status code.</li>
--   </ul>
batchWriteItemResponse :: Int -> BatchWriteItemResponse

-- | Represents the output of a <i>BatchWriteItem</i> operation.
--   
--   <i>See:</i> <a>batchWriteItemResponse</a> smart constructor.
data BatchWriteItemResponse

-- | A list of tables that were processed by <i>BatchWriteItem</i> and, for
--   each table, information about any item collections that were affected
--   by individual <i>DeleteItem</i> or <i>PutItem</i> operations. Each
--   entry consists of the following subelements: *
--   <i>ItemCollectionKey</i> - The partition key value of the item
--   collection. This is the same as the partition key value of the item. *
--   <i>SizeEstimateRange</i> - An estimate of item collection size,
--   expressed in GB. This is a two-element array containing a lower bound
--   and an upper bound for the estimate. The estimate includes the size of
--   all the items in the table, plus the size of all attributes projected
--   into all of the local secondary indexes on the table. Use this
--   estimate to measure whether a local secondary index is approaching its
--   size limit. The estimate is subject to change over time; therefore, do
--   not rely on the precision or accuracy of the estimate.
bwirsItemCollectionMetrics :: Lens' BatchWriteItemResponse (HashMap Text [ItemCollectionMetrics])

-- | The capacity units consumed by the operation. Each element consists
--   of: * <i>TableName</i> - The table that consumed the provisioned
--   throughput. * <i>CapacityUnits</i> - The total number of capacity
--   units consumed.
bwirsConsumedCapacity :: Lens' BatchWriteItemResponse [ConsumedCapacity]

-- | A map of tables and requests against those tables that were not
--   processed. The <i>UnprocessedItems</i> value is in the same form as
--   <i>RequestItems</i> , so you can provide this value directly to a
--   subsequent <i>BatchGetItem</i> operation. For more information, see
--   <i>RequestItems</i> in the Request Parameters section. Each
--   <i>UnprocessedItems</i> entry consists of a table name and, for that
--   table, a list of operations to perform (<i>DeleteRequest</i> or
--   <i>PutRequest</i> ). * <i>DeleteRequest</i> - Perform a
--   <i>DeleteItem</i> operation on the specified item. The item to be
--   deleted is identified by a <i>Key</i> subelement: * <i>Key</i> - A map
--   of primary key attribute values that uniquely identify the item. Each
--   entry in this map consists of an attribute name and an attribute
--   value. * <i>PutRequest</i> - Perform a <i>PutItem</i> operation on the
--   specified item. The item to be put is identified by an <i>Item</i>
--   subelement: * <i>Item</i> - A map of attributes and their values. Each
--   entry in this map consists of an attribute name and an attribute
--   value. Attribute values must not be null; string and binary type
--   attributes must have lengths greater than zero; and set type
--   attributes must not be empty. Requests that contain empty values will
--   be rejected with a <i>ValidationException</i> exception. If you
--   specify any attributes that are part of an index key, then the data
--   types for those attributes must match those of the schema in the
--   table's attribute definition. If there are no unprocessed items
--   remaining, the response contains an empty <i>UnprocessedItems</i> map.
bwirsUnprocessedItems :: Lens' BatchWriteItemResponse (HashMap Text (NonEmpty WriteRequest))

-- | <ul>
--   <li>- | The response status code.</li>
--   </ul>
bwirsResponseStatus :: Lens' BatchWriteItemResponse Int
instance GHC.Generics.Generic Network.AWS.DynamoDB.BatchWriteItem.BatchWriteItemResponse
instance Data.Data.Data Network.AWS.DynamoDB.BatchWriteItem.BatchWriteItemResponse
instance GHC.Show.Show Network.AWS.DynamoDB.BatchWriteItem.BatchWriteItemResponse
instance GHC.Read.Read Network.AWS.DynamoDB.BatchWriteItem.BatchWriteItemResponse
instance GHC.Classes.Eq Network.AWS.DynamoDB.BatchWriteItem.BatchWriteItemResponse
instance GHC.Generics.Generic Network.AWS.DynamoDB.BatchWriteItem.BatchWriteItem
instance Data.Data.Data Network.AWS.DynamoDB.BatchWriteItem.BatchWriteItem
instance GHC.Show.Show Network.AWS.DynamoDB.BatchWriteItem.BatchWriteItem
instance GHC.Read.Read Network.AWS.DynamoDB.BatchWriteItem.BatchWriteItem
instance GHC.Classes.Eq Network.AWS.DynamoDB.BatchWriteItem.BatchWriteItem
instance Network.AWS.Types.AWSRequest Network.AWS.DynamoDB.BatchWriteItem.BatchWriteItem
instance Data.Hashable.Class.Hashable Network.AWS.DynamoDB.BatchWriteItem.BatchWriteItem
instance Control.DeepSeq.NFData Network.AWS.DynamoDB.BatchWriteItem.BatchWriteItem
instance Network.AWS.Data.Headers.ToHeaders Network.AWS.DynamoDB.BatchWriteItem.BatchWriteItem
instance Data.Aeson.Types.ToJSON.ToJSON Network.AWS.DynamoDB.BatchWriteItem.BatchWriteItem
instance Network.AWS.Data.Path.ToPath Network.AWS.DynamoDB.BatchWriteItem.BatchWriteItem
instance Network.AWS.Data.Query.ToQuery Network.AWS.DynamoDB.BatchWriteItem.BatchWriteItem
instance Control.DeepSeq.NFData Network.AWS.DynamoDB.BatchWriteItem.BatchWriteItemResponse


-- | The <i>BatchGetItem</i> operation returns the attributes of one or
--   more items from one or more tables. You identify requested items by
--   primary key.
--   
--   A single operation can retrieve up to 16 MB of data, which can contain
--   as many as 100 items. <i>BatchGetItem</i> will return a partial result
--   if the response size limit is exceeded, the table's provisioned
--   throughput is exceeded, or an internal processing failure occurs. If a
--   partial result is returned, the operation returns a value for
--   <i>UnprocessedKeys</i> . You can use this value to retry the operation
--   starting with the next item to get.
--   
--   <i>Important:</i> If you request more than 100 items
--   <i>BatchGetItem</i> will return a <i>ValidationException</i> with the
--   message "Too many items requested for the BatchGetItem call".
--   
--   For example, if you ask to retrieve 100 items, but each individual
--   item is 300 KB in size, the system returns 52 items (so as not to
--   exceed the 16 MB limit). It also returns an appropriate
--   <i>UnprocessedKeys</i> value so you can get the next page of results.
--   If desired, your application can include its own logic to assemble the
--   pages of results into one data set.
--   
--   If <i>none</i> of the items can be processed due to insufficient
--   provisioned throughput on all of the tables in the request, then
--   <i>BatchGetItem</i> will return a
--   <i>ProvisionedThroughputExceededException</i> . If <i>at least one</i>
--   of the items is successfully processed, then <i>BatchGetItem</i>
--   completes successfully, while returning the keys of the unread items
--   in <i>UnprocessedKeys</i> .
--   
--   <i>Important:</i> If DynamoDB returns any unprocessed items, you
--   should retry the batch operation on those items. However, <i>we
--   strongly recommend that you use an exponential backoff algorithm</i> .
--   If you retry the batch operation immediately, the underlying read or
--   write requests can still fail due to throttling on the individual
--   tables. If you delay the batch operation using exponential backoff,
--   the individual requests in the batch are much more likely to succeed.
--   
--   For more information, see <a>Batch Operations and Error Handling</a>
--   in the <i>Amazon DynamoDB Developer Guide</i> .
--   
--   By default, <i>BatchGetItem</i> performs eventually consistent reads
--   on every table in the request. If you want strongly consistent reads
--   instead, you can set <i>ConsistentRead</i> to <tt>true</tt> for any or
--   all tables.
--   
--   In order to minimize response latency, <i>BatchGetItem</i> retrieves
--   items in parallel.
--   
--   When designing your application, keep in mind that DynamoDB does not
--   return items in any particular order. To help parse the response by
--   item, include the primary key values for the items in your request in
--   the <i>AttributesToGet</i> parameter.
--   
--   If a requested item does not exist, it is not returned in the result.
--   Requests for nonexistent items consume the minimum read capacity units
--   according to the type of read. For more information, see <a>Capacity
--   Units Calculations</a> in the <i>Amazon DynamoDB Developer Guide</i> .
module Network.AWS.DynamoDB.BatchGetItem

-- | Creates a value of <a>BatchGetItem</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>bgiReturnConsumedCapacity</a> - Undocumented member.</li>
--   <li><a>bgiRequestItems</a> - A map of one or more table names and, for
--   each table, a map that describes one or more items to retrieve from
--   that table. Each table name can be used only once per
--   <i>BatchGetItem</i> request. Each element in the map of items to
--   retrieve consists of the following: * <i>ConsistentRead</i> - If
--   <tt>true</tt> , a strongly consistent read is used; if <tt>false</tt>
--   (the default), an eventually consistent read is used. *
--   <i>ExpressionAttributeNames</i> - One or more substitution tokens for
--   attribute names in the <i>ProjectionExpression</i> parameter. The
--   following are some use cases for using <i>ExpressionAttributeNames</i>
--   : * To access an attribute whose name conflicts with a DynamoDB
--   reserved word. * To create a placeholder for repeating occurrences of
--   an attribute name in an expression. * To prevent special characters in
--   an attribute name from being misinterpreted in an expression. Use the
--   <b>#</b> character in an expression to dereference an attribute name.
--   For example, consider the following attribute name: *
--   <tt>Percentile</tt> The name of this attribute conflicts with a
--   reserved word, so it cannot be used directly in an expression. (For
--   the complete list of reserved words, see <a>Reserved Words</a> in the
--   <i>Amazon DynamoDB Developer Guide</i> ). To work around this, you
--   could specify the following for <i>ExpressionAttributeNames</i> : *
--   <tt>{"#P":<a>Percentile</a>}</tt> You could then use this substitution
--   in an expression, as in this example: * <tt>#P = :val</tt> For more
--   information on expression attribute names, see <a>Accessing Item
--   Attributes</a> in the <i>Amazon DynamoDB Developer Guide</i> . *
--   <i>Keys</i> - An array of primary key attribute values that define
--   specific items in the table. For each primary key, you must provide
--   <i>all</i> of the key attributes. For example, with a simple primary
--   key, you only need to provide the partition key value. For a composite
--   key, you must provide <i>both</i> the partition key value and the sort
--   key value. * <i>ProjectionExpression</i> - A string that identifies
--   one or more attributes to retrieve from the table. These attributes
--   can include scalars, sets, or elements of a JSON document. The
--   attributes in the expression must be separated by commas. If no
--   attribute names are specified, then all attributes will be returned.
--   If any of the requested attributes are not found, they will not appear
--   in the result. For more information, see <a>Accessing Item
--   Attributes</a> in the <i>Amazon DynamoDB Developer Guide</i> . *
--   <i>AttributesToGet</i> - <i>Important:</i> This is a legacy parameter,
--   for backward compatibility. New applications should use
--   <i>ProjectionExpression</i> instead. Do not combine legacy parameters
--   and expression parameters in a single API call; otherwise, DynamoDB
--   will return a <i>ValidationException</i> exception. This parameter
--   allows you to retrieve attributes of type List or Map; however, it
--   cannot retrieve individual elements within a List or a Map. The names
--   of one or more attributes to retrieve. If no attribute names are
--   provided, then all attributes will be returned. If any of the
--   requested attributes are not found, they will not appear in the
--   result. Note that <i>AttributesToGet</i> has no effect on provisioned
--   throughput consumption. DynamoDB determines capacity units consumed
--   based on item size, not on the amount of data that is returned to an
--   application.</li>
--   </ul>
batchGetItem :: BatchGetItem

-- | Represents the input of a <i>BatchGetItem</i> operation.
--   
--   <i>See:</i> <a>batchGetItem</a> smart constructor.
data BatchGetItem

-- | Undocumented member.
bgiReturnConsumedCapacity :: Lens' BatchGetItem (Maybe ReturnConsumedCapacity)

-- | A map of one or more table names and, for each table, a map that
--   describes one or more items to retrieve from that table. Each table
--   name can be used only once per <i>BatchGetItem</i> request. Each
--   element in the map of items to retrieve consists of the following: *
--   <i>ConsistentRead</i> - If <tt>true</tt> , a strongly consistent read
--   is used; if <tt>false</tt> (the default), an eventually consistent
--   read is used. * <i>ExpressionAttributeNames</i> - One or more
--   substitution tokens for attribute names in the
--   <i>ProjectionExpression</i> parameter. The following are some use
--   cases for using <i>ExpressionAttributeNames</i> : * To access an
--   attribute whose name conflicts with a DynamoDB reserved word. * To
--   create a placeholder for repeating occurrences of an attribute name in
--   an expression. * To prevent special characters in an attribute name
--   from being misinterpreted in an expression. Use the <b>#</b> character
--   in an expression to dereference an attribute name. For example,
--   consider the following attribute name: * <tt>Percentile</tt> The name
--   of this attribute conflicts with a reserved word, so it cannot be used
--   directly in an expression. (For the complete list of reserved words,
--   see <a>Reserved Words</a> in the <i>Amazon DynamoDB Developer
--   Guide</i> ). To work around this, you could specify the following for
--   <i>ExpressionAttributeNames</i> : * <tt>{"#P":<a>Percentile</a>}</tt>
--   You could then use this substitution in an expression, as in this
--   example: * <tt>#P = :val</tt> For more information on expression
--   attribute names, see <a>Accessing Item Attributes</a> in the <i>Amazon
--   DynamoDB Developer Guide</i> . * <i>Keys</i> - An array of primary key
--   attribute values that define specific items in the table. For each
--   primary key, you must provide <i>all</i> of the key attributes. For
--   example, with a simple primary key, you only need to provide the
--   partition key value. For a composite key, you must provide <i>both</i>
--   the partition key value and the sort key value. *
--   <i>ProjectionExpression</i> - A string that identifies one or more
--   attributes to retrieve from the table. These attributes can include
--   scalars, sets, or elements of a JSON document. The attributes in the
--   expression must be separated by commas. If no attribute names are
--   specified, then all attributes will be returned. If any of the
--   requested attributes are not found, they will not appear in the
--   result. For more information, see <a>Accessing Item Attributes</a> in
--   the <i>Amazon DynamoDB Developer Guide</i> . * <i>AttributesToGet</i>
--   - <i>Important:</i> This is a legacy parameter, for backward
--   compatibility. New applications should use <i>ProjectionExpression</i>
--   instead. Do not combine legacy parameters and expression parameters in
--   a single API call; otherwise, DynamoDB will return a
--   <i>ValidationException</i> exception. This parameter allows you to
--   retrieve attributes of type List or Map; however, it cannot retrieve
--   individual elements within a List or a Map. The names of one or more
--   attributes to retrieve. If no attribute names are provided, then all
--   attributes will be returned. If any of the requested attributes are
--   not found, they will not appear in the result. Note that
--   <i>AttributesToGet</i> has no effect on provisioned throughput
--   consumption. DynamoDB determines capacity units consumed based on item
--   size, not on the amount of data that is returned to an application.
bgiRequestItems :: Lens' BatchGetItem (HashMap Text KeysAndAttributes)

-- | Creates a value of <a>BatchGetItemResponse</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>bgirsUnprocessedKeys</a> - A map of tables and their respective
--   keys that were not processed with the current response. The
--   <i>UnprocessedKeys</i> value is in the same form as
--   <i>RequestItems</i> , so the value can be provided directly to a
--   subsequent <i>BatchGetItem</i> operation. For more information, see
--   <i>RequestItems</i> in the Request Parameters section. Each element
--   consists of: * <i>Keys</i> - An array of primary key attribute values
--   that define specific items in the table. * <i>AttributesToGet</i> -
--   One or more attributes to be retrieved from the table or index. By
--   default, all attributes are returned. If a requested attribute is not
--   found, it does not appear in the result. * <i>ConsistentRead</i> - The
--   consistency of a read operation. If set to <tt>true</tt> , then a
--   strongly consistent read is used; otherwise, an eventually consistent
--   read is used. If there are no unprocessed keys remaining, the response
--   contains an empty <i>UnprocessedKeys</i> map.</li>
--   <li><a>bgirsResponses</a> - A map of table name to a list of items.
--   Each object in <i>Responses</i> consists of a table name, along with a
--   map of attribute data consisting of the data type and attribute
--   value.</li>
--   <li><a>bgirsConsumedCapacity</a> - The read capacity units consumed by
--   the operation. Each element consists of: * <i>TableName</i> - The
--   table that consumed the provisioned throughput. * <i>CapacityUnits</i>
--   - The total number of capacity units consumed.</li>
--   <li><a>bgirsResponseStatus</a> - -- | The response status code.</li>
--   </ul>
batchGetItemResponse :: Int -> BatchGetItemResponse

-- | Represents the output of a <i>BatchGetItem</i> operation.
--   
--   <i>See:</i> <a>batchGetItemResponse</a> smart constructor.
data BatchGetItemResponse

-- | A map of tables and their respective keys that were not processed with
--   the current response. The <i>UnprocessedKeys</i> value is in the same
--   form as <i>RequestItems</i> , so the value can be provided directly to
--   a subsequent <i>BatchGetItem</i> operation. For more information, see
--   <i>RequestItems</i> in the Request Parameters section. Each element
--   consists of: * <i>Keys</i> - An array of primary key attribute values
--   that define specific items in the table. * <i>AttributesToGet</i> -
--   One or more attributes to be retrieved from the table or index. By
--   default, all attributes are returned. If a requested attribute is not
--   found, it does not appear in the result. * <i>ConsistentRead</i> - The
--   consistency of a read operation. If set to <tt>true</tt> , then a
--   strongly consistent read is used; otherwise, an eventually consistent
--   read is used. If there are no unprocessed keys remaining, the response
--   contains an empty <i>UnprocessedKeys</i> map.
bgirsUnprocessedKeys :: Lens' BatchGetItemResponse (HashMap Text KeysAndAttributes)

-- | A map of table name to a list of items. Each object in
--   <i>Responses</i> consists of a table name, along with a map of
--   attribute data consisting of the data type and attribute value.
bgirsResponses :: Lens' BatchGetItemResponse (HashMap Text [HashMap Text AttributeValue])

-- | The read capacity units consumed by the operation. Each element
--   consists of: * <i>TableName</i> - The table that consumed the
--   provisioned throughput. * <i>CapacityUnits</i> - The total number of
--   capacity units consumed.
bgirsConsumedCapacity :: Lens' BatchGetItemResponse [ConsumedCapacity]

-- | <ul>
--   <li>- | The response status code.</li>
--   </ul>
bgirsResponseStatus :: Lens' BatchGetItemResponse Int
instance GHC.Generics.Generic Network.AWS.DynamoDB.BatchGetItem.BatchGetItemResponse
instance Data.Data.Data Network.AWS.DynamoDB.BatchGetItem.BatchGetItemResponse
instance GHC.Show.Show Network.AWS.DynamoDB.BatchGetItem.BatchGetItemResponse
instance GHC.Read.Read Network.AWS.DynamoDB.BatchGetItem.BatchGetItemResponse
instance GHC.Classes.Eq Network.AWS.DynamoDB.BatchGetItem.BatchGetItemResponse
instance GHC.Generics.Generic Network.AWS.DynamoDB.BatchGetItem.BatchGetItem
instance Data.Data.Data Network.AWS.DynamoDB.BatchGetItem.BatchGetItem
instance GHC.Show.Show Network.AWS.DynamoDB.BatchGetItem.BatchGetItem
instance GHC.Read.Read Network.AWS.DynamoDB.BatchGetItem.BatchGetItem
instance GHC.Classes.Eq Network.AWS.DynamoDB.BatchGetItem.BatchGetItem
instance Network.AWS.Types.AWSRequest Network.AWS.DynamoDB.BatchGetItem.BatchGetItem
instance Data.Hashable.Class.Hashable Network.AWS.DynamoDB.BatchGetItem.BatchGetItem
instance Control.DeepSeq.NFData Network.AWS.DynamoDB.BatchGetItem.BatchGetItem
instance Network.AWS.Data.Headers.ToHeaders Network.AWS.DynamoDB.BatchGetItem.BatchGetItem
instance Data.Aeson.Types.ToJSON.ToJSON Network.AWS.DynamoDB.BatchGetItem.BatchGetItem
instance Network.AWS.Data.Path.ToPath Network.AWS.DynamoDB.BatchGetItem.BatchGetItem
instance Network.AWS.Data.Query.ToQuery Network.AWS.DynamoDB.BatchGetItem.BatchGetItem
instance Control.DeepSeq.NFData Network.AWS.DynamoDB.BatchGetItem.BatchGetItemResponse


-- | <b>Amazon DynamoDB</b>
--   
--   This is the Amazon DynamoDB API Reference. This guide provides
--   descriptions of the low-level DynamoDB API.
--   
--   This guide is intended for use with the following DynamoDB
--   documentation:
--   
--   <ul>
--   <li><a>Amazon DynamoDB Getting Started Guide</a> - provides hands-on
--   exercises that help you learn the basics of working with DynamoDB.
--   <i>If you are new to DynamoDB, we recommend that you begin with the
--   Getting Started Guide.</i></li>
--   <li><a>Amazon DynamoDB Developer Guide</a> - contains detailed
--   information about DynamoDB concepts, usage, and best practices.</li>
--   <li><a>Amazon DynamoDB Streams API Reference</a> - provides
--   descriptions and samples of the DynamoDB Streams API. (For more
--   information, see <a>Capturing Table Activity with DynamoDB Streams</a>
--   in the Amazon DynamoDB Developer Guide.)</li>
--   </ul>
--   
--   Instead of making the requests to the low-level DynamoDB API directly
--   from your application, we recommend that you use the AWS Software
--   Development Kits (SDKs). The easy-to-use libraries in the AWS SDKs
--   make it unnecessary to call the low-level DynamoDB API directly from
--   your application. The libraries take care of request authentication,
--   serialization, and connection management. For more information, see
--   <a>Using the AWS SDKs with DynamoDB</a> in the Amazon DynamoDB
--   Developer Guide.
--   
--   If you decide to code against the low-level DynamoDB API directly, you
--   will need to write the necessary code to authenticate your requests.
--   For more information on signing your requests, see <a>Using the
--   DynamoDB API</a> in the <i>Amazon DynamoDB Developer Guide</i> .
--   
--   The following are short descriptions of each low-level API action,
--   organized by function.
--   
--   <b>Managing Tables</b>
--   
--   <ul>
--   <li><i>CreateTable</i> - Creates a table with user-specified
--   provisioned throughput settings. You must define a primary key for the
--   table - either a simple primary key (partition key), or a composite
--   primary key (partition key and sort key). Optionally, you can create
--   one or more secondary indexes, which provide fast data access using
--   non-key attributes.</li>
--   <li><i>DescribeTable</i> - Returns metadata for a table, such as table
--   size, status, and index information.</li>
--   <li><i>UpdateTable</i> - Modifies the provisioned throughput settings
--   for a table. Optionally, you can modify the provisioned throughput
--   settings for global secondary indexes on the table.</li>
--   <li><i>ListTables</i> - Returns a list of all tables associated with
--   the current AWS account and endpoint.</li>
--   <li><i>DeleteTable</i> - Deletes a table and all of its indexes.</li>
--   </ul>
--   
--   For conceptual information about managing tables, see <a>Working with
--   Tables</a> in the <i>Amazon DynamoDB Developer Guide</i> .
--   
--   <b>Reading Data</b>
--   
--   <ul>
--   <li><i>GetItem</i> - Returns a set of attributes for the item that has
--   a given primary key. By default, <i>GetItem</i> performs an eventually
--   consistent read; however, applications can request a strongly
--   consistent read instead.</li>
--   <li><i>BatchGetItem</i> - Performs multiple <i>GetItem</i> requests
--   for data items using their primary keys, from one table or multiple
--   tables. The response from <i>BatchGetItem</i> has a size limit of 16
--   MB and returns a maximum of 100 items. Both eventually consistent and
--   strongly consistent reads can be used.</li>
--   <li><i>Query</i> - Returns one or more items from a table or a
--   secondary index. You must provide a specific value for the partition
--   key. You can narrow the scope of the query using comparison operators
--   against a sort key value, or on the index key. <i>Query</i> supports
--   either eventual or strong consistency. A single response has a size
--   limit of 1 MB.</li>
--   <li><i>Scan</i> - Reads every item in a table; the result set is
--   eventually consistent. You can limit the number of items returned by
--   filtering the data attributes, using conditional expressions.
--   <i>Scan</i> can be used to enable ad-hoc querying of a table against
--   non-key attributes; however, since this is a full table scan without
--   using an index, <i>Scan</i> should not be used for any application
--   query use case that requires predictable performance.</li>
--   </ul>
--   
--   For conceptual information about reading data, see <a>Working with
--   Items</a> and <a>Query and Scan Operations</a> in the <i>Amazon
--   DynamoDB Developer Guide</i> .
--   
--   <b>Modifying Data</b>
--   
--   <ul>
--   <li><i>PutItem</i> - Creates a new item, or replaces an existing item
--   with a new item (including all the attributes). By default, if an item
--   in the table already exists with the same primary key, the new item
--   completely replaces the existing item. You can use conditional
--   operators to replace an item only if its attribute values match
--   certain conditions, or to insert a new item only if that item doesn't
--   already exist.</li>
--   <li><i>UpdateItem</i> - Modifies the attributes of an existing item.
--   You can also use conditional operators to perform an update only if
--   the item's attribute values match certain conditions.</li>
--   <li><i>DeleteItem</i> - Deletes an item in a table by primary key. You
--   can use conditional operators to perform a delete an item only if the
--   item's attribute values match certain conditions.</li>
--   <li><i>BatchWriteItem</i> - Performs multiple <i>PutItem</i> and
--   <i>DeleteItem</i> requests across multiple tables in a single request.
--   A failure of any request(s) in the batch will not cause the entire
--   <i>BatchWriteItem</i> operation to fail. Supports batches of up to 25
--   items to put or delete, with a maximum total request size of 16
--   MB.</li>
--   </ul>
--   
--   For conceptual information about modifying data, see <a>Working with
--   Items</a> and <a>Query and Scan Operations</a> in the <i>Amazon
--   DynamoDB Developer Guide</i> .
module Network.AWS.DynamoDB

-- | API version <tt>2012-08-10</tt> of the Amazon DynamoDB SDK
--   configuration.
dynamoDB :: Service

-- | Your request rate is too high. The AWS SDKs for DynamoDB automatically
--   retry requests that receive this exception. Your request is eventually
--   successful, unless your retry queue is too large to finish. Reduce the
--   frequency of requests and use exponential backoff. For more
--   information, go to <a>Error Retries and Exponential Backoff</a> in the
--   <i>Amazon DynamoDB Developer Guide</i> .
_ProvisionedThroughputExceededException :: AsError a => Getting (First ServiceError) a ServiceError

-- | A condition specified in the operation could not be evaluated.
_ConditionalCheckFailedException :: AsError a => Getting (First ServiceError) a ServiceError

-- | An item collection is too large. This exception is only returned for
--   tables that have one or more local secondary indexes.
_ItemCollectionSizeLimitExceededException :: AsError a => Getting (First ServiceError) a ServiceError

-- | An error occurred on the server side.
_InternalServerError :: AsError a => Getting (First ServiceError) a ServiceError

-- | The operation tried to access a nonexistent table or index. The
--   resource might not be specified correctly, or its status might not be
--   <tt>ACTIVE</tt> .
_ResourceNotFoundException :: AsError a => Getting (First ServiceError) a ServiceError

-- | The number of concurrent table requests (cumulative number of tables
--   in the <tt>CREATING</tt> , <tt>DELETING</tt> or <tt>UPDATING</tt>
--   state) exceeds the maximum allowed of 10.
--   
--   Also, for tables with secondary indexes, only one of those tables can
--   be in the <tt>CREATING</tt> state at any point in time. Do not attempt
--   to create more than one such table simultaneously.
--   
--   The total limit of tables in the <tt>ACTIVE</tt> state is 250.
_LimitExceededException :: AsError a => Getting (First ServiceError) a ServiceError

-- | The operation conflicts with the resource's availability. For example,
--   you attempted to recreate an existing table, or tried to delete a
--   table currently in the <tt>CREATING</tt> state.
_ResourceInUseException :: AsError a => Getting (First ServiceError) a ServiceError

-- | Polls <a>DescribeTable</a> every 20 seconds until a successful state
--   is reached. An error is returned after 25 failed checks.
tableNotExists :: Wait DescribeTable

-- | Polls <a>DescribeTable</a> every 20 seconds until a successful state
--   is reached. An error is returned after 25 failed checks.
tableExists :: Wait DescribeTable
data AttributeAction
Add :: AttributeAction
Delete :: AttributeAction
Put :: AttributeAction
data ComparisonOperator
BeginsWith :: ComparisonOperator
Between :: ComparisonOperator
Contains :: ComparisonOperator
EQ' :: ComparisonOperator
GE :: ComparisonOperator
GT' :: ComparisonOperator
IN :: ComparisonOperator
LE :: ComparisonOperator
LT' :: ComparisonOperator
NE :: ComparisonOperator
NotContains :: ComparisonOperator
NotNull :: ComparisonOperator
Null :: ComparisonOperator
data ConditionalOperator
And :: ConditionalOperator
OR :: ConditionalOperator
data IndexStatus
ISActive :: IndexStatus
ISCreating :: IndexStatus
ISDeleting :: IndexStatus
ISUpdating :: IndexStatus
data KeyType
Hash :: KeyType
Range :: KeyType
data ProjectionType
All :: ProjectionType
Include :: ProjectionType
KeysOnly :: ProjectionType

-- | Determines the level of detail about provisioned throughput
--   consumption that is returned in the response:
--   
--   <ul>
--   <li><i>INDEXES</i> - The response includes the aggregate
--   <i>ConsumedCapacity</i> for the operation, together with
--   <i>ConsumedCapacity</i> for each table and secondary index that was
--   accessed.</li>
--   </ul>
--   
--   Note that some operations, such as <i>GetItem</i> and
--   <i>BatchGetItem</i> , do not access any indexes at all. In these
--   cases, specifying <i>INDEXES</i> will only return
--   <i>ConsumedCapacity</i> information for table(s).
--   
--   <ul>
--   <li><i>TOTAL</i> - The response includes only the aggregate
--   <i>ConsumedCapacity</i> for the operation.</li>
--   <li><i>NONE</i> - No <i>ConsumedCapacity</i> details are included in
--   the response.</li>
--   </ul>
data ReturnConsumedCapacity
RCCIndexes :: ReturnConsumedCapacity
RCCNone :: ReturnConsumedCapacity
RCCTotal :: ReturnConsumedCapacity
data ReturnItemCollectionMetrics
RICMNone :: ReturnItemCollectionMetrics
RICMSize :: ReturnItemCollectionMetrics
data ReturnValue
AllNew :: ReturnValue
AllOld :: ReturnValue
None :: ReturnValue
UpdatedNew :: ReturnValue
UpdatedOld :: ReturnValue
data ScalarAttributeType
B :: ScalarAttributeType
N :: ScalarAttributeType
S :: ScalarAttributeType
data Select
AllAttributes :: Select
AllProjectedAttributes :: Select
Count :: Select
SpecificAttributes :: Select
data StreamViewType
SVTKeysOnly :: StreamViewType
SVTNewAndOldImages :: StreamViewType
SVTNewImage :: StreamViewType
SVTOldImage :: StreamViewType
data TableStatus
Active :: TableStatus
Creating :: TableStatus
Deleting :: TableStatus
Updating :: TableStatus

-- | Represents an attribute for describing the key schema for the table
--   and indexes.
--   
--   <i>See:</i> <a>attributeDefinition</a> smart constructor.
data AttributeDefinition

-- | Creates a value of <a>AttributeDefinition</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>adAttributeName</a> - A name for the attribute.</li>
--   <li><a>adAttributeType</a> - The data type for the attribute, where: *
--   <tt>S</tt> - the attribute is of type String * <tt>N</tt> - the
--   attribute is of type Number * <tt>B</tt> - the attribute is of type
--   Binary</li>
--   </ul>
attributeDefinition :: Text -> ScalarAttributeType -> AttributeDefinition

-- | A name for the attribute.
adAttributeName :: Lens' AttributeDefinition Text

-- | The data type for the attribute, where: * <tt>S</tt> - the attribute
--   is of type String * <tt>N</tt> - the attribute is of type Number *
--   <tt>B</tt> - the attribute is of type Binary
adAttributeType :: Lens' AttributeDefinition ScalarAttributeType

-- | Represents the data for an attribute. You can set one, and only one,
--   of the elements.
--   
--   Each attribute in an item is a name-value pair. An attribute can be
--   single-valued or multi-valued set. For example, a book item can have
--   title and authors attributes. Each book has one title but can have
--   many authors. The multi-valued attribute is a set; duplicate values
--   are not allowed.
--   
--   <i>See:</i> <a>attributeValue</a> smart constructor.
data AttributeValue

-- | Creates a value of <a>AttributeValue</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>avL</a> - A List of attribute values.</li>
--   <li><a>avNS</a> - A Number Set data type.</li>
--   <li><a>avM</a> - A Map of attribute values.</li>
--   <li><a>avNULL</a> - A Null data type.</li>
--   <li><a>avN</a> - A Number data type.</li>
--   <li><a>avBS</a> - A Binary Set data type.</li>
--   <li><a>avB</a> - A Binary data type.-- <i>Note:</i> This <tt>Lens</tt>
--   automatically encodes and decodes Base64 data. The underlying
--   isomorphism will encode to Base64 representation during serialisation,
--   and decode from Base64 representation during deserialisation. This
--   <tt>Lens</tt> accepts and returns only raw unencoded data.</li>
--   <li><a>avSS</a> - A String Set data type.</li>
--   <li><a>avS</a> - A String data type.</li>
--   <li><a>avBOOL</a> - A Boolean data type.</li>
--   </ul>
attributeValue :: AttributeValue

-- | A List of attribute values.
avL :: Lens' AttributeValue [AttributeValue]

-- | A Number Set data type.
avNS :: Lens' AttributeValue [Text]

-- | A Map of attribute values.
avM :: Lens' AttributeValue (HashMap Text AttributeValue)

-- | A Null data type.
avNULL :: Lens' AttributeValue (Maybe Bool)

-- | A Number data type.
avN :: Lens' AttributeValue (Maybe Text)

-- | A Binary Set data type.
avBS :: Lens' AttributeValue [ByteString]

-- | A Binary data type.-- <i>Note:</i> This <tt>Lens</tt> automatically
--   encodes and decodes Base64 data. The underlying isomorphism will
--   encode to Base64 representation during serialisation, and decode from
--   Base64 representation during deserialisation. This <tt>Lens</tt>
--   accepts and returns only raw unencoded data.
avB :: Lens' AttributeValue (Maybe ByteString)

-- | A String Set data type.
avSS :: Lens' AttributeValue [Text]

-- | A String data type.
avS :: Lens' AttributeValue (Maybe Text)

-- | A Boolean data type.
avBOOL :: Lens' AttributeValue (Maybe Bool)

-- | For the <i>UpdateItem</i> operation, represents the attributes to be
--   modified, the action to perform on each, and the new value for each.
--   
--   Attribute values cannot be null; string and binary type attributes
--   must have lengths greater than zero; and set type attributes must not
--   be empty. Requests with empty values will be rejected with a
--   <i>ValidationException</i> exception.
--   
--   <i>See:</i> <a>attributeValueUpdate</a> smart constructor.
data AttributeValueUpdate

-- | Creates a value of <a>AttributeValueUpdate</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>avuValue</a> - Undocumented member.</li>
--   <li><a>avuAction</a> - Specifies how to perform the update. Valid
--   values are <tt>PUT</tt> (default), <tt>DELETE</tt> , and <tt>ADD</tt>
--   . The behavior depends on whether the specified primary key already
--   exists in the table. <b>If an item with the specified <i>Key</i> is
--   found in the table:</b> * <tt>PUT</tt> - Adds the specified attribute
--   to the item. If the attribute already exists, it is replaced by the
--   new value. * <tt>DELETE</tt> - If no value is specified, the attribute
--   and its value are removed from the item. The data type of the
--   specified value must match the existing value's data type. If a
--   <i>set</i> of values is specified, then those values are subtracted
--   from the old set. For example, if the attribute value was the set
--   <tt>[a,b,c]</tt> and the <i>DELETE</i> action specified <tt>[a,c]</tt>
--   , then the final attribute value would be <tt>[b]</tt> . Specifying an
--   empty set is an error. * <tt>ADD</tt> - If the attribute does not
--   already exist, then the attribute and its values are added to the
--   item. If the attribute does exist, then the behavior of <tt>ADD</tt>
--   depends on the data type of the attribute: * If the existing attribute
--   is a number, and if <i>Value</i> is also a number, then the
--   <i>Value</i> is mathematically added to the existing attribute. If
--   <i>Value</i> is a negative number, then it is subtracted from the
--   existing attribute. * If the existing data type is a set, and if the
--   <i>Value</i> is also a set, then the <i>Value</i> is added to the
--   existing set. (This is a <i>set</i> operation, not mathematical
--   addition.) For example, if the attribute value was the set
--   <tt>[1,2]</tt> , and the <tt>ADD</tt> action specified <tt>[3]</tt> ,
--   then the final attribute value would be <tt>[1,2,3]</tt> . An error
--   occurs if an Add action is specified for a set attribute and the
--   attribute type specified does not match the existing set type. Both
--   sets must have the same primitive data type. For example, if the
--   existing data type is a set of strings, the <i>Value</i> must also be
--   a set of strings. The same holds true for number sets and binary sets.
--   This action is only valid for an existing attribute whose data type is
--   number or is a set. Do not use <tt>ADD</tt> for any other data types.
--   <b>If no item with the specified <i>Key</i> is found:</b> *
--   <tt>PUT</tt> - DynamoDB creates a new item with the specified primary
--   key, and then adds the attribute. * <tt>DELETE</tt> - Nothing happens;
--   there is no attribute to delete. * <tt>ADD</tt> - DynamoDB creates an
--   item with the supplied primary key and number (or set of numbers) for
--   the attribute value. The only data types allowed are number and number
--   set; no other data types can be specified.</li>
--   </ul>
attributeValueUpdate :: AttributeValueUpdate

-- | Undocumented member.
avuValue :: Lens' AttributeValueUpdate (Maybe AttributeValue)

-- | Specifies how to perform the update. Valid values are <tt>PUT</tt>
--   (default), <tt>DELETE</tt> , and <tt>ADD</tt> . The behavior depends
--   on whether the specified primary key already exists in the table.
--   <b>If an item with the specified <i>Key</i> is found in the table:</b>
--   * <tt>PUT</tt> - Adds the specified attribute to the item. If the
--   attribute already exists, it is replaced by the new value. *
--   <tt>DELETE</tt> - If no value is specified, the attribute and its
--   value are removed from the item. The data type of the specified value
--   must match the existing value's data type. If a <i>set</i> of values
--   is specified, then those values are subtracted from the old set. For
--   example, if the attribute value was the set <tt>[a,b,c]</tt> and the
--   <i>DELETE</i> action specified <tt>[a,c]</tt> , then the final
--   attribute value would be <tt>[b]</tt> . Specifying an empty set is an
--   error. * <tt>ADD</tt> - If the attribute does not already exist, then
--   the attribute and its values are added to the item. If the attribute
--   does exist, then the behavior of <tt>ADD</tt> depends on the data type
--   of the attribute: * If the existing attribute is a number, and if
--   <i>Value</i> is also a number, then the <i>Value</i> is mathematically
--   added to the existing attribute. If <i>Value</i> is a negative number,
--   then it is subtracted from the existing attribute. * If the existing
--   data type is a set, and if the <i>Value</i> is also a set, then the
--   <i>Value</i> is added to the existing set. (This is a <i>set</i>
--   operation, not mathematical addition.) For example, if the attribute
--   value was the set <tt>[1,2]</tt> , and the <tt>ADD</tt> action
--   specified <tt>[3]</tt> , then the final attribute value would be
--   <tt>[1,2,3]</tt> . An error occurs if an Add action is specified for a
--   set attribute and the attribute type specified does not match the
--   existing set type. Both sets must have the same primitive data type.
--   For example, if the existing data type is a set of strings, the
--   <i>Value</i> must also be a set of strings. The same holds true for
--   number sets and binary sets. This action is only valid for an existing
--   attribute whose data type is number or is a set. Do not use
--   <tt>ADD</tt> for any other data types. <b>If no item with the
--   specified <i>Key</i> is found:</b> * <tt>PUT</tt> - DynamoDB creates a
--   new item with the specified primary key, and then adds the attribute.
--   * <tt>DELETE</tt> - Nothing happens; there is no attribute to delete.
--   * <tt>ADD</tt> - DynamoDB creates an item with the supplied primary
--   key and number (or set of numbers) for the attribute value. The only
--   data types allowed are number and number set; no other data types can
--   be specified.
avuAction :: Lens' AttributeValueUpdate (Maybe AttributeAction)

-- | Represents the amount of provisioned throughput capacity consumed on a
--   table or an index.
--   
--   <i>See:</i> <a>capacity</a> smart constructor.
data Capacity

-- | Creates a value of <a>Capacity</a> with the minimum fields required to
--   make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>cCapacityUnits</a> - The total number of capacity units
--   consumed on a table or an index.</li>
--   </ul>
capacity :: Capacity

-- | The total number of capacity units consumed on a table or an index.
cCapacityUnits :: Lens' Capacity (Maybe Double)

-- | Represents the selection criteria for a <i>Query</i> or <i>Scan</i>
--   operation:
--   
--   <ul>
--   <li>For a <i>Query</i> operation, <i>Condition</i> is used for
--   specifying the <i>KeyConditions</i> to use when querying a table or an
--   index. For <i>KeyConditions</i> , only the following comparison
--   operators are supported:</li>
--   </ul>
--   
--   <pre>
--   EQ | LE | LT | GE | GT | BEGINS_WITH | BETWEEN
--   </pre>
--   
--   <i>Condition</i> is also used in a <i>QueryFilter</i> , which
--   evaluates the query results and returns only the desired values.
--   
--   <ul>
--   <li>For a <i>Scan</i> operation, <i>Condition</i> is used in a
--   <i>ScanFilter</i> , which evaluates the scan results and returns only
--   the desired values.</li>
--   </ul>
--   
--   <i>See:</i> <a>condition</a> smart constructor.
data Condition

-- | Creates a value of <a>Condition</a> with the minimum fields required
--   to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>cAttributeValueList</a> - One or more values to evaluate
--   against the supplied attribute. The number of values in the list
--   depends on the <i>ComparisonOperator</i> being used. For type Number,
--   value comparisons are numeric. String value comparisons for greater
--   than, equals, or less than are based on ASCII character code values.
--   For example, <tt>a</tt> is greater than <tt>A</tt> , and <tt>a</tt> is
--   greater than <tt>B</tt> . For a list of code values, see
--   <a>http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters</a> .
--   For Binary, DynamoDB treats each byte of the binary data as unsigned
--   when it compares binary values.</li>
--   <li><a>cComparisonOperator</a> - A comparator for evaluating
--   attributes. For example, equals, greater than, less than, etc. The
--   following comparison operators are available: <tt>EQ | NE | LE | LT |
--   GE | GT | NOT_NULL | NULL | CONTAINS | NOT_CONTAINS | BEGINS_WITH | IN
--   | BETWEEN</tt> The following are descriptions of each comparison
--   operator. * <tt>EQ</tt> : Equal. <tt>EQ</tt> is supported for all
--   datatypes, including lists and maps. <i>AttributeValueList</i> can
--   contain only one <i>AttributeValue</i> element of type String, Number,
--   Binary, String Set, Number Set, or Binary Set. If an item contains an
--   <i>AttributeValue</i> element of a different type than the one
--   provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>NE</tt> : Not equal. <tt>NE</tt> is supported for
--   all datatypes, including lists and maps. <i>AttributeValueList</i> can
--   contain only one <i>AttributeValue</i> of type String, Number, Binary,
--   String Set, Number Set, or Binary Set. If an item contains an
--   <i>AttributeValue</i> of a different type than the one provided in the
--   request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LE</tt> : Less than or equal.
--   <i>AttributeValueList</i> can contain only one <i>AttributeValue</i>
--   element of type String, Number, or Binary (not a set type). If an item
--   contains an <i>AttributeValue</i> element of a different type than the
--   one provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LT</tt> : Less than. <i>AttributeValueList</i> can
--   contain only one <i>AttributeValue</i> of type String, Number, or
--   Binary (not a set type). If an item contains an <i>AttributeValue</i>
--   element of a different type than the one provided in the request, the
--   value does not match. For example, <tt>{<a>S</a>:"6"}</tt> does not
--   equal <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GE</tt> :
--   Greater than or equal. <i>AttributeValueList</i> can contain only one
--   <i>AttributeValue</i> element of type String, Number, or Binary (not a
--   set type). If an item contains an <i>AttributeValue</i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GT</tt> :
--   Greater than. <i>AttributeValueList</i> can contain only one
--   <i>AttributeValue</i> element of type String, Number, or Binary (not a
--   set type). If an item contains an <i>AttributeValue</i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>NOT_NULL</tt>
--   : The attribute exists. <tt>NOT_NULL</tt> is supported for all
--   datatypes, including lists and maps. * <tt>NULL</tt> : The attribute
--   does not exist. <tt>NULL</tt> is supported for all datatypes,
--   including lists and maps. * <tt>CONTAINS</tt> : Checks for a
--   subsequence, or value in a set. <i>AttributeValueList</i> can contain
--   only one <i>AttributeValue</i> element of type String, Number, or
--   Binary (not a set type). If the target attribute of the comparison is
--   of type String, then the operator checks for a substring match. If the
--   target attribute of the comparison is of type Binary, then the
--   operator looks for a subsequence of the target that matches the input.
--   If the target attribute of the comparison is a set ("<tt>SS</tt> ",
--   "<tt>NS</tt> ", or "<tt>BS</tt> "), then the operator evaluates to
--   true if it finds an exact match with any member of the set. CONTAINS
--   is supported for lists: When evaluating "<tt>a CONTAINS b</tt> ",
--   "<tt>a</tt> " can be a list; however, "<tt>b</tt> " cannot be a set, a
--   map, or a list. * <tt>NOT_CONTAINS</tt> : Checks for absence of a
--   subsequence, or absence of a value in a set. <i>AttributeValueList</i>
--   can contain only one <i>AttributeValue</i> element of type String,
--   Number, or Binary (not a set type). If the target attribute of the
--   comparison is a String, then the operator checks for the absence of a
--   substring match. If the target attribute of the comparison is Binary,
--   then the operator checks for the absence of a subsequence of the
--   target that matches the input. If the target attribute of the
--   comparison is a set ("<tt>SS</tt> ", "<tt>NS</tt> ", or "<tt>BS</tt>
--   "), then the operator evaluates to true if it <i>does not</i> find an
--   exact match with any member of the set. NOT_CONTAINS is supported for
--   lists: When evaluating "<tt>a NOT CONTAINS b</tt> ", "<tt>a</tt> " can
--   be a list; however, "<tt>b</tt> " cannot be a set, a map, or a list. *
--   <tt>BEGINS_WITH</tt> : Checks for a prefix. <i>AttributeValueList</i>
--   can contain only one <i>AttributeValue</i> of type String or Binary
--   (not a Number or a set type). The target attribute of the comparison
--   must be of type String or Binary (not a Number or a set type). *
--   <tt>IN</tt> : Checks for matching elements within two sets.
--   <i>AttributeValueList</i> can contain one or more
--   <i>AttributeValue</i> elements of type String, Number, or Binary (not
--   a set type). These attributes are compared against an existing set
--   type attribute of an item. If any elements of the input set are
--   present in the item attribute, the expression evaluates to true. *
--   <tt>BETWEEN</tt> : Greater than or equal to the first value, and less
--   than or equal to the second value. <i>AttributeValueList</i> must
--   contain two <i>AttributeValue</i> elements of the same type, either
--   String, Number, or Binary (not a set type). A target attribute matches
--   if the target value is greater than, or equal to, the first element
--   and less than, or equal to, the second element. If an item contains an
--   <i>AttributeValue</i> element of a different type than the one
--   provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not compare to <tt>{<a>N</a>:"6"}</tt> .
--   Also, <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6",
--   "2", "1"]}</tt> For usage examples of <i>AttributeValueList</i> and
--   <i>ComparisonOperator</i> , see <a>Legacy Conditional Parameters</a>
--   in the <i>Amazon DynamoDB Developer Guide</i> .</li>
--   </ul>
condition :: ComparisonOperator -> Condition

-- | One or more values to evaluate against the supplied attribute. The
--   number of values in the list depends on the <i>ComparisonOperator</i>
--   being used. For type Number, value comparisons are numeric. String
--   value comparisons for greater than, equals, or less than are based on
--   ASCII character code values. For example, <tt>a</tt> is greater than
--   <tt>A</tt> , and <tt>a</tt> is greater than <tt>B</tt> . For a list of
--   code values, see
--   <a>http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters</a> .
--   For Binary, DynamoDB treats each byte of the binary data as unsigned
--   when it compares binary values.
cAttributeValueList :: Lens' Condition [AttributeValue]

-- | A comparator for evaluating attributes. For example, equals, greater
--   than, less than, etc. The following comparison operators are
--   available: <tt>EQ | NE | LE | LT | GE | GT | NOT_NULL | NULL |
--   CONTAINS | NOT_CONTAINS | BEGINS_WITH | IN | BETWEEN</tt> The
--   following are descriptions of each comparison operator. * <tt>EQ</tt>
--   : Equal. <tt>EQ</tt> is supported for all datatypes, including lists
--   and maps. <i>AttributeValueList</i> can contain only one
--   <i>AttributeValue</i> element of type String, Number, Binary, String
--   Set, Number Set, or Binary Set. If an item contains an
--   <i>AttributeValue</i> element of a different type than the one
--   provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>NE</tt> : Not equal. <tt>NE</tt> is supported for
--   all datatypes, including lists and maps. <i>AttributeValueList</i> can
--   contain only one <i>AttributeValue</i> of type String, Number, Binary,
--   String Set, Number Set, or Binary Set. If an item contains an
--   <i>AttributeValue</i> of a different type than the one provided in the
--   request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LE</tt> : Less than or equal.
--   <i>AttributeValueList</i> can contain only one <i>AttributeValue</i>
--   element of type String, Number, or Binary (not a set type). If an item
--   contains an <i>AttributeValue</i> element of a different type than the
--   one provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LT</tt> : Less than. <i>AttributeValueList</i> can
--   contain only one <i>AttributeValue</i> of type String, Number, or
--   Binary (not a set type). If an item contains an <i>AttributeValue</i>
--   element of a different type than the one provided in the request, the
--   value does not match. For example, <tt>{<a>S</a>:"6"}</tt> does not
--   equal <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GE</tt> :
--   Greater than or equal. <i>AttributeValueList</i> can contain only one
--   <i>AttributeValue</i> element of type String, Number, or Binary (not a
--   set type). If an item contains an <i>AttributeValue</i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GT</tt> :
--   Greater than. <i>AttributeValueList</i> can contain only one
--   <i>AttributeValue</i> element of type String, Number, or Binary (not a
--   set type). If an item contains an <i>AttributeValue</i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>NOT_NULL</tt>
--   : The attribute exists. <tt>NOT_NULL</tt> is supported for all
--   datatypes, including lists and maps. * <tt>NULL</tt> : The attribute
--   does not exist. <tt>NULL</tt> is supported for all datatypes,
--   including lists and maps. * <tt>CONTAINS</tt> : Checks for a
--   subsequence, or value in a set. <i>AttributeValueList</i> can contain
--   only one <i>AttributeValue</i> element of type String, Number, or
--   Binary (not a set type). If the target attribute of the comparison is
--   of type String, then the operator checks for a substring match. If the
--   target attribute of the comparison is of type Binary, then the
--   operator looks for a subsequence of the target that matches the input.
--   If the target attribute of the comparison is a set ("<tt>SS</tt> ",
--   "<tt>NS</tt> ", or "<tt>BS</tt> "), then the operator evaluates to
--   true if it finds an exact match with any member of the set. CONTAINS
--   is supported for lists: When evaluating "<tt>a CONTAINS b</tt> ",
--   "<tt>a</tt> " can be a list; however, "<tt>b</tt> " cannot be a set, a
--   map, or a list. * <tt>NOT_CONTAINS</tt> : Checks for absence of a
--   subsequence, or absence of a value in a set. <i>AttributeValueList</i>
--   can contain only one <i>AttributeValue</i> element of type String,
--   Number, or Binary (not a set type). If the target attribute of the
--   comparison is a String, then the operator checks for the absence of a
--   substring match. If the target attribute of the comparison is Binary,
--   then the operator checks for the absence of a subsequence of the
--   target that matches the input. If the target attribute of the
--   comparison is a set ("<tt>SS</tt> ", "<tt>NS</tt> ", or "<tt>BS</tt>
--   "), then the operator evaluates to true if it <i>does not</i> find an
--   exact match with any member of the set. NOT_CONTAINS is supported for
--   lists: When evaluating "<tt>a NOT CONTAINS b</tt> ", "<tt>a</tt> " can
--   be a list; however, "<tt>b</tt> " cannot be a set, a map, or a list. *
--   <tt>BEGINS_WITH</tt> : Checks for a prefix. <i>AttributeValueList</i>
--   can contain only one <i>AttributeValue</i> of type String or Binary
--   (not a Number or a set type). The target attribute of the comparison
--   must be of type String or Binary (not a Number or a set type). *
--   <tt>IN</tt> : Checks for matching elements within two sets.
--   <i>AttributeValueList</i> can contain one or more
--   <i>AttributeValue</i> elements of type String, Number, or Binary (not
--   a set type). These attributes are compared against an existing set
--   type attribute of an item. If any elements of the input set are
--   present in the item attribute, the expression evaluates to true. *
--   <tt>BETWEEN</tt> : Greater than or equal to the first value, and less
--   than or equal to the second value. <i>AttributeValueList</i> must
--   contain two <i>AttributeValue</i> elements of the same type, either
--   String, Number, or Binary (not a set type). A target attribute matches
--   if the target value is greater than, or equal to, the first element
--   and less than, or equal to, the second element. If an item contains an
--   <i>AttributeValue</i> element of a different type than the one
--   provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not compare to <tt>{<a>N</a>:"6"}</tt> .
--   Also, <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6",
--   "2", "1"]}</tt> For usage examples of <i>AttributeValueList</i> and
--   <i>ComparisonOperator</i> , see <a>Legacy Conditional Parameters</a>
--   in the <i>Amazon DynamoDB Developer Guide</i> .
cComparisonOperator :: Lens' Condition ComparisonOperator

-- | The capacity units consumed by an operation. The data returned
--   includes the total provisioned throughput consumed, along with
--   statistics for the table and any indexes involved in the operation.
--   <i>ConsumedCapacity</i> is only returned if the request asked for it.
--   For more information, see <a>Provisioned Throughput</a> in the
--   <i>Amazon DynamoDB Developer Guide</i> .
--   
--   <i>See:</i> <a>consumedCapacity</a> smart constructor.
data ConsumedCapacity

-- | Creates a value of <a>ConsumedCapacity</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>ccGlobalSecondaryIndexes</a> - The amount of throughput
--   consumed on each global index affected by the operation.</li>
--   <li><a>ccCapacityUnits</a> - The total number of capacity units
--   consumed by the operation.</li>
--   <li><a>ccLocalSecondaryIndexes</a> - The amount of throughput consumed
--   on each local index affected by the operation.</li>
--   <li><a>ccTable</a> - The amount of throughput consumed on the table
--   affected by the operation.</li>
--   <li><a>ccTableName</a> - The name of the table that was affected by
--   the operation.</li>
--   </ul>
consumedCapacity :: ConsumedCapacity

-- | The amount of throughput consumed on each global index affected by the
--   operation.
ccGlobalSecondaryIndexes :: Lens' ConsumedCapacity (HashMap Text Capacity)

-- | The total number of capacity units consumed by the operation.
ccCapacityUnits :: Lens' ConsumedCapacity (Maybe Double)

-- | The amount of throughput consumed on each local index affected by the
--   operation.
ccLocalSecondaryIndexes :: Lens' ConsumedCapacity (HashMap Text Capacity)

-- | The amount of throughput consumed on the table affected by the
--   operation.
ccTable :: Lens' ConsumedCapacity (Maybe Capacity)

-- | The name of the table that was affected by the operation.
ccTableName :: Lens' ConsumedCapacity (Maybe Text)

-- | Represents a new global secondary index to be added to an existing
--   table.
--   
--   <i>See:</i> <a>createGlobalSecondaryIndexAction</a> smart constructor.
data CreateGlobalSecondaryIndexAction

-- | Creates a value of <a>CreateGlobalSecondaryIndexAction</a> with the
--   minimum fields required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>cgsiaIndexName</a> - The name of the global secondary index to
--   be created.</li>
--   <li><a>cgsiaKeySchema</a> - The key schema for the global secondary
--   index.</li>
--   <li><a>cgsiaProjection</a> - Undocumented member.</li>
--   <li><a>cgsiaProvisionedThroughput</a> - Undocumented member.</li>
--   </ul>
createGlobalSecondaryIndexAction :: Text -> NonEmpty KeySchemaElement -> Projection -> ProvisionedThroughput -> CreateGlobalSecondaryIndexAction

-- | The name of the global secondary index to be created.
cgsiaIndexName :: Lens' CreateGlobalSecondaryIndexAction Text

-- | The key schema for the global secondary index.
cgsiaKeySchema :: Lens' CreateGlobalSecondaryIndexAction (NonEmpty KeySchemaElement)

-- | Undocumented member.
cgsiaProjection :: Lens' CreateGlobalSecondaryIndexAction Projection

-- | Undocumented member.
cgsiaProvisionedThroughput :: Lens' CreateGlobalSecondaryIndexAction ProvisionedThroughput

-- | Represents a global secondary index to be deleted from an existing
--   table.
--   
--   <i>See:</i> <a>deleteGlobalSecondaryIndexAction</a> smart constructor.
data DeleteGlobalSecondaryIndexAction

-- | Creates a value of <a>DeleteGlobalSecondaryIndexAction</a> with the
--   minimum fields required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>dgsiaIndexName</a> - The name of the global secondary index to
--   be deleted.</li>
--   </ul>
deleteGlobalSecondaryIndexAction :: Text -> DeleteGlobalSecondaryIndexAction

-- | The name of the global secondary index to be deleted.
dgsiaIndexName :: Lens' DeleteGlobalSecondaryIndexAction Text

-- | Represents a request to perform a <i>DeleteItem</i> operation on an
--   item.
--   
--   <i>See:</i> <a>deleteRequest</a> smart constructor.
data DeleteRequest

-- | Creates a value of <a>DeleteRequest</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>drKey</a> - A map of attribute name to attribute values,
--   representing the primary key of the item to delete. All of the table's
--   primary key attributes must be specified, and their data types must
--   match those of the table's key schema.</li>
--   </ul>
deleteRequest :: DeleteRequest

-- | A map of attribute name to attribute values, representing the primary
--   key of the item to delete. All of the table's primary key attributes
--   must be specified, and their data types must match those of the
--   table's key schema.
drKey :: Lens' DeleteRequest (HashMap Text AttributeValue)

-- | Represents a condition to be compared with an attribute value. This
--   condition can be used with <i>DeleteItem</i> , <i>PutItem</i> or
--   <i>UpdateItem</i> operations; if the comparison evaluates to true, the
--   operation succeeds; if not, the operation fails. You can use
--   <i>ExpectedAttributeValue</i> in one of two different ways:
--   
--   <ul>
--   <li>Use <i>AttributeValueList</i> to specify one or more values to
--   compare against an attribute. Use <i>ComparisonOperator</i> to specify
--   how you want to perform the comparison. If the comparison evaluates to
--   true, then the conditional operation succeeds.</li>
--   <li>Use <i>Value</i> to specify a value that DynamoDB will compare
--   against an attribute. If the values match, then
--   <i>ExpectedAttributeValue</i> evaluates to true and the conditional
--   operation succeeds. Optionally, you can also set <i>Exists</i> to
--   false, indicating that you <i>do not</i> expect to find the attribute
--   value in the table. In this case, the conditional operation succeeds
--   only if the comparison evaluates to false.</li>
--   </ul>
--   
--   <i>Value</i> and <i>Exists</i> are incompatible with
--   <i>AttributeValueList</i> and <i>ComparisonOperator</i> . Note that if
--   you use both sets of parameters at once, DynamoDB will return a
--   <i>ValidationException</i> exception.
--   
--   <i>See:</i> <a>expectedAttributeValue</a> smart constructor.
data ExpectedAttributeValue

-- | Creates a value of <a>ExpectedAttributeValue</a> with the minimum
--   fields required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>eavAttributeValueList</a> - One or more values to evaluate
--   against the supplied attribute. The number of values in the list
--   depends on the <i>ComparisonOperator</i> being used. For type Number,
--   value comparisons are numeric. String value comparisons for greater
--   than, equals, or less than are based on ASCII character code values.
--   For example, <tt>a</tt> is greater than <tt>A</tt> , and <tt>a</tt> is
--   greater than <tt>B</tt> . For a list of code values, see
--   <a>http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters</a> .
--   For 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 <a>JSON Data Format</a> in the <i>Amazon DynamoDB
--   Developer Guide</i> .</li>
--   <li><a>eavExists</a> - Causes DynamoDB to evaluate the value before
--   attempting a conditional operation: * If <i>Exists</i> is
--   <tt>true</tt> , DynamoDB will check to see if that attribute value
--   already exists in the table. If it is found, then the operation
--   succeeds. If it is not found, the operation fails with a
--   <i>ConditionalCheckFailedException</i> . * If <i>Exists</i> is
--   <tt>false</tt> , DynamoDB assumes that the attribute value does not
--   exist in the table. If in fact the value does not exist, then the
--   assumption is valid and the operation succeeds. If the value is found,
--   despite the assumption that it does not exist, the operation fails
--   with a <i>ConditionalCheckFailedException</i> . The default setting
--   for <i>Exists</i> is <tt>true</tt> . If you supply a <i>Value</i> all
--   by itself, DynamoDB assumes the attribute exists: You don't have to
--   set <i>Exists</i> to <tt>true</tt> , because it is implied. DynamoDB
--   returns a <i>ValidationException</i> if: * <i>Exists</i> is
--   <tt>true</tt> but there is no <i>Value</i> to check. (You expect a
--   value to exist, but don't specify what that value is.) * <i>Exists</i>
--   is <tt>false</tt> but you also provide a <i>Value</i> . (You cannot
--   expect an attribute to have a value, while also expecting it not to
--   exist.)</li>
--   <li><a>eavValue</a> - Undocumented member.</li>
--   <li><a>eavComparisonOperator</a> - A comparator for evaluating
--   attributes in the <i>AttributeValueList</i> . For example, equals,
--   greater than, less than, etc. The following comparison operators are
--   available: <tt>EQ | NE | LE | LT | GE | GT | NOT_NULL | NULL |
--   CONTAINS | NOT_CONTAINS | BEGINS_WITH | IN | BETWEEN</tt> The
--   following are descriptions of each comparison operator. * <tt>EQ</tt>
--   : Equal. <tt>EQ</tt> is supported for all datatypes, including lists
--   and maps. <i>AttributeValueList</i> can contain only one
--   <i>AttributeValue</i> element of type String, Number, Binary, String
--   Set, Number Set, or Binary Set. If an item contains an
--   <i>AttributeValue</i> element of a different type than the one
--   provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>NE</tt> : Not equal. <tt>NE</tt> is supported for
--   all datatypes, including lists and maps. <i>AttributeValueList</i> can
--   contain only one <i>AttributeValue</i> of type String, Number, Binary,
--   String Set, Number Set, or Binary Set. If an item contains an
--   <i>AttributeValue</i> of a different type than the one provided in the
--   request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LE</tt> : Less than or equal.
--   <i>AttributeValueList</i> can contain only one <i>AttributeValue</i>
--   element of type String, Number, or Binary (not a set type). If an item
--   contains an <i>AttributeValue</i> element of a different type than the
--   one provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LT</tt> : Less than. <i>AttributeValueList</i> can
--   contain only one <i>AttributeValue</i> of type String, Number, or
--   Binary (not a set type). If an item contains an <i>AttributeValue</i>
--   element of a different type than the one provided in the request, the
--   value does not match. For example, <tt>{<a>S</a>:"6"}</tt> does not
--   equal <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GE</tt> :
--   Greater than or equal. <i>AttributeValueList</i> can contain only one
--   <i>AttributeValue</i> element of type String, Number, or Binary (not a
--   set type). If an item contains an <i>AttributeValue</i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GT</tt> :
--   Greater than. <i>AttributeValueList</i> can contain only one
--   <i>AttributeValue</i> element of type String, Number, or Binary (not a
--   set type). If an item contains an <i>AttributeValue</i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>NOT_NULL</tt>
--   : The attribute exists. <tt>NOT_NULL</tt> is supported for all
--   datatypes, including lists and maps. * <tt>NULL</tt> : The attribute
--   does not exist. <tt>NULL</tt> is supported for all datatypes,
--   including lists and maps. * <tt>CONTAINS</tt> : Checks for a
--   subsequence, or value in a set. <i>AttributeValueList</i> can contain
--   only one <i>AttributeValue</i> element of type String, Number, or
--   Binary (not a set type). If the target attribute of the comparison is
--   of type String, then the operator checks for a substring match. If the
--   target attribute of the comparison is of type Binary, then the
--   operator looks for a subsequence of the target that matches the input.
--   If the target attribute of the comparison is a set ("<tt>SS</tt> ",
--   "<tt>NS</tt> ", or "<tt>BS</tt> "), then the operator evaluates to
--   true if it finds an exact match with any member of the set. CONTAINS
--   is supported for lists: When evaluating "<tt>a CONTAINS b</tt> ",
--   "<tt>a</tt> " can be a list; however, "<tt>b</tt> " cannot be a set, a
--   map, or a list. * <tt>NOT_CONTAINS</tt> : Checks for absence of a
--   subsequence, or absence of a value in a set. <i>AttributeValueList</i>
--   can contain only one <i>AttributeValue</i> element of type String,
--   Number, or Binary (not a set type). If the target attribute of the
--   comparison is a String, then the operator checks for the absence of a
--   substring match. If the target attribute of the comparison is Binary,
--   then the operator checks for the absence of a subsequence of the
--   target that matches the input. If the target attribute of the
--   comparison is a set ("<tt>SS</tt> ", "<tt>NS</tt> ", or "<tt>BS</tt>
--   "), then the operator evaluates to true if it <i>does not</i> find an
--   exact match with any member of the set. NOT_CONTAINS is supported for
--   lists: When evaluating "<tt>a NOT CONTAINS b</tt> ", "<tt>a</tt> " can
--   be a list; however, "<tt>b</tt> " cannot be a set, a map, or a list. *
--   <tt>BEGINS_WITH</tt> : Checks for a prefix. <i>AttributeValueList</i>
--   can contain only one <i>AttributeValue</i> of type String or Binary
--   (not a Number or a set type). The target attribute of the comparison
--   must be of type String or Binary (not a Number or a set type). *
--   <tt>IN</tt> : Checks for matching elements within two sets.
--   <i>AttributeValueList</i> can contain one or more
--   <i>AttributeValue</i> elements of type String, Number, or Binary (not
--   a set type). These attributes are compared against an existing set
--   type attribute of an item. If any elements of the input set are
--   present in the item attribute, the expression evaluates to true. *
--   <tt>BETWEEN</tt> : Greater than or equal to the first value, and less
--   than or equal to the second value. <i>AttributeValueList</i> must
--   contain two <i>AttributeValue</i> elements of the same type, either
--   String, Number, or Binary (not a set type). A target attribute matches
--   if the target value is greater than, or equal to, the first element
--   and less than, or equal to, the second element. If an item contains an
--   <i>AttributeValue</i> element of a different type than the one
--   provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not compare to <tt>{<a>N</a>:"6"}</tt> .
--   Also, <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6",
--   "2", "1"]}</tt></li>
--   </ul>
expectedAttributeValue :: ExpectedAttributeValue

-- | One or more values to evaluate against the supplied attribute. The
--   number of values in the list depends on the <i>ComparisonOperator</i>
--   being used. For type Number, value comparisons are numeric. String
--   value comparisons for greater than, equals, or less than are based on
--   ASCII character code values. For example, <tt>a</tt> is greater than
--   <tt>A</tt> , and <tt>a</tt> is greater than <tt>B</tt> . For a list of
--   code values, see
--   <a>http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters</a> .
--   For 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 <a>JSON Data Format</a> in the <i>Amazon DynamoDB
--   Developer Guide</i> .
eavAttributeValueList :: Lens' ExpectedAttributeValue [AttributeValue]

-- | Causes DynamoDB to evaluate the value before attempting a conditional
--   operation: * If <i>Exists</i> is <tt>true</tt> , DynamoDB will check
--   to see if that attribute value already exists in the table. If it is
--   found, then the operation succeeds. If it is not found, the operation
--   fails with a <i>ConditionalCheckFailedException</i> . * If
--   <i>Exists</i> is <tt>false</tt> , DynamoDB assumes that the attribute
--   value does not exist in the table. If in fact the value does not
--   exist, then the assumption is valid and the operation succeeds. If the
--   value is found, despite the assumption that it does not exist, the
--   operation fails with a <i>ConditionalCheckFailedException</i> . The
--   default setting for <i>Exists</i> is <tt>true</tt> . If you supply a
--   <i>Value</i> all by itself, DynamoDB assumes the attribute exists: You
--   don't have to set <i>Exists</i> to <tt>true</tt> , because it is
--   implied. DynamoDB returns a <i>ValidationException</i> if: *
--   <i>Exists</i> is <tt>true</tt> but there is no <i>Value</i> to check.
--   (You expect a value to exist, but don't specify what that value is.) *
--   <i>Exists</i> is <tt>false</tt> but you also provide a <i>Value</i> .
--   (You cannot expect an attribute to have a value, while also expecting
--   it not to exist.)
eavExists :: Lens' ExpectedAttributeValue (Maybe Bool)

-- | Undocumented member.
eavValue :: Lens' ExpectedAttributeValue (Maybe AttributeValue)

-- | A comparator for evaluating attributes in the
--   <i>AttributeValueList</i> . For example, equals, greater than, less
--   than, etc. The following comparison operators are available: <tt>EQ |
--   NE | LE | LT | GE | GT | NOT_NULL | NULL | CONTAINS | NOT_CONTAINS |
--   BEGINS_WITH | IN | BETWEEN</tt> The following are descriptions of each
--   comparison operator. * <tt>EQ</tt> : Equal. <tt>EQ</tt> is supported
--   for all datatypes, including lists and maps. <i>AttributeValueList</i>
--   can contain only one <i>AttributeValue</i> element of type String,
--   Number, Binary, String Set, Number Set, or Binary Set. If an item
--   contains an <i>AttributeValue</i> element of a different type than the
--   one provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>NE</tt> : Not equal. <tt>NE</tt> is supported for
--   all datatypes, including lists and maps. <i>AttributeValueList</i> can
--   contain only one <i>AttributeValue</i> of type String, Number, Binary,
--   String Set, Number Set, or Binary Set. If an item contains an
--   <i>AttributeValue</i> of a different type than the one provided in the
--   request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not equal <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LE</tt> : Less than or equal.
--   <i>AttributeValueList</i> can contain only one <i>AttributeValue</i>
--   element of type String, Number, or Binary (not a set type). If an item
--   contains an <i>AttributeValue</i> element of a different type than the
--   one provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not equal <tt>{<a>N</a>:"6"}</tt> . Also,
--   <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6", "2",
--   "1"]}</tt> . * <tt>LT</tt> : Less than. <i>AttributeValueList</i> can
--   contain only one <i>AttributeValue</i> of type String, Number, or
--   Binary (not a set type). If an item contains an <i>AttributeValue</i>
--   element of a different type than the one provided in the request, the
--   value does not match. For example, <tt>{<a>S</a>:"6"}</tt> does not
--   equal <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GE</tt> :
--   Greater than or equal. <i>AttributeValueList</i> can contain only one
--   <i>AttributeValue</i> element of type String, Number, or Binary (not a
--   set type). If an item contains an <i>AttributeValue</i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>GT</tt> :
--   Greater than. <i>AttributeValueList</i> can contain only one
--   <i>AttributeValue</i> element of type String, Number, or Binary (not a
--   set type). If an item contains an <i>AttributeValue</i> element of a
--   different type than the one provided in the request, the value does
--   not match. For example, <tt>{<a>S</a>:"6"}</tt> does not equal
--   <tt>{<a>N</a>:"6"}</tt> . Also, <tt>{<a>N</a>:"6"}</tt> does not
--   compare to <tt>{<a>NS</a>:["6", "2", "1"]}</tt> . * <tt>NOT_NULL</tt>
--   : The attribute exists. <tt>NOT_NULL</tt> is supported for all
--   datatypes, including lists and maps. * <tt>NULL</tt> : The attribute
--   does not exist. <tt>NULL</tt> is supported for all datatypes,
--   including lists and maps. * <tt>CONTAINS</tt> : Checks for a
--   subsequence, or value in a set. <i>AttributeValueList</i> can contain
--   only one <i>AttributeValue</i> element of type String, Number, or
--   Binary (not a set type). If the target attribute of the comparison is
--   of type String, then the operator checks for a substring match. If the
--   target attribute of the comparison is of type Binary, then the
--   operator looks for a subsequence of the target that matches the input.
--   If the target attribute of the comparison is a set ("<tt>SS</tt> ",
--   "<tt>NS</tt> ", or "<tt>BS</tt> "), then the operator evaluates to
--   true if it finds an exact match with any member of the set. CONTAINS
--   is supported for lists: When evaluating "<tt>a CONTAINS b</tt> ",
--   "<tt>a</tt> " can be a list; however, "<tt>b</tt> " cannot be a set, a
--   map, or a list. * <tt>NOT_CONTAINS</tt> : Checks for absence of a
--   subsequence, or absence of a value in a set. <i>AttributeValueList</i>
--   can contain only one <i>AttributeValue</i> element of type String,
--   Number, or Binary (not a set type). If the target attribute of the
--   comparison is a String, then the operator checks for the absence of a
--   substring match. If the target attribute of the comparison is Binary,
--   then the operator checks for the absence of a subsequence of the
--   target that matches the input. If the target attribute of the
--   comparison is a set ("<tt>SS</tt> ", "<tt>NS</tt> ", or "<tt>BS</tt>
--   "), then the operator evaluates to true if it <i>does not</i> find an
--   exact match with any member of the set. NOT_CONTAINS is supported for
--   lists: When evaluating "<tt>a NOT CONTAINS b</tt> ", "<tt>a</tt> " can
--   be a list; however, "<tt>b</tt> " cannot be a set, a map, or a list. *
--   <tt>BEGINS_WITH</tt> : Checks for a prefix. <i>AttributeValueList</i>
--   can contain only one <i>AttributeValue</i> of type String or Binary
--   (not a Number or a set type). The target attribute of the comparison
--   must be of type String or Binary (not a Number or a set type). *
--   <tt>IN</tt> : Checks for matching elements within two sets.
--   <i>AttributeValueList</i> can contain one or more
--   <i>AttributeValue</i> elements of type String, Number, or Binary (not
--   a set type). These attributes are compared against an existing set
--   type attribute of an item. If any elements of the input set are
--   present in the item attribute, the expression evaluates to true. *
--   <tt>BETWEEN</tt> : Greater than or equal to the first value, and less
--   than or equal to the second value. <i>AttributeValueList</i> must
--   contain two <i>AttributeValue</i> elements of the same type, either
--   String, Number, or Binary (not a set type). A target attribute matches
--   if the target value is greater than, or equal to, the first element
--   and less than, or equal to, the second element. If an item contains an
--   <i>AttributeValue</i> element of a different type than the one
--   provided in the request, the value does not match. For example,
--   <tt>{<a>S</a>:"6"}</tt> does not compare to <tt>{<a>N</a>:"6"}</tt> .
--   Also, <tt>{<a>N</a>:"6"}</tt> does not compare to <tt>{<a>NS</a>:["6",
--   "2", "1"]}</tt>
eavComparisonOperator :: Lens' ExpectedAttributeValue (Maybe ComparisonOperator)

-- | Represents the properties of a global secondary index.
--   
--   <i>See:</i> <a>globalSecondaryIndex</a> smart constructor.
data GlobalSecondaryIndex

-- | Creates a value of <a>GlobalSecondaryIndex</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>gsiIndexName</a> - The name of the global secondary index. The
--   name must be unique among all other indexes on this table.</li>
--   <li><a>gsiKeySchema</a> - The complete key schema for a global
--   secondary index, which consists of one or more pairs of attribute
--   names and key types: * <tt>HASH</tt> - partition key * <tt>RANGE</tt>
--   - sort key</li>
--   <li><a>gsiProjection</a> - Undocumented member.</li>
--   <li><a>gsiProvisionedThroughput</a> - Undocumented member.</li>
--   </ul>
globalSecondaryIndex :: Text -> NonEmpty KeySchemaElement -> Projection -> ProvisionedThroughput -> GlobalSecondaryIndex

-- | The name of the global secondary index. The name must be unique among
--   all other indexes on this table.
gsiIndexName :: Lens' GlobalSecondaryIndex Text

-- | The complete key schema for a global secondary index, which consists
--   of one or more pairs of attribute names and key types: * <tt>HASH</tt>
--   - partition key * <tt>RANGE</tt> - sort key
gsiKeySchema :: Lens' GlobalSecondaryIndex (NonEmpty KeySchemaElement)

-- | Undocumented member.
gsiProjection :: Lens' GlobalSecondaryIndex Projection

-- | Undocumented member.
gsiProvisionedThroughput :: Lens' GlobalSecondaryIndex ProvisionedThroughput

-- | Represents the properties of a global secondary index.
--   
--   <i>See:</i> <a>globalSecondaryIndexDescription</a> smart constructor.
data GlobalSecondaryIndexDescription

-- | Creates a value of <a>GlobalSecondaryIndexDescription</a> with the
--   minimum fields required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>gsidBackfilling</a> - Indicates whether the index is currently
--   backfilling. <i>Backfilling</i> is the process of reading items from
--   the table and determining whether they can be added to the index. (Not
--   all items will qualify: For example, a partition key cannot have any
--   duplicate values.) If an item can be added to the index, DynamoDB will
--   do so. After all items have been processed, the backfilling operation
--   is complete and <i>Backfilling</i> is false.</li>
--   <li><a>gsidIndexSizeBytes</a> - The total size of the specified index,
--   in bytes. DynamoDB updates this value approximately every six hours.
--   Recent changes might not be reflected in this value.</li>
--   <li><a>gsidIndexStatus</a> - The current state of the global secondary
--   index: * <i>CREATING</i> - The index is being created. *
--   <i>UPDATING</i> - The index is being updated. * <i>DELETING</i> - The
--   index is being deleted. * <i>ACTIVE</i> - The index is ready for
--   use.</li>
--   <li><a>gsidProvisionedThroughput</a> - Undocumented member.</li>
--   <li><a>gsidIndexARN</a> - The Amazon Resource Name (ARN) that uniquely
--   identifies the index.</li>
--   <li><a>gsidKeySchema</a> - The complete key schema for a global
--   secondary index, which consists of one or more pairs of attribute
--   names and key types: * <tt>HASH</tt> - partition key * <tt>RANGE</tt>
--   - sort key</li>
--   <li><a>gsidProjection</a> - Undocumented member.</li>
--   <li><a>gsidItemCount</a> - The number of items in the specified index.
--   DynamoDB updates this value approximately every six hours. Recent
--   changes might not be reflected in this value.</li>
--   <li><a>gsidIndexName</a> - The name of the global secondary
--   index.</li>
--   </ul>
globalSecondaryIndexDescription :: GlobalSecondaryIndexDescription

-- | Indicates whether the index is currently backfilling.
--   <i>Backfilling</i> is the process of reading items from the table and
--   determining whether they can be added to the index. (Not all items
--   will qualify: For example, a partition key cannot have any duplicate
--   values.) If an item can be added to the index, DynamoDB will do so.
--   After all items have been processed, the backfilling operation is
--   complete and <i>Backfilling</i> is false.
gsidBackfilling :: Lens' GlobalSecondaryIndexDescription (Maybe Bool)

-- | The total size of the specified index, in bytes. DynamoDB updates this
--   value approximately every six hours. Recent changes might not be
--   reflected in this value.
gsidIndexSizeBytes :: Lens' GlobalSecondaryIndexDescription (Maybe Integer)

-- | The current state of the global secondary index: * <i>CREATING</i> -
--   The index is being created. * <i>UPDATING</i> - The index is being
--   updated. * <i>DELETING</i> - The index is being deleted. *
--   <i>ACTIVE</i> - The index is ready for use.
gsidIndexStatus :: Lens' GlobalSecondaryIndexDescription (Maybe IndexStatus)

-- | Undocumented member.
gsidProvisionedThroughput :: Lens' GlobalSecondaryIndexDescription (Maybe ProvisionedThroughputDescription)

-- | The Amazon Resource Name (ARN) that uniquely identifies the index.
gsidIndexARN :: Lens' GlobalSecondaryIndexDescription (Maybe Text)

-- | The complete key schema for a global secondary index, which consists
--   of one or more pairs of attribute names and key types: * <tt>HASH</tt>
--   - partition key * <tt>RANGE</tt> - sort key
gsidKeySchema :: Lens' GlobalSecondaryIndexDescription (Maybe (NonEmpty KeySchemaElement))

-- | Undocumented member.
gsidProjection :: Lens' GlobalSecondaryIndexDescription (Maybe Projection)

-- | The number of items in the specified index. DynamoDB updates this
--   value approximately every six hours. Recent changes might not be
--   reflected in this value.
gsidItemCount :: Lens' GlobalSecondaryIndexDescription (Maybe Integer)

-- | The name of the global secondary index.
gsidIndexName :: Lens' GlobalSecondaryIndexDescription (Maybe Text)

-- | Represents one of the following:
--   
--   <ul>
--   <li>A new global secondary index to be added to an existing
--   table.</li>
--   <li>New provisioned throughput parameters for an existing global
--   secondary index.</li>
--   <li>An existing global secondary index to be removed from an existing
--   table.</li>
--   </ul>
--   
--   <i>See:</i> <a>globalSecondaryIndexUpdate</a> smart constructor.
data GlobalSecondaryIndexUpdate

-- | Creates a value of <a>GlobalSecondaryIndexUpdate</a> with the minimum
--   fields required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>gsiuCreate</a> - The parameters required for creating a global
--   secondary index on an existing table: * <tt>IndexName </tt> *
--   <tt>KeySchema </tt> * <tt>AttributeDefinitions </tt> * <tt>Projection
--   </tt> * <tt>ProvisionedThroughput </tt></li>
--   <li><a>gsiuDelete</a> - The name of an existing global secondary index
--   to be removed.</li>
--   <li><a>gsiuUpdate</a> - The name of an existing global secondary
--   index, along with new provisioned throughput settings to be applied to
--   that index.</li>
--   </ul>
globalSecondaryIndexUpdate :: GlobalSecondaryIndexUpdate

-- | The parameters required for creating a global secondary index on an
--   existing table: * <tt>IndexName </tt> * <tt>KeySchema </tt> *
--   <tt>AttributeDefinitions </tt> * <tt>Projection </tt> *
--   <tt>ProvisionedThroughput </tt>
gsiuCreate :: Lens' GlobalSecondaryIndexUpdate (Maybe CreateGlobalSecondaryIndexAction)

-- | The name of an existing global secondary index to be removed.
gsiuDelete :: Lens' GlobalSecondaryIndexUpdate (Maybe DeleteGlobalSecondaryIndexAction)

-- | The name of an existing global secondary index, along with new
--   provisioned throughput settings to be applied to that index.
gsiuUpdate :: Lens' GlobalSecondaryIndexUpdate (Maybe UpdateGlobalSecondaryIndexAction)

-- | Information about item collections, if any, that were affected by the
--   operation. <i>ItemCollectionMetrics</i> is only returned if the
--   request asked for it. If the table does not have any local secondary
--   indexes, this information is not returned in the response.
--   
--   <i>See:</i> <a>itemCollectionMetrics</a> smart constructor.
data ItemCollectionMetrics

-- | Creates a value of <a>ItemCollectionMetrics</a> with the minimum
--   fields required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>icmItemCollectionKey</a> - The partition key value of the item
--   collection. This value is the same as the partition key value of the
--   item.</li>
--   <li><a>icmSizeEstimateRangeGB</a> - An estimate of item collection
--   size, in gigabytes. This value is a two-element array containing a
--   lower bound and an upper bound for the estimate. The estimate includes
--   the size of all the items in the table, plus the size of all
--   attributes projected into all of the local secondary indexes on that
--   table. Use this estimate to measure whether a local secondary index is
--   approaching its size limit. The estimate is subject to change over
--   time; therefore, do not rely on the precision or accuracy of the
--   estimate.</li>
--   </ul>
itemCollectionMetrics :: ItemCollectionMetrics

-- | The partition key value of the item collection. This value is the same
--   as the partition key value of the item.
icmItemCollectionKey :: Lens' ItemCollectionMetrics (HashMap Text AttributeValue)

-- | An estimate of item collection size, in gigabytes. This value is a
--   two-element array containing a lower bound and an upper bound for the
--   estimate. The estimate includes the size of all the items in the
--   table, plus the size of all attributes projected into all of the local
--   secondary indexes on that table. Use this estimate to measure whether
--   a local secondary index is approaching its size limit. The estimate is
--   subject to change over time; therefore, do not rely on the precision
--   or accuracy of the estimate.
icmSizeEstimateRangeGB :: Lens' ItemCollectionMetrics [Double]

-- | Represents <i>a single element</i> of a key schema. A key schema
--   specifies the attributes that make up the primary key of a table, or
--   the key attributes of an index.
--   
--   A <i>KeySchemaElement</i> represents exactly one attribute of the
--   primary key. For example, a simple primary key would be represented by
--   one <i>KeySchemaElement</i> (for the partition key). A composite
--   primary key would require one <i>KeySchemaElement</i> for the
--   partition key, and another <i>KeySchemaElement</i> for the sort key.
--   
--   A <i>KeySchemaElement</i> must be a scalar, top-level attribute (not a
--   nested attribute). The data type must be one of String, Number, or
--   Binary. The attribute cannot be nested within a List or a Map.
--   
--   <i>See:</i> <a>keySchemaElement</a> smart constructor.
data KeySchemaElement

-- | Creates a value of <a>KeySchemaElement</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>kseAttributeName</a> - The name of a key attribute.</li>
--   <li><a>kseKeyType</a> - The role that this key attribute will assume:
--   * <tt>HASH</tt> - partition key * <tt>RANGE</tt> - sort key</li>
--   </ul>
keySchemaElement :: Text -> KeyType -> KeySchemaElement

-- | The name of a key attribute.
kseAttributeName :: Lens' KeySchemaElement Text

-- | The role that this key attribute will assume: * <tt>HASH</tt> -
--   partition key * <tt>RANGE</tt> - sort key
kseKeyType :: Lens' KeySchemaElement KeyType

-- | Represents a set of primary keys and, for each key, the attributes to
--   retrieve from the table.
--   
--   For each primary key, you must provide <i>all</i> of the key
--   attributes. For example, with a simple primary key, you only need to
--   provide the partition key. For a composite primary key, you must
--   provide <i>both</i> the partition key and the sort key.
--   
--   <i>See:</i> <a>keysAndAttributes</a> smart constructor.
data KeysAndAttributes

-- | Creates a value of <a>KeysAndAttributes</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>kaaProjectionExpression</a> - A string that identifies one or
--   more attributes to retrieve from the table. These attributes can
--   include scalars, sets, or elements of a JSON document. The attributes
--   in the <i>ProjectionExpression</i> must be separated by commas. If no
--   attribute names are specified, then all attributes will be returned.
--   If any of the requested attributes are not found, they will not appear
--   in the result. For more information, see <a>Accessing Item
--   Attributes</a> in the <i>Amazon DynamoDB Developer Guide</i> .</li>
--   <li><a>kaaAttributesToGet</a> - One or more attributes to retrieve
--   from the table or index. If no attribute names are specified then all
--   attributes will be returned. If any of the specified attributes are
--   not found, they will not appear in the result.</li>
--   <li><a>kaaExpressionAttributeNames</a> - One or more substitution
--   tokens for attribute names in an expression. The following are some
--   use cases for using <i>ExpressionAttributeNames</i> : * To access an
--   attribute whose name conflicts with a DynamoDB reserved word. * To
--   create a placeholder for repeating occurrences of an attribute name in
--   an expression. * To prevent special characters in an attribute name
--   from being misinterpreted in an expression. Use the <b>#</b> character
--   in an expression to dereference an attribute name. For example,
--   consider the following attribute name: * <tt>Percentile</tt> The name
--   of this attribute conflicts with a reserved word, so it cannot be used
--   directly in an expression. (For the complete list of reserved words,
--   see <a>Reserved Words</a> in the <i>Amazon DynamoDB Developer
--   Guide</i> ). To work around this, you could specify the following for
--   <i>ExpressionAttributeNames</i> : * <tt>{"#P":<a>Percentile</a>}</tt>
--   You could then use this substitution in an expression, as in this
--   example: * <tt>#P = :val</tt> For more information on expression
--   attribute names, see <a>Accessing Item Attributes</a> in the <i>Amazon
--   DynamoDB Developer Guide</i> .</li>
--   <li><a>kaaConsistentRead</a> - The consistency of a read operation. If
--   set to <tt>true</tt> , then a strongly consistent read is used;
--   otherwise, an eventually consistent read is used.</li>
--   <li><a>kaaKeys</a> - The primary key attribute values that define the
--   items and the attributes associated with the items.</li>
--   </ul>
keysAndAttributes :: NonEmpty (HashMap Text AttributeValue) -> KeysAndAttributes

-- | A string that identifies one or more attributes to retrieve from the
--   table. These attributes can include scalars, sets, or elements of a
--   JSON document. The attributes in the <i>ProjectionExpression</i> must
--   be separated by commas. If no attribute names are specified, then all
--   attributes will be returned. If any of the requested attributes are
--   not found, they will not appear in the result. For more information,
--   see <a>Accessing Item Attributes</a> in the <i>Amazon DynamoDB
--   Developer Guide</i> .
kaaProjectionExpression :: Lens' KeysAndAttributes (Maybe Text)

-- | One or more attributes to retrieve from the table or index. If no
--   attribute names are specified then all attributes will be returned. If
--   any of the specified attributes are not found, they will not appear in
--   the result.
kaaAttributesToGet :: Lens' KeysAndAttributes (Maybe (NonEmpty Text))

-- | One or more substitution tokens for attribute names in an expression.
--   The following are some use cases for using
--   <i>ExpressionAttributeNames</i> : * To access an attribute whose name
--   conflicts with a DynamoDB reserved word. * To create a placeholder for
--   repeating occurrences of an attribute name in an expression. * To
--   prevent special characters in an attribute name from being
--   misinterpreted in an expression. Use the <b>#</b> character in an
--   expression to dereference an attribute name. For example, consider the
--   following attribute name: * <tt>Percentile</tt> The name of this
--   attribute conflicts with a reserved word, so it cannot be used
--   directly in an expression. (For the complete list of reserved words,
--   see <a>Reserved Words</a> in the <i>Amazon DynamoDB Developer
--   Guide</i> ). To work around this, you could specify the following for
--   <i>ExpressionAttributeNames</i> : * <tt>{"#P":<a>Percentile</a>}</tt>
--   You could then use this substitution in an expression, as in this
--   example: * <tt>#P = :val</tt> For more information on expression
--   attribute names, see <a>Accessing Item Attributes</a> in the <i>Amazon
--   DynamoDB Developer Guide</i> .
kaaExpressionAttributeNames :: Lens' KeysAndAttributes (HashMap Text Text)

-- | The consistency of a read operation. If set to <tt>true</tt> , then a
--   strongly consistent read is used; otherwise, an eventually consistent
--   read is used.
kaaConsistentRead :: Lens' KeysAndAttributes (Maybe Bool)

-- | The primary key attribute values that define the items and the
--   attributes associated with the items.
kaaKeys :: Lens' KeysAndAttributes (NonEmpty (HashMap Text AttributeValue))

-- | Represents the properties of a local secondary index.
--   
--   <i>See:</i> <a>localSecondaryIndex</a> smart constructor.
data LocalSecondaryIndex

-- | Creates a value of <a>LocalSecondaryIndex</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>lsiIndexName</a> - The name of the local secondary index. The
--   name must be unique among all other indexes on this table.</li>
--   <li><a>lsiKeySchema</a> - The complete key schema for the local
--   secondary index, consisting of one or more pairs of attribute names
--   and key types: * <tt>HASH</tt> - partition key * <tt>RANGE</tt> - sort
--   key</li>
--   <li><a>lsiProjection</a> - Undocumented member.</li>
--   </ul>
localSecondaryIndex :: Text -> NonEmpty KeySchemaElement -> Projection -> LocalSecondaryIndex

-- | The name of the local secondary index. The name must be unique among
--   all other indexes on this table.
lsiIndexName :: Lens' LocalSecondaryIndex Text

-- | The complete key schema for the local secondary index, consisting of
--   one or more pairs of attribute names and key types: * <tt>HASH</tt> -
--   partition key * <tt>RANGE</tt> - sort key
lsiKeySchema :: Lens' LocalSecondaryIndex (NonEmpty KeySchemaElement)

-- | Undocumented member.
lsiProjection :: Lens' LocalSecondaryIndex Projection

-- | Represents the properties of a local secondary index.
--   
--   <i>See:</i> <a>localSecondaryIndexDescription</a> smart constructor.
data LocalSecondaryIndexDescription

-- | Creates a value of <a>LocalSecondaryIndexDescription</a> with the
--   minimum fields required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>lsidIndexSizeBytes</a> - The total size of the specified index,
--   in bytes. DynamoDB updates this value approximately every six hours.
--   Recent changes might not be reflected in this value.</li>
--   <li><a>lsidIndexARN</a> - The Amazon Resource Name (ARN) that uniquely
--   identifies the index.</li>
--   <li><a>lsidKeySchema</a> - The complete key schema for the local
--   secondary index, consisting of one or more pairs of attribute names
--   and key types: * <tt>HASH</tt> - partition key * <tt>RANGE</tt> - sort
--   key</li>
--   <li><a>lsidProjection</a> - Undocumented member.</li>
--   <li><a>lsidItemCount</a> - The number of items in the specified index.
--   DynamoDB updates this value approximately every six hours. Recent
--   changes might not be reflected in this value.</li>
--   <li><a>lsidIndexName</a> - Represents the name of the local secondary
--   index.</li>
--   </ul>
localSecondaryIndexDescription :: LocalSecondaryIndexDescription

-- | The total size of the specified index, in bytes. DynamoDB updates this
--   value approximately every six hours. Recent changes might not be
--   reflected in this value.
lsidIndexSizeBytes :: Lens' LocalSecondaryIndexDescription (Maybe Integer)

-- | The Amazon Resource Name (ARN) that uniquely identifies the index.
lsidIndexARN :: Lens' LocalSecondaryIndexDescription (Maybe Text)

-- | The complete key schema for the local secondary index, consisting of
--   one or more pairs of attribute names and key types: * <tt>HASH</tt> -
--   partition key * <tt>RANGE</tt> - sort key
lsidKeySchema :: Lens' LocalSecondaryIndexDescription (Maybe (NonEmpty KeySchemaElement))

-- | Undocumented member.
lsidProjection :: Lens' LocalSecondaryIndexDescription (Maybe Projection)

-- | The number of items in the specified index. DynamoDB updates this
--   value approximately every six hours. Recent changes might not be
--   reflected in this value.
lsidItemCount :: Lens' LocalSecondaryIndexDescription (Maybe Integer)

-- | Represents the name of the local secondary index.
lsidIndexName :: Lens' LocalSecondaryIndexDescription (Maybe Text)

-- | Represents attributes that are copied (projected) from the table into
--   an index. These are in addition to the primary key attributes and
--   index key attributes, which are automatically projected.
--   
--   <i>See:</i> <a>projection</a> smart constructor.
data Projection

-- | Creates a value of <a>Projection</a> with the minimum fields required
--   to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>pProjectionType</a> - The set of attributes that are projected
--   into the index: * <tt>KEYS_ONLY</tt> - Only the index and primary keys
--   are projected into the index. * <tt>INCLUDE</tt> - Only the specified
--   table attributes are projected into the index. The list of projected
--   attributes are in <i>NonKeyAttributes</i> . * <tt>ALL</tt> - All of
--   the table attributes are projected into the index.</li>
--   <li><a>pNonKeyAttributes</a> - Represents the non-key attribute names
--   which will be projected into the index. For local secondary indexes,
--   the total count of <i>NonKeyAttributes</i> summed across all of the
--   local secondary indexes, must not exceed 20. If you project the same
--   attribute into two different indexes, this counts as two distinct
--   attributes when determining the total.</li>
--   </ul>
projection :: Projection

-- | The set of attributes that are projected into the index: *
--   <tt>KEYS_ONLY</tt> - Only the index and primary keys are projected
--   into the index. * <tt>INCLUDE</tt> - Only the specified table
--   attributes are projected into the index. The list of projected
--   attributes are in <i>NonKeyAttributes</i> . * <tt>ALL</tt> - All of
--   the table attributes are projected into the index.
pProjectionType :: Lens' Projection (Maybe ProjectionType)

-- | Represents the non-key attribute names which will be projected into
--   the index. For local secondary indexes, the total count of
--   <i>NonKeyAttributes</i> summed across all of the local secondary
--   indexes, must not exceed 20. If you project the same attribute into
--   two different indexes, this counts as two distinct attributes when
--   determining the total.
pNonKeyAttributes :: Lens' Projection (Maybe (NonEmpty Text))

-- | Represents the provisioned throughput settings for a specified table
--   or index. The settings can be modified using the <i>UpdateTable</i>
--   operation.
--   
--   For current minimum and maximum provisioned throughput values, see
--   <a>Limits</a> in the <i>Amazon DynamoDB Developer Guide</i> .
--   
--   <i>See:</i> <a>provisionedThroughput</a> smart constructor.
data ProvisionedThroughput

-- | Creates a value of <a>ProvisionedThroughput</a> with the minimum
--   fields required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>ptReadCapacityUnits</a> - The maximum number of strongly
--   consistent reads consumed per second before DynamoDB returns a
--   <i>ThrottlingException</i> . For more information, see <a>Specifying
--   Read and Write Requirements</a> in the <i>Amazon DynamoDB Developer
--   Guide</i> .</li>
--   <li><a>ptWriteCapacityUnits</a> - The maximum number of writes
--   consumed per second before DynamoDB returns a
--   <i>ThrottlingException</i> . For more information, see <a>Specifying
--   Read and Write Requirements</a> in the <i>Amazon DynamoDB Developer
--   Guide</i> .</li>
--   </ul>
provisionedThroughput :: Natural -> Natural -> ProvisionedThroughput

-- | The maximum number of strongly consistent reads consumed per second
--   before DynamoDB returns a <i>ThrottlingException</i> . For more
--   information, see <a>Specifying Read and Write Requirements</a> in the
--   <i>Amazon DynamoDB Developer Guide</i> .
ptReadCapacityUnits :: Lens' ProvisionedThroughput Natural

-- | The maximum number of writes consumed per second before DynamoDB
--   returns a <i>ThrottlingException</i> . For more information, see
--   <a>Specifying Read and Write Requirements</a> in the <i>Amazon
--   DynamoDB Developer Guide</i> .
ptWriteCapacityUnits :: Lens' ProvisionedThroughput Natural

-- | Represents the provisioned throughput settings for the table,
--   consisting of read and write capacity units, along with data about
--   increases and decreases.
--   
--   <i>See:</i> <a>provisionedThroughputDescription</a> smart constructor.
data ProvisionedThroughputDescription

-- | Creates a value of <a>ProvisionedThroughputDescription</a> with the
--   minimum fields required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>ptdReadCapacityUnits</a> - The maximum number of strongly
--   consistent reads consumed per second before DynamoDB returns a
--   <i>ThrottlingException</i> . Eventually consistent reads require less
--   effort than strongly consistent reads, so a setting of 50
--   <i>ReadCapacityUnits</i> per second provides 100 eventually consistent
--   <i>ReadCapacityUnits</i> per second.</li>
--   <li><a>ptdLastDecreaseDateTime</a> - The date and time of the last
--   provisioned throughput decrease for this table.</li>
--   <li><a>ptdWriteCapacityUnits</a> - The maximum number of writes
--   consumed per second before DynamoDB returns a
--   <i>ThrottlingException</i> .</li>
--   <li><a>ptdNumberOfDecreasesToday</a> - The number of provisioned
--   throughput decreases for this table during this UTC calendar day. For
--   current maximums on provisioned throughput decreases, see
--   <a>Limits</a> in the <i>Amazon DynamoDB Developer Guide</i> .</li>
--   <li><a>ptdLastIncreaseDateTime</a> - The date and time of the last
--   provisioned throughput increase for this table.</li>
--   </ul>
provisionedThroughputDescription :: ProvisionedThroughputDescription

-- | The maximum number of strongly consistent reads consumed per second
--   before DynamoDB returns a <i>ThrottlingException</i> . Eventually
--   consistent reads require less effort than strongly consistent reads,
--   so a setting of 50 <i>ReadCapacityUnits</i> per second provides 100
--   eventually consistent <i>ReadCapacityUnits</i> per second.
ptdReadCapacityUnits :: Lens' ProvisionedThroughputDescription (Maybe Natural)

-- | The date and time of the last provisioned throughput decrease for this
--   table.
ptdLastDecreaseDateTime :: Lens' ProvisionedThroughputDescription (Maybe UTCTime)

-- | The maximum number of writes consumed per second before DynamoDB
--   returns a <i>ThrottlingException</i> .
ptdWriteCapacityUnits :: Lens' ProvisionedThroughputDescription (Maybe Natural)

-- | The number of provisioned throughput decreases for this table during
--   this UTC calendar day. For current maximums on provisioned throughput
--   decreases, see <a>Limits</a> in the <i>Amazon DynamoDB Developer
--   Guide</i> .
ptdNumberOfDecreasesToday :: Lens' ProvisionedThroughputDescription (Maybe Natural)

-- | The date and time of the last provisioned throughput increase for this
--   table.
ptdLastIncreaseDateTime :: Lens' ProvisionedThroughputDescription (Maybe UTCTime)

-- | Represents a request to perform a <i>PutItem</i> operation on an item.
--   
--   <i>See:</i> <a>putRequest</a> smart constructor.
data PutRequest

-- | Creates a value of <a>PutRequest</a> with the minimum fields required
--   to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>prItem</a> - A map of attribute name to attribute values,
--   representing the primary key of an item to be processed by
--   <i>PutItem</i> . All of the table's primary key attributes must be
--   specified, and their data types must match those of the table's key
--   schema. If any attributes are present in the item which are part of an
--   index key schema for the table, their types must match the index key
--   schema.</li>
--   </ul>
putRequest :: PutRequest

-- | A map of attribute name to attribute values, representing the primary
--   key of an item to be processed by <i>PutItem</i> . All of the table's
--   primary key attributes must be specified, and their data types must
--   match those of the table's key schema. If any attributes are present
--   in the item which are part of an index key schema for the table, their
--   types must match the index key schema.
prItem :: Lens' PutRequest (HashMap Text AttributeValue)

-- | Represents the DynamoDB Streams configuration for a table in DynamoDB.
--   
--   <i>See:</i> <a>streamSpecification</a> smart constructor.
data StreamSpecification

-- | Creates a value of <a>StreamSpecification</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>ssStreamViewType</a> - The DynamoDB Streams settings for the
--   table. These settings consist of: * <i>StreamEnabled</i> - Indicates
--   whether DynamoDB Streams is enabled (true) or disabled (false) on the
--   table. * <i>StreamViewType</i> - When an item in the table is
--   modified, <i>StreamViewType</i> determines what information is written
--   to the stream for this table. Valid values for <i>StreamViewType</i>
--   are: * <i>KEYS_ONLY</i> - Only the key attributes of the modified item
--   are written to the stream. * <i>NEW_IMAGE</i> - The entire item, as it
--   appears after it was modified, is written to the stream. *
--   <i>OLD_IMAGE</i> - The entire item, as it appeared before it was
--   modified, is written to the stream. * <i>NEW_AND_OLD_IMAGES</i> - Both
--   the new and the old item images of the item are written to the
--   stream.</li>
--   <li><a>ssStreamEnabled</a> - Indicates whether DynamoDB Streams is
--   enabled (true) or disabled (false) on the table.</li>
--   </ul>
streamSpecification :: StreamSpecification

-- | The DynamoDB Streams settings for the table. These settings consist
--   of: * <i>StreamEnabled</i> - Indicates whether DynamoDB Streams is
--   enabled (true) or disabled (false) on the table. *
--   <i>StreamViewType</i> - When an item in the table is modified,
--   <i>StreamViewType</i> determines what information is written to the
--   stream for this table. Valid values for <i>StreamViewType</i> are: *
--   <i>KEYS_ONLY</i> - Only the key attributes of the modified item are
--   written to the stream. * <i>NEW_IMAGE</i> - The entire item, as it
--   appears after it was modified, is written to the stream. *
--   <i>OLD_IMAGE</i> - The entire item, as it appeared before it was
--   modified, is written to the stream. * <i>NEW_AND_OLD_IMAGES</i> - Both
--   the new and the old item images of the item are written to the stream.
ssStreamViewType :: Lens' StreamSpecification (Maybe StreamViewType)

-- | Indicates whether DynamoDB Streams is enabled (true) or disabled
--   (false) on the table.
ssStreamEnabled :: Lens' StreamSpecification (Maybe Bool)

-- | Represents the properties of a table.
--   
--   <i>See:</i> <a>tableDescription</a> smart constructor.
data TableDescription

-- | Creates a value of <a>TableDescription</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>tdTableSizeBytes</a> - The total size of the specified table,
--   in bytes. DynamoDB updates this value approximately every six hours.
--   Recent changes might not be reflected in this value.</li>
--   <li><a>tdAttributeDefinitions</a> - An array of
--   <i>AttributeDefinition</i> objects. Each of these objects describes
--   one attribute in the table and index key schema. Each
--   <i>AttributeDefinition</i> object in this array is composed of: *
--   <i>AttributeName</i> - The name of the attribute. *
--   <i>AttributeType</i> - The data type for the attribute.</li>
--   <li><a>tdLatestStreamARN</a> - The Amazon Resource Name (ARN) that
--   uniquely identifies the latest stream for this table.</li>
--   <li><a>tdProvisionedThroughput</a> - The provisioned throughput
--   settings for the table, consisting of read and write capacity units,
--   along with data about increases and decreases.</li>
--   <li><a>tdTableStatus</a> - The current state of the table: *
--   <i>CREATING</i> - The table is being created. * <i>UPDATING</i> - The
--   table is being updated. * <i>DELETING</i> - The table is being
--   deleted. * <i>ACTIVE</i> - The table is ready for use.</li>
--   <li><a>tdTableARN</a> - The Amazon Resource Name (ARN) that uniquely
--   identifies the table.</li>
--   <li><a>tdKeySchema</a> - The primary key structure for the table. Each
--   <i>KeySchemaElement</i> consists of: * <i>AttributeName</i> - The name
--   of the attribute. * <i>KeyType</i> - The role of the attribute: *
--   <tt>HASH</tt> - partition key * <tt>RANGE</tt> - sort key For more
--   information about primary keys, see <a>Primary Key</a> in the
--   <i>Amazon DynamoDB Developer Guide</i> .</li>
--   <li><a>tdGlobalSecondaryIndexes</a> - The global secondary indexes, if
--   any, on the table. Each index is scoped to a given partition key
--   value. Each element is composed of: * <i>Backfilling</i> - If true,
--   then the index is currently in the backfilling phase. Backfilling
--   occurs only when a new global secondary index is added to the table;
--   it is the process by which DynamoDB populates the new index with data
--   from the table. (This attribute does not appear for indexes that were
--   created during a <i>CreateTable</i> operation.) * <i>IndexName</i> -
--   The name of the global secondary index. * <i>IndexSizeBytes</i> - The
--   total size of the global secondary index, in bytes. DynamoDB updates
--   this value approximately every six hours. Recent changes might not be
--   reflected in this value. * <i>IndexStatus</i> - The current status of
--   the global secondary index: * <i>CREATING</i> - The index is being
--   created. * <i>UPDATING</i> - The index is being updated. *
--   <i>DELETING</i> - The index is being deleted. * <i>ACTIVE</i> - The
--   index is ready for use. * <i>ItemCount</i> - The number of items in
--   the global secondary index. DynamoDB updates this value approximately
--   every six hours. Recent changes might not be reflected in this value.
--   * <i>KeySchema</i> - Specifies the complete index key schema. The
--   attribute names in the key schema must be between 1 and 255 characters
--   (inclusive). The key schema must begin with the same partition key as
--   the table. * <i>Projection</i> - Specifies attributes that are copied
--   (projected) from the table into the index. These are in addition to
--   the primary key attributes and index key attributes, which are
--   automatically projected. Each attribute specification is composed of:
--   * <i>ProjectionType</i> - One of the following: * <tt>KEYS_ONLY</tt> -
--   Only the index and primary keys are projected into the index. *
--   <tt>INCLUDE</tt> - Only the specified table attributes are projected
--   into the index. The list of projected attributes are in
--   <i>NonKeyAttributes</i> . * <tt>ALL</tt> - All of the table attributes
--   are projected into the index. * <i>NonKeyAttributes</i> - A list of
--   one or more non-key attribute names that are projected into the
--   secondary index. The total count of attributes provided in
--   <i>NonKeyAttributes</i> , summed across all of the secondary indexes,
--   must not exceed 20. If you project the same attribute into two
--   different indexes, this counts as two distinct attributes when
--   determining the total. * <i>ProvisionedThroughput</i> - The
--   provisioned throughput settings for the global secondary index,
--   consisting of read and write capacity units, along with data about
--   increases and decreases. If the table is in the <tt>DELETING</tt>
--   state, no information about indexes will be returned.</li>
--   <li><a>tdLatestStreamLabel</a> - A timestamp, in ISO 8601 format, for
--   this stream. Note that <i>LatestStreamLabel</i> is not a unique
--   identifier for the stream, because it is possible that a stream from
--   another table might have the same timestamp. However, the combination
--   of the following three elements is guaranteed to be unique: * the AWS
--   customer ID. * the table name. * the <i>StreamLabel</i> .</li>
--   <li><a>tdLocalSecondaryIndexes</a> - Represents one or more local
--   secondary indexes on the table. Each index is scoped to a given
--   partition key value. Tables with one or more local secondary indexes
--   are subject to an item collection size limit, where the amount of data
--   within a given item collection cannot exceed 10 GB. Each element is
--   composed of: * <i>IndexName</i> - The name of the local secondary
--   index. * <i>KeySchema</i> - Specifies the complete index key schema.
--   The attribute names in the key schema must be between 1 and 255
--   characters (inclusive). The key schema must begin with the same
--   partition key as the table. * <i>Projection</i> - Specifies attributes
--   that are copied (projected) from the table into the index. These are
--   in addition to the primary key attributes and index key attributes,
--   which are automatically projected. Each attribute specification is
--   composed of: * <i>ProjectionType</i> - One of the following: *
--   <tt>KEYS_ONLY</tt> - Only the index and primary keys are projected
--   into the index. * <tt>INCLUDE</tt> - Only the specified table
--   attributes are projected into the index. The list of projected
--   attributes are in <i>NonKeyAttributes</i> . * <tt>ALL</tt> - All of
--   the table attributes are projected into the index. *
--   <i>NonKeyAttributes</i> - A list of one or more non-key attribute
--   names that are projected into the secondary index. The total count of
--   attributes provided in <i>NonKeyAttributes</i> , summed across all of
--   the secondary indexes, must not exceed 20. If you project the same
--   attribute into two different indexes, this counts as two distinct
--   attributes when determining the total. * <i>IndexSizeBytes</i> -
--   Represents the total size of the index, in bytes. DynamoDB updates
--   this value approximately every six hours. Recent changes might not be
--   reflected in this value. * <i>ItemCount</i> - Represents the number of
--   items in the index. DynamoDB updates this value approximately every
--   six hours. Recent changes might not be reflected in this value. If the
--   table is in the <tt>DELETING</tt> state, no information about indexes
--   will be returned.</li>
--   <li><a>tdCreationDateTime</a> - The date and time when the table was
--   created, in <a>UNIX epoch time</a> format.</li>
--   <li><a>tdItemCount</a> - The number of items in the specified table.
--   DynamoDB updates this value approximately every six hours. Recent
--   changes might not be reflected in this value.</li>
--   <li><a>tdTableName</a> - The name of the table.</li>
--   <li><a>tdStreamSpecification</a> - The current DynamoDB Streams
--   configuration for the table.</li>
--   </ul>
tableDescription :: TableDescription

-- | The total size of the specified table, in bytes. DynamoDB updates this
--   value approximately every six hours. Recent changes might not be
--   reflected in this value.
tdTableSizeBytes :: Lens' TableDescription (Maybe Integer)

-- | An array of <i>AttributeDefinition</i> objects. Each of these objects
--   describes one attribute in the table and index key schema. Each
--   <i>AttributeDefinition</i> object in this array is composed of: *
--   <i>AttributeName</i> - The name of the attribute. *
--   <i>AttributeType</i> - The data type for the attribute.
tdAttributeDefinitions :: Lens' TableDescription [AttributeDefinition]

-- | The Amazon Resource Name (ARN) that uniquely identifies the latest
--   stream for this table.
tdLatestStreamARN :: Lens' TableDescription (Maybe Text)

-- | The provisioned throughput settings for the table, consisting of read
--   and write capacity units, along with data about increases and
--   decreases.
tdProvisionedThroughput :: Lens' TableDescription (Maybe ProvisionedThroughputDescription)

-- | The current state of the table: * <i>CREATING</i> - The table is being
--   created. * <i>UPDATING</i> - The table is being updated. *
--   <i>DELETING</i> - The table is being deleted. * <i>ACTIVE</i> - The
--   table is ready for use.
tdTableStatus :: Lens' TableDescription (Maybe TableStatus)

-- | The Amazon Resource Name (ARN) that uniquely identifies the table.
tdTableARN :: Lens' TableDescription (Maybe Text)

-- | The primary key structure for the table. Each <i>KeySchemaElement</i>
--   consists of: * <i>AttributeName</i> - The name of the attribute. *
--   <i>KeyType</i> - The role of the attribute: * <tt>HASH</tt> -
--   partition key * <tt>RANGE</tt> - sort key For more information about
--   primary keys, see <a>Primary Key</a> in the <i>Amazon DynamoDB
--   Developer Guide</i> .
tdKeySchema :: Lens' TableDescription (Maybe (NonEmpty KeySchemaElement))

-- | The global secondary indexes, if any, on the table. Each index is
--   scoped to a given partition key value. Each element is composed of: *
--   <i>Backfilling</i> - If true, then the index is currently in the
--   backfilling phase. Backfilling occurs only when a new global secondary
--   index is added to the table; it is the process by which DynamoDB
--   populates the new index with data from the table. (This attribute does
--   not appear for indexes that were created during a <i>CreateTable</i>
--   operation.) * <i>IndexName</i> - The name of the global secondary
--   index. * <i>IndexSizeBytes</i> - The total size of the global
--   secondary index, in bytes. DynamoDB updates this value approximately
--   every six hours. Recent changes might not be reflected in this value.
--   * <i>IndexStatus</i> - The current status of the global secondary
--   index: * <i>CREATING</i> - The index is being created. *
--   <i>UPDATING</i> - The index is being updated. * <i>DELETING</i> - The
--   index is being deleted. * <i>ACTIVE</i> - The index is ready for use.
--   * <i>ItemCount</i> - The number of items in the global secondary
--   index. DynamoDB updates this value approximately every six hours.
--   Recent changes might not be reflected in this value. *
--   <i>KeySchema</i> - Specifies the complete index key schema. The
--   attribute names in the key schema must be between 1 and 255 characters
--   (inclusive). The key schema must begin with the same partition key as
--   the table. * <i>Projection</i> - Specifies attributes that are copied
--   (projected) from the table into the index. These are in addition to
--   the primary key attributes and index key attributes, which are
--   automatically projected. Each attribute specification is composed of:
--   * <i>ProjectionType</i> - One of the following: * <tt>KEYS_ONLY</tt> -
--   Only the index and primary keys are projected into the index. *
--   <tt>INCLUDE</tt> - Only the specified table attributes are projected
--   into the index. The list of projected attributes are in
--   <i>NonKeyAttributes</i> . * <tt>ALL</tt> - All of the table attributes
--   are projected into the index. * <i>NonKeyAttributes</i> - A list of
--   one or more non-key attribute names that are projected into the
--   secondary index. The total count of attributes provided in
--   <i>NonKeyAttributes</i> , summed across all of the secondary indexes,
--   must not exceed 20. If you project the same attribute into two
--   different indexes, this counts as two distinct attributes when
--   determining the total. * <i>ProvisionedThroughput</i> - The
--   provisioned throughput settings for the global secondary index,
--   consisting of read and write capacity units, along with data about
--   increases and decreases. If the table is in the <tt>DELETING</tt>
--   state, no information about indexes will be returned.
tdGlobalSecondaryIndexes :: Lens' TableDescription [GlobalSecondaryIndexDescription]

-- | A timestamp, in ISO 8601 format, for this stream. Note that
--   <i>LatestStreamLabel</i> is not a unique identifier for the stream,
--   because it is possible that a stream from another table might have the
--   same timestamp. However, the combination of the following three
--   elements is guaranteed to be unique: * the AWS customer ID. * the
--   table name. * the <i>StreamLabel</i> .
tdLatestStreamLabel :: Lens' TableDescription (Maybe Text)

-- | Represents one or more local secondary indexes on the table. Each
--   index is scoped to a given partition key value. Tables with one or
--   more local secondary indexes are subject to an item collection size
--   limit, where the amount of data within a given item collection cannot
--   exceed 10 GB. Each element is composed of: * <i>IndexName</i> - The
--   name of the local secondary index. * <i>KeySchema</i> - Specifies the
--   complete index key schema. The attribute names in the key schema must
--   be between 1 and 255 characters (inclusive). The key schema must begin
--   with the same partition key as the table. * <i>Projection</i> -
--   Specifies attributes that are copied (projected) from the table into
--   the index. These are in addition to the primary key attributes and
--   index key attributes, which are automatically projected. Each
--   attribute specification is composed of: * <i>ProjectionType</i> - One
--   of the following: * <tt>KEYS_ONLY</tt> - Only the index and primary
--   keys are projected into the index. * <tt>INCLUDE</tt> - Only the
--   specified table attributes are projected into the index. The list of
--   projected attributes are in <i>NonKeyAttributes</i> . * <tt>ALL</tt> -
--   All of the table attributes are projected into the index. *
--   <i>NonKeyAttributes</i> - A list of one or more non-key attribute
--   names that are projected into the secondary index. The total count of
--   attributes provided in <i>NonKeyAttributes</i> , summed across all of
--   the secondary indexes, must not exceed 20. If you project the same
--   attribute into two different indexes, this counts as two distinct
--   attributes when determining the total. * <i>IndexSizeBytes</i> -
--   Represents the total size of the index, in bytes. DynamoDB updates
--   this value approximately every six hours. Recent changes might not be
--   reflected in this value. * <i>ItemCount</i> - Represents the number of
--   items in the index. DynamoDB updates this value approximately every
--   six hours. Recent changes might not be reflected in this value. If the
--   table is in the <tt>DELETING</tt> state, no information about indexes
--   will be returned.
tdLocalSecondaryIndexes :: Lens' TableDescription [LocalSecondaryIndexDescription]

-- | The date and time when the table was created, in <a>UNIX epoch
--   time</a> format.
tdCreationDateTime :: Lens' TableDescription (Maybe UTCTime)

-- | The number of items in the specified table. DynamoDB updates this
--   value approximately every six hours. Recent changes might not be
--   reflected in this value.
tdItemCount :: Lens' TableDescription (Maybe Integer)

-- | The name of the table.
tdTableName :: Lens' TableDescription (Maybe Text)

-- | The current DynamoDB Streams configuration for the table.
tdStreamSpecification :: Lens' TableDescription (Maybe StreamSpecification)

-- | Represents the new provisioned throughput settings to be applied to a
--   global secondary index.
--   
--   <i>See:</i> <a>updateGlobalSecondaryIndexAction</a> smart constructor.
data UpdateGlobalSecondaryIndexAction

-- | Creates a value of <a>UpdateGlobalSecondaryIndexAction</a> with the
--   minimum fields required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>ugsiaIndexName</a> - The name of the global secondary index to
--   be updated.</li>
--   <li><a>ugsiaProvisionedThroughput</a> - Undocumented member.</li>
--   </ul>
updateGlobalSecondaryIndexAction :: Text -> ProvisionedThroughput -> UpdateGlobalSecondaryIndexAction

-- | The name of the global secondary index to be updated.
ugsiaIndexName :: Lens' UpdateGlobalSecondaryIndexAction Text

-- | Undocumented member.
ugsiaProvisionedThroughput :: Lens' UpdateGlobalSecondaryIndexAction ProvisionedThroughput

-- | Represents an operation to perform - either <i>DeleteItem</i> or
--   <i>PutItem</i> . You can only request one of these operations, not
--   both, in a single <i>WriteRequest</i> . If you do need to perform both
--   of these operations, you will need to provide two separate
--   <i>WriteRequest</i> objects.
--   
--   <i>See:</i> <a>writeRequest</a> smart constructor.
data WriteRequest

-- | Creates a value of <a>WriteRequest</a> with the minimum fields
--   required to make a request.
--   
--   Use one of the following lenses to modify other fields as desired:
--   
--   <ul>
--   <li><a>wrDeleteRequest</a> - A request to perform a <i>DeleteItem</i>
--   operation.</li>
--   <li><a>wrPutRequest</a> - A request to perform a <i>PutItem</i>
--   operation.</li>
--   </ul>
writeRequest :: WriteRequest

-- | A request to perform a <i>DeleteItem</i> operation.
wrDeleteRequest :: Lens' WriteRequest (Maybe DeleteRequest)

-- | A request to perform a <i>PutItem</i> operation.
wrPutRequest :: Lens' WriteRequest (Maybe PutRequest)
