Contains options to return a list of summary information about the objects in the specified bucket. Depending on the request parameters, additional information is returned, such as common prefixes if a delimiter was specified. List results are always returned in lexicographic (alphabetical) order.
Buckets can contain a virtually unlimited number of keys, and the complete results of a list query can be extremely large. To manage large result sets, Amazon S3 uses pagination to split them into multiple responses. Always check the {@link ObjectListing#isTruncated()} method to seeif the returned listing is complete, or if callers need to make additional calls to get more results. Alternatively, use the {@link AmazonS3Client#listNextBatchOfObjects(ObjectListing)} method as aneasy way to get the next page of object listings.
Calling {@link ListObjectsRequest#setDelimiter(String)}sets the delimiter, allowing groups of keys that share the delimiter-terminated prefix to be included in the returned listing. This allows applications to organize and browse their keys hierarchically, similar to how a file system organizes files into directories. These common prefixes can be retrieved through the {@link ObjectListing#getCommonPrefixes()} method.
For example, consider a bucket that contains the following keys:
listObjects with a prefix value of "foo/" and a delimiter value of "/" on this bucket, an ObjectListing is returned that contains one key ("foo/boo") and one entry in the common prefixes list ("foo/bar/"). To see deeper into the virtual hierarchy, make another call to listObjects setting the prefix parameter to any interesting common prefix to list the individual keys under that prefix. The total number of keys in a bucket doesn't substantially affect list performance, nor does the presence or absence of additional request parameters.
Contains options to return a list of summary information about the objects in the specified bucket. Depending on the request parameters, additional information is returned, such as common prefixes if a delimiter was specified. List results are always returned in lexicographic (alphabetical) order.
Buckets can contain a virtually unlimited number of keys, and the complete results of a list query can be extremely large. To manage large result sets, GCS uses pagination to split them into multiple responses. Always check the {@link GcsObjectListing#isTruncated()} method to seeif the returned listing is complete, or if callers need to make additional calls to get more results. Alternatively, use the {@link ApptaniumGcsService#listNextBatchOfObjects(GcsObjectListing)} method as aneasy way to get the next page of object listings.
Calling {@link ListObjectsRequest#setDelimiter(String)}sets the delimiter, allowing groups of keys that share the delimiter-terminated prefix to be included in the returned listing. This allows applications to organize and browse their keys hierarchically, similar to how a file system organizes files into directories. These common prefixes can be retrieved through the {@link GcsObjectListing#getCommonPrefixes()} method.
For example, consider a bucket that contains the following keys:
listObjects with a prefix value of "foo/" and a delimiter value of "/" on this bucket, an ObjectListing is returned that contains one key ("foo/boo") and one entry in the common prefixes list ("foo/bar/"). To see deeper into the virtual hierarchy, make another call to listObjects setting the prefix parameter to any interesting common prefix to list the individual keys under that prefix. The total number of keys in a bucket doesn't substantially affect list performance, nor does the presence or absence of additional request parameters.
| |
| |