Skip to content

Commit 19cd4e2

Browse files
author
AWS
committed
Amazon Simple Storage Service Update: This release includes backward compatibility work on the "Expires" parameter.
1 parent c8eef02 commit 19cd4e2

File tree

2 files changed

+8
-2
lines changed

2 files changed

+8
-2
lines changed
Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
{
2+
"type": "feature",
3+
"category": "Amazon Simple Storage Service",
4+
"contributor": "",
5+
"description": "This release includes backward compatibility work on the \"Expires\" parameter."
6+
}

services/s3/src/main/resources/codegen-resources/service-2.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4309,7 +4309,7 @@
43094309
"type":"boolean",
43104310
"box":true
43114311
},
4312-
"Expires":{"type":"timestamp"},
4312+
"Expires":{"type":"string"},
43134313
"ExposeHeader":{"type":"string"},
43144314
"ExposeHeaders":{
43154315
"type":"list",
@@ -10773,7 +10773,7 @@
1077310773
"members":{
1077410774
"Payload":{
1077510775
"shape":"Body",
10776-
"documentation":"<p>The byte array of partial, one or more result records. S3 Select doesn't guarantee that a record will be self-contained in one record frame. To ensure continuous streaming of data, S3 Select might split the same record across multiple record frames instead of aggregating the results in memory. Some S3 clients (for example, the SDKforJava) handle this behavior by creating a <code>ByteStream</code> out of the response by default. Other clients might not handle this behavior by default. In those cases, you must aggregate the results on the client side and parse the response.</p>",
10776+
"documentation":"<p>The byte array of partial, one or more result records. S3 Select doesn't guarantee that a record will be self-contained in one record frame. To ensure continuous streaming of data, S3 Select might split the same record across multiple record frames instead of aggregating the results in memory. Some S3 clients (for example, the SDK for Java) handle this behavior by creating a <code>ByteStream</code> out of the response by default. Other clients might not handle this behavior by default. In those cases, you must aggregate the results on the client side and parse the response.</p>",
1077710777
"eventpayload":true
1077810778
}
1077910779
},

0 commit comments

Comments
 (0)