aws_sdk_dynamodb/operation/update_item/builders.rs
1// Code generated by software.amazon.smithy.rust.codegen.smithy-rs. DO NOT EDIT.
2pub use crate::operation::update_item::_update_item_output::UpdateItemOutputBuilder;
3
4pub use crate::operation::update_item::_update_item_input::UpdateItemInputBuilder;
5
6impl crate::operation::update_item::builders::UpdateItemInputBuilder {
7 /// Sends a request with this input using the given client.
8 pub async fn send_with(
9 self,
10 client: &crate::Client,
11 ) -> ::std::result::Result<
12 crate::operation::update_item::UpdateItemOutput,
13 ::aws_smithy_runtime_api::client::result::SdkError<
14 crate::operation::update_item::UpdateItemError,
15 ::aws_smithy_runtime_api::client::orchestrator::HttpResponse,
16 >,
17 > {
18 let mut fluent_builder = client.update_item();
19 fluent_builder.inner = self;
20 fluent_builder.send().await
21 }
22}
23/// Fluent builder constructing a request to `UpdateItem`.
24///
25/// <p>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).</p>
26/// <p>You can also return the item's attribute values in the same <code>UpdateItem</code> operation using the <code>ReturnValues</code> parameter.</p>
27#[derive(::std::clone::Clone, ::std::fmt::Debug)]
28pub struct UpdateItemFluentBuilder {
29 handle: ::std::sync::Arc<crate::client::Handle>,
30 inner: crate::operation::update_item::builders::UpdateItemInputBuilder,
31 config_override: ::std::option::Option<crate::config::Builder>,
32}
33impl
34 crate::client::customize::internal::CustomizableSend<
35 crate::operation::update_item::UpdateItemOutput,
36 crate::operation::update_item::UpdateItemError,
37 > for UpdateItemFluentBuilder
38{
39 fn send(
40 self,
41 config_override: crate::config::Builder,
42 ) -> crate::client::customize::internal::BoxFuture<
43 crate::client::customize::internal::SendResult<
44 crate::operation::update_item::UpdateItemOutput,
45 crate::operation::update_item::UpdateItemError,
46 >,
47 > {
48 ::std::boxed::Box::pin(async move { self.config_override(config_override).send().await })
49 }
50}
51impl UpdateItemFluentBuilder {
52 /// Creates a new `UpdateItemFluentBuilder`.
53 pub(crate) fn new(handle: ::std::sync::Arc<crate::client::Handle>) -> Self {
54 Self {
55 handle,
56 inner: ::std::default::Default::default(),
57 config_override: ::std::option::Option::None,
58 }
59 }
60 /// Access the UpdateItem as a reference.
61 pub fn as_input(&self) -> &crate::operation::update_item::builders::UpdateItemInputBuilder {
62 &self.inner
63 }
64 /// Sends the request and returns the response.
65 ///
66 /// If an error occurs, an `SdkError` will be returned with additional details that
67 /// can be matched against.
68 ///
69 /// By default, any retryable failures will be retried twice. Retry behavior
70 /// is configurable with the [RetryConfig](aws_smithy_types::retry::RetryConfig), which can be
71 /// set when configuring the client.
72 pub async fn send(
73 self,
74 ) -> ::std::result::Result<
75 crate::operation::update_item::UpdateItemOutput,
76 ::aws_smithy_runtime_api::client::result::SdkError<
77 crate::operation::update_item::UpdateItemError,
78 ::aws_smithy_runtime_api::client::orchestrator::HttpResponse,
79 >,
80 > {
81 let input = self
82 .inner
83 .build()
84 .map_err(::aws_smithy_runtime_api::client::result::SdkError::construction_failure)?;
85 let runtime_plugins = crate::operation::update_item::UpdateItem::operation_runtime_plugins(
86 self.handle.runtime_plugins.clone(),
87 &self.handle.conf,
88 self.config_override,
89 );
90 crate::operation::update_item::UpdateItem::orchestrate(&runtime_plugins, input).await
91 }
92
93 /// Consumes this builder, creating a customizable operation that can be modified before being sent.
94 pub fn customize(
95 self,
96 ) -> crate::client::customize::CustomizableOperation<
97 crate::operation::update_item::UpdateItemOutput,
98 crate::operation::update_item::UpdateItemError,
99 Self,
100 > {
101 crate::client::customize::CustomizableOperation::new(self)
102 }
103 pub(crate) fn config_override(mut self, config_override: impl ::std::convert::Into<crate::config::Builder>) -> Self {
104 self.set_config_override(::std::option::Option::Some(config_override.into()));
105 self
106 }
107
108 pub(crate) fn set_config_override(&mut self, config_override: ::std::option::Option<crate::config::Builder>) -> &mut Self {
109 self.config_override = config_override;
110 self
111 }
112 /// <p>The name of the table containing the item to update. You can also provide the Amazon Resource Name (ARN) of the table in this parameter.</p>
113 pub fn table_name(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self {
114 self.inner = self.inner.table_name(input.into());
115 self
116 }
117 /// <p>The name of the table containing the item to update. You can also provide the Amazon Resource Name (ARN) of the table in this parameter.</p>
118 pub fn set_table_name(mut self, input: ::std::option::Option<::std::string::String>) -> Self {
119 self.inner = self.inner.set_table_name(input);
120 self
121 }
122 /// <p>The name of the table containing the item to update. You can also provide the Amazon Resource Name (ARN) of the table in this parameter.</p>
123 pub fn get_table_name(&self) -> &::std::option::Option<::std::string::String> {
124 self.inner.get_table_name()
125 }
126 ///
127 /// Adds a key-value pair to `Key`.
128 ///
129 /// To override the contents of this collection use [`set_key`](Self::set_key).
130 ///
131 /// <p>The primary key of the item to be updated. Each element consists of an attribute name and a value for that attribute.</p>
132 /// <p>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.</p>
133 pub fn key(mut self, k: impl ::std::convert::Into<::std::string::String>, v: crate::types::AttributeValue) -> Self {
134 self.inner = self.inner.key(k.into(), v);
135 self
136 }
137 /// <p>The primary key of the item to be updated. Each element consists of an attribute name and a value for that attribute.</p>
138 /// <p>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.</p>
139 pub fn set_key(mut self, input: ::std::option::Option<::std::collections::HashMap<::std::string::String, crate::types::AttributeValue>>) -> Self {
140 self.inner = self.inner.set_key(input);
141 self
142 }
143 /// <p>The primary key of the item to be updated. Each element consists of an attribute name and a value for that attribute.</p>
144 /// <p>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.</p>
145 pub fn get_key(&self) -> &::std::option::Option<::std::collections::HashMap<::std::string::String, crate::types::AttributeValue>> {
146 self.inner.get_key()
147 }
148 ///
149 /// Adds a key-value pair to `AttributeUpdates`.
150 ///
151 /// To override the contents of this collection use [`set_attribute_updates`](Self::set_attribute_updates).
152 ///
153 /// <p>This is a legacy parameter. Use <code>UpdateExpression</code> instead. For more information, see <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/LegacyConditionalParameters.AttributeUpdates.html">AttributeUpdates</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>
154 pub fn attribute_updates(mut self, k: impl ::std::convert::Into<::std::string::String>, v: crate::types::AttributeValueUpdate) -> Self {
155 self.inner = self.inner.attribute_updates(k.into(), v);
156 self
157 }
158 /// <p>This is a legacy parameter. Use <code>UpdateExpression</code> instead. For more information, see <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/LegacyConditionalParameters.AttributeUpdates.html">AttributeUpdates</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>
159 pub fn set_attribute_updates(
160 mut self,
161 input: ::std::option::Option<::std::collections::HashMap<::std::string::String, crate::types::AttributeValueUpdate>>,
162 ) -> Self {
163 self.inner = self.inner.set_attribute_updates(input);
164 self
165 }
166 /// <p>This is a legacy parameter. Use <code>UpdateExpression</code> instead. For more information, see <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/LegacyConditionalParameters.AttributeUpdates.html">AttributeUpdates</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>
167 pub fn get_attribute_updates(
168 &self,
169 ) -> &::std::option::Option<::std::collections::HashMap<::std::string::String, crate::types::AttributeValueUpdate>> {
170 self.inner.get_attribute_updates()
171 }
172 ///
173 /// Adds a key-value pair to `Expected`.
174 ///
175 /// To override the contents of this collection use [`set_expected`](Self::set_expected).
176 ///
177 /// <p>This is a legacy parameter. Use <code>ConditionExpression</code> instead. For more information, see <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/LegacyConditionalParameters.Expected.html">Expected</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>
178 pub fn expected(mut self, k: impl ::std::convert::Into<::std::string::String>, v: crate::types::ExpectedAttributeValue) -> Self {
179 self.inner = self.inner.expected(k.into(), v);
180 self
181 }
182 /// <p>This is a legacy parameter. Use <code>ConditionExpression</code> instead. For more information, see <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/LegacyConditionalParameters.Expected.html">Expected</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>
183 pub fn set_expected(
184 mut self,
185 input: ::std::option::Option<::std::collections::HashMap<::std::string::String, crate::types::ExpectedAttributeValue>>,
186 ) -> Self {
187 self.inner = self.inner.set_expected(input);
188 self
189 }
190 /// <p>This is a legacy parameter. Use <code>ConditionExpression</code> instead. For more information, see <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/LegacyConditionalParameters.Expected.html">Expected</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>
191 pub fn get_expected(&self) -> &::std::option::Option<::std::collections::HashMap<::std::string::String, crate::types::ExpectedAttributeValue>> {
192 self.inner.get_expected()
193 }
194 /// <p>This is a legacy parameter. Use <code>ConditionExpression</code> instead. For more information, see <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/LegacyConditionalParameters.ConditionalOperator.html">ConditionalOperator</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>
195 pub fn conditional_operator(mut self, input: crate::types::ConditionalOperator) -> Self {
196 self.inner = self.inner.conditional_operator(input);
197 self
198 }
199 /// <p>This is a legacy parameter. Use <code>ConditionExpression</code> instead. For more information, see <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/LegacyConditionalParameters.ConditionalOperator.html">ConditionalOperator</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>
200 pub fn set_conditional_operator(mut self, input: ::std::option::Option<crate::types::ConditionalOperator>) -> Self {
201 self.inner = self.inner.set_conditional_operator(input);
202 self
203 }
204 /// <p>This is a legacy parameter. Use <code>ConditionExpression</code> instead. For more information, see <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/LegacyConditionalParameters.ConditionalOperator.html">ConditionalOperator</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>
205 pub fn get_conditional_operator(&self) -> &::std::option::Option<crate::types::ConditionalOperator> {
206 self.inner.get_conditional_operator()
207 }
208 /// <p>Use <code>ReturnValues</code> if you want to get the item attributes as they appear before or after they are successfully updated. For <code>UpdateItem</code>, the valid values are:</p>
209 /// <ul>
210 /// <li>
211 /// <p><code>NONE</code> - If <code>ReturnValues</code> is not specified, or if its value is <code>NONE</code>, then nothing is returned. (This setting is the default for <code>ReturnValues</code>.)</p></li>
212 /// <li>
213 /// <p><code>ALL_OLD</code> - Returns all of the attributes of the item, as they appeared before the UpdateItem operation.</p></li>
214 /// <li>
215 /// <p><code>UPDATED_OLD</code> - Returns only the updated attributes, as they appeared before the UpdateItem operation.</p></li>
216 /// <li>
217 /// <p><code>ALL_NEW</code> - Returns all of the attributes of the item, as they appear after the UpdateItem operation.</p></li>
218 /// <li>
219 /// <p><code>UPDATED_NEW</code> - Returns only the updated attributes, as they appear after the UpdateItem operation.</p></li>
220 /// </ul>
221 /// <p>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.</p>
222 /// <p>The values returned are strongly consistent.</p>
223 pub fn return_values(mut self, input: crate::types::ReturnValue) -> Self {
224 self.inner = self.inner.return_values(input);
225 self
226 }
227 /// <p>Use <code>ReturnValues</code> if you want to get the item attributes as they appear before or after they are successfully updated. For <code>UpdateItem</code>, the valid values are:</p>
228 /// <ul>
229 /// <li>
230 /// <p><code>NONE</code> - If <code>ReturnValues</code> is not specified, or if its value is <code>NONE</code>, then nothing is returned. (This setting is the default for <code>ReturnValues</code>.)</p></li>
231 /// <li>
232 /// <p><code>ALL_OLD</code> - Returns all of the attributes of the item, as they appeared before the UpdateItem operation.</p></li>
233 /// <li>
234 /// <p><code>UPDATED_OLD</code> - Returns only the updated attributes, as they appeared before the UpdateItem operation.</p></li>
235 /// <li>
236 /// <p><code>ALL_NEW</code> - Returns all of the attributes of the item, as they appear after the UpdateItem operation.</p></li>
237 /// <li>
238 /// <p><code>UPDATED_NEW</code> - Returns only the updated attributes, as they appear after the UpdateItem operation.</p></li>
239 /// </ul>
240 /// <p>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.</p>
241 /// <p>The values returned are strongly consistent.</p>
242 pub fn set_return_values(mut self, input: ::std::option::Option<crate::types::ReturnValue>) -> Self {
243 self.inner = self.inner.set_return_values(input);
244 self
245 }
246 /// <p>Use <code>ReturnValues</code> if you want to get the item attributes as they appear before or after they are successfully updated. For <code>UpdateItem</code>, the valid values are:</p>
247 /// <ul>
248 /// <li>
249 /// <p><code>NONE</code> - If <code>ReturnValues</code> is not specified, or if its value is <code>NONE</code>, then nothing is returned. (This setting is the default for <code>ReturnValues</code>.)</p></li>
250 /// <li>
251 /// <p><code>ALL_OLD</code> - Returns all of the attributes of the item, as they appeared before the UpdateItem operation.</p></li>
252 /// <li>
253 /// <p><code>UPDATED_OLD</code> - Returns only the updated attributes, as they appeared before the UpdateItem operation.</p></li>
254 /// <li>
255 /// <p><code>ALL_NEW</code> - Returns all of the attributes of the item, as they appear after the UpdateItem operation.</p></li>
256 /// <li>
257 /// <p><code>UPDATED_NEW</code> - Returns only the updated attributes, as they appear after the UpdateItem operation.</p></li>
258 /// </ul>
259 /// <p>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.</p>
260 /// <p>The values returned are strongly consistent.</p>
261 pub fn get_return_values(&self) -> &::std::option::Option<crate::types::ReturnValue> {
262 self.inner.get_return_values()
263 }
264 /// <p>Determines the level of detail about either provisioned or on-demand throughput consumption that is returned in the response:</p>
265 /// <ul>
266 /// <li>
267 /// <p><code>INDEXES</code> - The response includes the aggregate <code>ConsumedCapacity</code> for the operation, together with <code>ConsumedCapacity</code> for each table and secondary index that was accessed.</p>
268 /// <p>Note that some operations, such as <code>GetItem</code> and <code>BatchGetItem</code>, do not access any indexes at all. In these cases, specifying <code>INDEXES</code> will only return <code>ConsumedCapacity</code> information for table(s).</p></li>
269 /// <li>
270 /// <p><code>TOTAL</code> - The response includes only the aggregate <code>ConsumedCapacity</code> for the operation.</p></li>
271 /// <li>
272 /// <p><code>NONE</code> - No <code>ConsumedCapacity</code> details are included in the response.</p></li>
273 /// </ul>
274 pub fn return_consumed_capacity(mut self, input: crate::types::ReturnConsumedCapacity) -> Self {
275 self.inner = self.inner.return_consumed_capacity(input);
276 self
277 }
278 /// <p>Determines the level of detail about either provisioned or on-demand throughput consumption that is returned in the response:</p>
279 /// <ul>
280 /// <li>
281 /// <p><code>INDEXES</code> - The response includes the aggregate <code>ConsumedCapacity</code> for the operation, together with <code>ConsumedCapacity</code> for each table and secondary index that was accessed.</p>
282 /// <p>Note that some operations, such as <code>GetItem</code> and <code>BatchGetItem</code>, do not access any indexes at all. In these cases, specifying <code>INDEXES</code> will only return <code>ConsumedCapacity</code> information for table(s).</p></li>
283 /// <li>
284 /// <p><code>TOTAL</code> - The response includes only the aggregate <code>ConsumedCapacity</code> for the operation.</p></li>
285 /// <li>
286 /// <p><code>NONE</code> - No <code>ConsumedCapacity</code> details are included in the response.</p></li>
287 /// </ul>
288 pub fn set_return_consumed_capacity(mut self, input: ::std::option::Option<crate::types::ReturnConsumedCapacity>) -> Self {
289 self.inner = self.inner.set_return_consumed_capacity(input);
290 self
291 }
292 /// <p>Determines the level of detail about either provisioned or on-demand throughput consumption that is returned in the response:</p>
293 /// <ul>
294 /// <li>
295 /// <p><code>INDEXES</code> - The response includes the aggregate <code>ConsumedCapacity</code> for the operation, together with <code>ConsumedCapacity</code> for each table and secondary index that was accessed.</p>
296 /// <p>Note that some operations, such as <code>GetItem</code> and <code>BatchGetItem</code>, do not access any indexes at all. In these cases, specifying <code>INDEXES</code> will only return <code>ConsumedCapacity</code> information for table(s).</p></li>
297 /// <li>
298 /// <p><code>TOTAL</code> - The response includes only the aggregate <code>ConsumedCapacity</code> for the operation.</p></li>
299 /// <li>
300 /// <p><code>NONE</code> - No <code>ConsumedCapacity</code> details are included in the response.</p></li>
301 /// </ul>
302 pub fn get_return_consumed_capacity(&self) -> &::std::option::Option<crate::types::ReturnConsumedCapacity> {
303 self.inner.get_return_consumed_capacity()
304 }
305 /// <p>Determines whether item collection metrics are returned. If set to <code>SIZE</code>, the response includes statistics about item collections, if any, that were modified during the operation are returned in the response. If set to <code>NONE</code> (the default), no statistics are returned.</p>
306 pub fn return_item_collection_metrics(mut self, input: crate::types::ReturnItemCollectionMetrics) -> Self {
307 self.inner = self.inner.return_item_collection_metrics(input);
308 self
309 }
310 /// <p>Determines whether item collection metrics are returned. If set to <code>SIZE</code>, the response includes statistics about item collections, if any, that were modified during the operation are returned in the response. If set to <code>NONE</code> (the default), no statistics are returned.</p>
311 pub fn set_return_item_collection_metrics(mut self, input: ::std::option::Option<crate::types::ReturnItemCollectionMetrics>) -> Self {
312 self.inner = self.inner.set_return_item_collection_metrics(input);
313 self
314 }
315 /// <p>Determines whether item collection metrics are returned. If set to <code>SIZE</code>, the response includes statistics about item collections, if any, that were modified during the operation are returned in the response. If set to <code>NONE</code> (the default), no statistics are returned.</p>
316 pub fn get_return_item_collection_metrics(&self) -> &::std::option::Option<crate::types::ReturnItemCollectionMetrics> {
317 self.inner.get_return_item_collection_metrics()
318 }
319 /// <p>An expression that defines one or more attributes to be updated, the action to be performed on them, and new values for them.</p>
320 /// <p>The following action values are available for <code>UpdateExpression</code>.</p>
321 /// <ul>
322 /// <li>
323 /// <p><code>SET</code> - Adds one or more attributes and values to an item. If any of these attributes already exist, they are replaced by the new values. You can also use <code>SET</code> to add or subtract from an attribute that is of type Number. For example: <code>SET myNum = myNum + :val</code></p>
324 /// <p><code>SET</code> supports the following functions:</p>
325 /// <ul>
326 /// <li>
327 /// <p><code>if_not_exists (path, operand)</code> - if the item does not contain an attribute at the specified path, then <code>if_not_exists</code> 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.</p></li>
328 /// <li>
329 /// <p><code>list_append (operand, operand)</code> - 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.</p></li>
330 /// </ul>
331 /// <p>These function names are case-sensitive.</p></li>
332 /// <li>
333 /// <p><code>REMOVE</code> - Removes one or more attributes from an item.</p></li>
334 /// <li>
335 /// <p><code>ADD</code> - Adds the specified value to the item, if the attribute does not already exist. If the attribute does exist, then the behavior of <code>ADD</code> depends on the data type of the attribute:</p>
336 /// <ul>
337 /// <li>
338 /// <p>If the existing attribute is a number, and if <code>Value</code> is also a number, then <code>Value</code> is mathematically added to the existing attribute. If <code>Value</code> is a negative number, then it is subtracted from the existing attribute.</p><note>
339 /// <p>If you use <code>ADD</code> to increment or decrement a number value for an item that doesn't exist before the update, DynamoDB uses <code>0</code> as the initial value.</p>
340 /// <p>Similarly, if you use <code>ADD</code> for an existing item to increment or decrement an attribute value that doesn't exist before the update, DynamoDB uses <code>0</code> as the initial value. For example, suppose that the item you want to update doesn't have an attribute named <code>itemcount</code>, but you decide to <code>ADD</code> the number <code>3</code> to this attribute anyway. DynamoDB will create the <code>itemcount</code> attribute, set its initial value to <code>0</code>, and finally add <code>3</code> to it. The result will be a new <code>itemcount</code> attribute in the item, with a value of <code>3</code>.</p>
341 /// </note></li>
342 /// <li>
343 /// <p>If the existing data type is a set and if <code>Value</code> is also a set, then <code>Value</code> is added to the existing set. For example, if the attribute value is the set <code>\[1,2\]</code>, and the <code>ADD</code> action specified <code>\[3\]</code>, then the final attribute value is <code>\[1,2,3\]</code>. An error occurs if an <code>ADD</code> action is specified for a set attribute and the attribute type specified does not match the existing set type.</p>
344 /// <p>Both sets must have the same primitive data type. For example, if the existing data type is a set of strings, the <code>Value</code> must also be a set of strings.</p></li>
345 /// </ul><important>
346 /// <p>The <code>ADD</code> action only supports Number and set data types. In addition, <code>ADD</code> can only be used on top-level attributes, not nested attributes.</p>
347 /// </important></li>
348 /// <li>
349 /// <p><code>DELETE</code> - Deletes an element from a set.</p>
350 /// <p>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 <code>\[a,b,c\]</code> and the <code>DELETE</code> action specifies <code>\[a,c\]</code>, then the final attribute value is <code>\[b\]</code>. Specifying an empty set is an error.</p><important>
351 /// <p>The <code>DELETE</code> action only supports set data types. In addition, <code>DELETE</code> can only be used on top-level attributes, not nested attributes.</p>
352 /// </important></li>
353 /// </ul>
354 /// <p>You can have many actions in a single expression, such as the following: <code>SET a=:value1, b=:value2 DELETE :value3, :value4, :value5</code></p>
355 /// <p>For more information on update expressions, see <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Expressions.Modifying.html">Modifying Items and Attributes</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>
356 pub fn update_expression(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self {
357 self.inner = self.inner.update_expression(input.into());
358 self
359 }
360 /// <p>An expression that defines one or more attributes to be updated, the action to be performed on them, and new values for them.</p>
361 /// <p>The following action values are available for <code>UpdateExpression</code>.</p>
362 /// <ul>
363 /// <li>
364 /// <p><code>SET</code> - Adds one or more attributes and values to an item. If any of these attributes already exist, they are replaced by the new values. You can also use <code>SET</code> to add or subtract from an attribute that is of type Number. For example: <code>SET myNum = myNum + :val</code></p>
365 /// <p><code>SET</code> supports the following functions:</p>
366 /// <ul>
367 /// <li>
368 /// <p><code>if_not_exists (path, operand)</code> - if the item does not contain an attribute at the specified path, then <code>if_not_exists</code> 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.</p></li>
369 /// <li>
370 /// <p><code>list_append (operand, operand)</code> - 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.</p></li>
371 /// </ul>
372 /// <p>These function names are case-sensitive.</p></li>
373 /// <li>
374 /// <p><code>REMOVE</code> - Removes one or more attributes from an item.</p></li>
375 /// <li>
376 /// <p><code>ADD</code> - Adds the specified value to the item, if the attribute does not already exist. If the attribute does exist, then the behavior of <code>ADD</code> depends on the data type of the attribute:</p>
377 /// <ul>
378 /// <li>
379 /// <p>If the existing attribute is a number, and if <code>Value</code> is also a number, then <code>Value</code> is mathematically added to the existing attribute. If <code>Value</code> is a negative number, then it is subtracted from the existing attribute.</p><note>
380 /// <p>If you use <code>ADD</code> to increment or decrement a number value for an item that doesn't exist before the update, DynamoDB uses <code>0</code> as the initial value.</p>
381 /// <p>Similarly, if you use <code>ADD</code> for an existing item to increment or decrement an attribute value that doesn't exist before the update, DynamoDB uses <code>0</code> as the initial value. For example, suppose that the item you want to update doesn't have an attribute named <code>itemcount</code>, but you decide to <code>ADD</code> the number <code>3</code> to this attribute anyway. DynamoDB will create the <code>itemcount</code> attribute, set its initial value to <code>0</code>, and finally add <code>3</code> to it. The result will be a new <code>itemcount</code> attribute in the item, with a value of <code>3</code>.</p>
382 /// </note></li>
383 /// <li>
384 /// <p>If the existing data type is a set and if <code>Value</code> is also a set, then <code>Value</code> is added to the existing set. For example, if the attribute value is the set <code>\[1,2\]</code>, and the <code>ADD</code> action specified <code>\[3\]</code>, then the final attribute value is <code>\[1,2,3\]</code>. An error occurs if an <code>ADD</code> action is specified for a set attribute and the attribute type specified does not match the existing set type.</p>
385 /// <p>Both sets must have the same primitive data type. For example, if the existing data type is a set of strings, the <code>Value</code> must also be a set of strings.</p></li>
386 /// </ul><important>
387 /// <p>The <code>ADD</code> action only supports Number and set data types. In addition, <code>ADD</code> can only be used on top-level attributes, not nested attributes.</p>
388 /// </important></li>
389 /// <li>
390 /// <p><code>DELETE</code> - Deletes an element from a set.</p>
391 /// <p>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 <code>\[a,b,c\]</code> and the <code>DELETE</code> action specifies <code>\[a,c\]</code>, then the final attribute value is <code>\[b\]</code>. Specifying an empty set is an error.</p><important>
392 /// <p>The <code>DELETE</code> action only supports set data types. In addition, <code>DELETE</code> can only be used on top-level attributes, not nested attributes.</p>
393 /// </important></li>
394 /// </ul>
395 /// <p>You can have many actions in a single expression, such as the following: <code>SET a=:value1, b=:value2 DELETE :value3, :value4, :value5</code></p>
396 /// <p>For more information on update expressions, see <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Expressions.Modifying.html">Modifying Items and Attributes</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>
397 pub fn set_update_expression(mut self, input: ::std::option::Option<::std::string::String>) -> Self {
398 self.inner = self.inner.set_update_expression(input);
399 self
400 }
401 /// <p>An expression that defines one or more attributes to be updated, the action to be performed on them, and new values for them.</p>
402 /// <p>The following action values are available for <code>UpdateExpression</code>.</p>
403 /// <ul>
404 /// <li>
405 /// <p><code>SET</code> - Adds one or more attributes and values to an item. If any of these attributes already exist, they are replaced by the new values. You can also use <code>SET</code> to add or subtract from an attribute that is of type Number. For example: <code>SET myNum = myNum + :val</code></p>
406 /// <p><code>SET</code> supports the following functions:</p>
407 /// <ul>
408 /// <li>
409 /// <p><code>if_not_exists (path, operand)</code> - if the item does not contain an attribute at the specified path, then <code>if_not_exists</code> 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.</p></li>
410 /// <li>
411 /// <p><code>list_append (operand, operand)</code> - 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.</p></li>
412 /// </ul>
413 /// <p>These function names are case-sensitive.</p></li>
414 /// <li>
415 /// <p><code>REMOVE</code> - Removes one or more attributes from an item.</p></li>
416 /// <li>
417 /// <p><code>ADD</code> - Adds the specified value to the item, if the attribute does not already exist. If the attribute does exist, then the behavior of <code>ADD</code> depends on the data type of the attribute:</p>
418 /// <ul>
419 /// <li>
420 /// <p>If the existing attribute is a number, and if <code>Value</code> is also a number, then <code>Value</code> is mathematically added to the existing attribute. If <code>Value</code> is a negative number, then it is subtracted from the existing attribute.</p><note>
421 /// <p>If you use <code>ADD</code> to increment or decrement a number value for an item that doesn't exist before the update, DynamoDB uses <code>0</code> as the initial value.</p>
422 /// <p>Similarly, if you use <code>ADD</code> for an existing item to increment or decrement an attribute value that doesn't exist before the update, DynamoDB uses <code>0</code> as the initial value. For example, suppose that the item you want to update doesn't have an attribute named <code>itemcount</code>, but you decide to <code>ADD</code> the number <code>3</code> to this attribute anyway. DynamoDB will create the <code>itemcount</code> attribute, set its initial value to <code>0</code>, and finally add <code>3</code> to it. The result will be a new <code>itemcount</code> attribute in the item, with a value of <code>3</code>.</p>
423 /// </note></li>
424 /// <li>
425 /// <p>If the existing data type is a set and if <code>Value</code> is also a set, then <code>Value</code> is added to the existing set. For example, if the attribute value is the set <code>\[1,2\]</code>, and the <code>ADD</code> action specified <code>\[3\]</code>, then the final attribute value is <code>\[1,2,3\]</code>. An error occurs if an <code>ADD</code> action is specified for a set attribute and the attribute type specified does not match the existing set type.</p>
426 /// <p>Both sets must have the same primitive data type. For example, if the existing data type is a set of strings, the <code>Value</code> must also be a set of strings.</p></li>
427 /// </ul><important>
428 /// <p>The <code>ADD</code> action only supports Number and set data types. In addition, <code>ADD</code> can only be used on top-level attributes, not nested attributes.</p>
429 /// </important></li>
430 /// <li>
431 /// <p><code>DELETE</code> - Deletes an element from a set.</p>
432 /// <p>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 <code>\[a,b,c\]</code> and the <code>DELETE</code> action specifies <code>\[a,c\]</code>, then the final attribute value is <code>\[b\]</code>. Specifying an empty set is an error.</p><important>
433 /// <p>The <code>DELETE</code> action only supports set data types. In addition, <code>DELETE</code> can only be used on top-level attributes, not nested attributes.</p>
434 /// </important></li>
435 /// </ul>
436 /// <p>You can have many actions in a single expression, such as the following: <code>SET a=:value1, b=:value2 DELETE :value3, :value4, :value5</code></p>
437 /// <p>For more information on update expressions, see <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Expressions.Modifying.html">Modifying Items and Attributes</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>
438 pub fn get_update_expression(&self) -> &::std::option::Option<::std::string::String> {
439 self.inner.get_update_expression()
440 }
441 /// <p>A condition that must be satisfied in order for a conditional update to succeed.</p>
442 /// <p>An expression can contain any of the following:</p>
443 /// <ul>
444 /// <li>
445 /// <p>Functions: <code>attribute_exists | attribute_not_exists | attribute_type | contains | begins_with | size</code></p>
446 /// <p>These function names are case-sensitive.</p></li>
447 /// <li>
448 /// <p>Comparison operators: <code>= | <> | < | > | <= | >= | BETWEEN | IN </code></p></li>
449 /// <li>
450 /// <p>Logical operators: <code>AND | OR | NOT</code></p></li>
451 /// </ul>
452 /// <p>For more information about condition expressions, see <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Expressions.SpecifyingConditions.html">Specifying Conditions</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>
453 pub fn condition_expression(mut self, input: impl ::std::convert::Into<::std::string::String>) -> Self {
454 self.inner = self.inner.condition_expression(input.into());
455 self
456 }
457 /// <p>A condition that must be satisfied in order for a conditional update to succeed.</p>
458 /// <p>An expression can contain any of the following:</p>
459 /// <ul>
460 /// <li>
461 /// <p>Functions: <code>attribute_exists | attribute_not_exists | attribute_type | contains | begins_with | size</code></p>
462 /// <p>These function names are case-sensitive.</p></li>
463 /// <li>
464 /// <p>Comparison operators: <code>= | <> | < | > | <= | >= | BETWEEN | IN </code></p></li>
465 /// <li>
466 /// <p>Logical operators: <code>AND | OR | NOT</code></p></li>
467 /// </ul>
468 /// <p>For more information about condition expressions, see <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Expressions.SpecifyingConditions.html">Specifying Conditions</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>
469 pub fn set_condition_expression(mut self, input: ::std::option::Option<::std::string::String>) -> Self {
470 self.inner = self.inner.set_condition_expression(input);
471 self
472 }
473 /// <p>A condition that must be satisfied in order for a conditional update to succeed.</p>
474 /// <p>An expression can contain any of the following:</p>
475 /// <ul>
476 /// <li>
477 /// <p>Functions: <code>attribute_exists | attribute_not_exists | attribute_type | contains | begins_with | size</code></p>
478 /// <p>These function names are case-sensitive.</p></li>
479 /// <li>
480 /// <p>Comparison operators: <code>= | <> | < | > | <= | >= | BETWEEN | IN </code></p></li>
481 /// <li>
482 /// <p>Logical operators: <code>AND | OR | NOT</code></p></li>
483 /// </ul>
484 /// <p>For more information about condition expressions, see <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Expressions.SpecifyingConditions.html">Specifying Conditions</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>
485 pub fn get_condition_expression(&self) -> &::std::option::Option<::std::string::String> {
486 self.inner.get_condition_expression()
487 }
488 ///
489 /// Adds a key-value pair to `ExpressionAttributeNames`.
490 ///
491 /// To override the contents of this collection use [`set_expression_attribute_names`](Self::set_expression_attribute_names).
492 ///
493 /// <p>One or more substitution tokens for attribute names in an expression. The following are some use cases for using <code>ExpressionAttributeNames</code>:</p>
494 /// <ul>
495 /// <li>
496 /// <p>To access an attribute whose name conflicts with a DynamoDB reserved word.</p></li>
497 /// <li>
498 /// <p>To create a placeholder for repeating occurrences of an attribute name in an expression.</p></li>
499 /// <li>
500 /// <p>To prevent special characters in an attribute name from being misinterpreted in an expression.</p></li>
501 /// </ul>
502 /// <p>Use the <b>#</b> character in an expression to dereference an attribute name. For example, consider the following attribute name:</p>
503 /// <ul>
504 /// <li>
505 /// <p><code>Percentile</code></p></li>
506 /// </ul>
507 /// <p>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 href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ReservedWords.html">Reserved Words</a> in the <i>Amazon DynamoDB Developer Guide</i>.) To work around this, you could specify the following for <code>ExpressionAttributeNames</code>:</p>
508 /// <ul>
509 /// <li>
510 /// <p><code>{"#P":"Percentile"}</code></p></li>
511 /// </ul>
512 /// <p>You could then use this substitution in an expression, as in this example:</p>
513 /// <ul>
514 /// <li>
515 /// <p><code>#P = :val</code></p></li>
516 /// </ul><note>
517 /// <p>Tokens that begin with the <b>:</b> character are <i>expression attribute values</i>, which are placeholders for the actual value at runtime.</p>
518 /// </note>
519 /// <p>For more information about expression attribute names, see <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Expressions.AccessingItemAttributes.html">Specifying Item Attributes</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>
520 pub fn expression_attribute_names(
521 mut self,
522 k: impl ::std::convert::Into<::std::string::String>,
523 v: impl ::std::convert::Into<::std::string::String>,
524 ) -> Self {
525 self.inner = self.inner.expression_attribute_names(k.into(), v.into());
526 self
527 }
528 /// <p>One or more substitution tokens for attribute names in an expression. The following are some use cases for using <code>ExpressionAttributeNames</code>:</p>
529 /// <ul>
530 /// <li>
531 /// <p>To access an attribute whose name conflicts with a DynamoDB reserved word.</p></li>
532 /// <li>
533 /// <p>To create a placeholder for repeating occurrences of an attribute name in an expression.</p></li>
534 /// <li>
535 /// <p>To prevent special characters in an attribute name from being misinterpreted in an expression.</p></li>
536 /// </ul>
537 /// <p>Use the <b>#</b> character in an expression to dereference an attribute name. For example, consider the following attribute name:</p>
538 /// <ul>
539 /// <li>
540 /// <p><code>Percentile</code></p></li>
541 /// </ul>
542 /// <p>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 href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ReservedWords.html">Reserved Words</a> in the <i>Amazon DynamoDB Developer Guide</i>.) To work around this, you could specify the following for <code>ExpressionAttributeNames</code>:</p>
543 /// <ul>
544 /// <li>
545 /// <p><code>{"#P":"Percentile"}</code></p></li>
546 /// </ul>
547 /// <p>You could then use this substitution in an expression, as in this example:</p>
548 /// <ul>
549 /// <li>
550 /// <p><code>#P = :val</code></p></li>
551 /// </ul><note>
552 /// <p>Tokens that begin with the <b>:</b> character are <i>expression attribute values</i>, which are placeholders for the actual value at runtime.</p>
553 /// </note>
554 /// <p>For more information about expression attribute names, see <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Expressions.AccessingItemAttributes.html">Specifying Item Attributes</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>
555 pub fn set_expression_attribute_names(
556 mut self,
557 input: ::std::option::Option<::std::collections::HashMap<::std::string::String, ::std::string::String>>,
558 ) -> Self {
559 self.inner = self.inner.set_expression_attribute_names(input);
560 self
561 }
562 /// <p>One or more substitution tokens for attribute names in an expression. The following are some use cases for using <code>ExpressionAttributeNames</code>:</p>
563 /// <ul>
564 /// <li>
565 /// <p>To access an attribute whose name conflicts with a DynamoDB reserved word.</p></li>
566 /// <li>
567 /// <p>To create a placeholder for repeating occurrences of an attribute name in an expression.</p></li>
568 /// <li>
569 /// <p>To prevent special characters in an attribute name from being misinterpreted in an expression.</p></li>
570 /// </ul>
571 /// <p>Use the <b>#</b> character in an expression to dereference an attribute name. For example, consider the following attribute name:</p>
572 /// <ul>
573 /// <li>
574 /// <p><code>Percentile</code></p></li>
575 /// </ul>
576 /// <p>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 href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ReservedWords.html">Reserved Words</a> in the <i>Amazon DynamoDB Developer Guide</i>.) To work around this, you could specify the following for <code>ExpressionAttributeNames</code>:</p>
577 /// <ul>
578 /// <li>
579 /// <p><code>{"#P":"Percentile"}</code></p></li>
580 /// </ul>
581 /// <p>You could then use this substitution in an expression, as in this example:</p>
582 /// <ul>
583 /// <li>
584 /// <p><code>#P = :val</code></p></li>
585 /// </ul><note>
586 /// <p>Tokens that begin with the <b>:</b> character are <i>expression attribute values</i>, which are placeholders for the actual value at runtime.</p>
587 /// </note>
588 /// <p>For more information about expression attribute names, see <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Expressions.AccessingItemAttributes.html">Specifying Item Attributes</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>
589 pub fn get_expression_attribute_names(
590 &self,
591 ) -> &::std::option::Option<::std::collections::HashMap<::std::string::String, ::std::string::String>> {
592 self.inner.get_expression_attribute_names()
593 }
594 ///
595 /// Adds a key-value pair to `ExpressionAttributeValues`.
596 ///
597 /// To override the contents of this collection use [`set_expression_attribute_values`](Self::set_expression_attribute_values).
598 ///
599 /// <p>One or more values that can be substituted in an expression.</p>
600 /// <p>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 <code>ProductStatus</code> attribute was one of the following:</p>
601 /// <p><code>Available | Backordered | Discontinued</code></p>
602 /// <p>You would first need to specify <code>ExpressionAttributeValues</code> as follows:</p>
603 /// <p><code>{ ":avail":{"S":"Available"}, ":back":{"S":"Backordered"}, ":disc":{"S":"Discontinued"} }</code></p>
604 /// <p>You could then use these values in an expression, such as this:</p>
605 /// <p><code>ProductStatus IN (:avail, :back, :disc)</code></p>
606 /// <p>For more information on expression attribute values, see <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Expressions.SpecifyingConditions.html">Condition Expressions</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>
607 pub fn expression_attribute_values(mut self, k: impl ::std::convert::Into<::std::string::String>, v: crate::types::AttributeValue) -> Self {
608 self.inner = self.inner.expression_attribute_values(k.into(), v);
609 self
610 }
611 /// <p>One or more values that can be substituted in an expression.</p>
612 /// <p>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 <code>ProductStatus</code> attribute was one of the following:</p>
613 /// <p><code>Available | Backordered | Discontinued</code></p>
614 /// <p>You would first need to specify <code>ExpressionAttributeValues</code> as follows:</p>
615 /// <p><code>{ ":avail":{"S":"Available"}, ":back":{"S":"Backordered"}, ":disc":{"S":"Discontinued"} }</code></p>
616 /// <p>You could then use these values in an expression, such as this:</p>
617 /// <p><code>ProductStatus IN (:avail, :back, :disc)</code></p>
618 /// <p>For more information on expression attribute values, see <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Expressions.SpecifyingConditions.html">Condition Expressions</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>
619 pub fn set_expression_attribute_values(
620 mut self,
621 input: ::std::option::Option<::std::collections::HashMap<::std::string::String, crate::types::AttributeValue>>,
622 ) -> Self {
623 self.inner = self.inner.set_expression_attribute_values(input);
624 self
625 }
626 /// <p>One or more values that can be substituted in an expression.</p>
627 /// <p>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 <code>ProductStatus</code> attribute was one of the following:</p>
628 /// <p><code>Available | Backordered | Discontinued</code></p>
629 /// <p>You would first need to specify <code>ExpressionAttributeValues</code> as follows:</p>
630 /// <p><code>{ ":avail":{"S":"Available"}, ":back":{"S":"Backordered"}, ":disc":{"S":"Discontinued"} }</code></p>
631 /// <p>You could then use these values in an expression, such as this:</p>
632 /// <p><code>ProductStatus IN (:avail, :back, :disc)</code></p>
633 /// <p>For more information on expression attribute values, see <a href="https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Expressions.SpecifyingConditions.html">Condition Expressions</a> in the <i>Amazon DynamoDB Developer Guide</i>.</p>
634 pub fn get_expression_attribute_values(
635 &self,
636 ) -> &::std::option::Option<::std::collections::HashMap<::std::string::String, crate::types::AttributeValue>> {
637 self.inner.get_expression_attribute_values()
638 }
639 /// <p>An optional parameter that returns the item attributes for an <code>UpdateItem</code> operation that failed a condition check.</p>
640 /// <p>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.</p>
641 pub fn return_values_on_condition_check_failure(mut self, input: crate::types::ReturnValuesOnConditionCheckFailure) -> Self {
642 self.inner = self.inner.return_values_on_condition_check_failure(input);
643 self
644 }
645 /// <p>An optional parameter that returns the item attributes for an <code>UpdateItem</code> operation that failed a condition check.</p>
646 /// <p>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.</p>
647 pub fn set_return_values_on_condition_check_failure(
648 mut self,
649 input: ::std::option::Option<crate::types::ReturnValuesOnConditionCheckFailure>,
650 ) -> Self {
651 self.inner = self.inner.set_return_values_on_condition_check_failure(input);
652 self
653 }
654 /// <p>An optional parameter that returns the item attributes for an <code>UpdateItem</code> operation that failed a condition check.</p>
655 /// <p>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.</p>
656 pub fn get_return_values_on_condition_check_failure(&self) -> &::std::option::Option<crate::types::ReturnValuesOnConditionCheckFailure> {
657 self.inner.get_return_values_on_condition_check_failure()
658 }
659}