mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-08 02:25:19 +00:00
gcloud: Wed Sep 20 10:45:25 UTC 2023
This commit is contained in:
parent
952686eb78
commit
54eca12593
183 changed files with 2246 additions and 4040 deletions
|
|
@ -1266,6 +1266,26 @@ AVAILABLE PROPERTIES
|
|||
the default storage class and retention period for the destination
|
||||
bucket meet the criteria for parallel composite upload.
|
||||
|
||||
parallel_composite_upload_component_prefix
|
||||
The prefix used when naming temporary components created by
|
||||
composite uploads. If the prefix begins with a /, the temporary
|
||||
components are uploaded relative to the bucket name. If the prefix
|
||||
does not begin with a /, the temporary components are uploaded
|
||||
relative to the prefix portion of the destination object name. For
|
||||
example, consider an upload that will create a final object named
|
||||
gs://bucket/dir1/dir2/object. Using a prefix of /prefix means
|
||||
temporary components use names like
|
||||
gs://bucket/prefix/COMPONENT_NAME. Using a prefix of prefix means
|
||||
temporary components use names like
|
||||
gs://bucket/dir1/dir2/prefix/COMPONENT_NAME. Note that this can
|
||||
complicate cleaning up temporary components, as they will not all
|
||||
share a common prefix. If this property is not specified, gcloud
|
||||
storage uses the prefix
|
||||
/gcloud/tmp/parallel_composite_uploads/see_gcloud_storage_cp_help_for_details/.
|
||||
If a chosen prefix results in temporary component names longer than
|
||||
the maximum length Cloud Storage allows, gcloud storage performs a
|
||||
non-composite upload.
|
||||
|
||||
parallel_composite_upload_component_size
|
||||
Specifies the ideal size of a component in bytes, which will act as
|
||||
an upper bound to the size of the components if ceil(file_size /
|
||||
|
|
|
|||
|
|
@ -1298,6 +1298,26 @@ AVAILABLE PROPERTIES
|
|||
the default storage class and retention period for the destination
|
||||
bucket meet the criteria for parallel composite upload.
|
||||
|
||||
parallel_composite_upload_component_prefix
|
||||
The prefix used when naming temporary components created by
|
||||
composite uploads. If the prefix begins with a /, the temporary
|
||||
components are uploaded relative to the bucket name. If the prefix
|
||||
does not begin with a /, the temporary components are uploaded
|
||||
relative to the prefix portion of the destination object name. For
|
||||
example, consider an upload that will create a final object named
|
||||
gs://bucket/dir1/dir2/object. Using a prefix of /prefix means
|
||||
temporary components use names like
|
||||
gs://bucket/prefix/COMPONENT_NAME. Using a prefix of prefix means
|
||||
temporary components use names like
|
||||
gs://bucket/dir1/dir2/prefix/COMPONENT_NAME. Note that this can
|
||||
complicate cleaning up temporary components, as they will not all
|
||||
share a common prefix. If this property is not specified, gcloud
|
||||
storage uses the prefix
|
||||
/gcloud/tmp/parallel_composite_uploads/see_gcloud_storage_cp_help_for_details/.
|
||||
If a chosen prefix results in temporary component names longer than
|
||||
the maximum length Cloud Storage allows, gcloud storage performs a
|
||||
non-composite upload.
|
||||
|
||||
parallel_composite_upload_component_size
|
||||
Specifies the ideal size of a component in bytes, which will act as
|
||||
an upper bound to the size of the components if ceil(file_size /
|
||||
|
|
|
|||
|
|
@ -1310,6 +1310,26 @@ AVAILABLE PROPERTIES
|
|||
the default storage class and retention period for the destination
|
||||
bucket meet the criteria for parallel composite upload.
|
||||
|
||||
parallel_composite_upload_component_prefix
|
||||
The prefix used when naming temporary components created by
|
||||
composite uploads. If the prefix begins with a /, the temporary
|
||||
components are uploaded relative to the bucket name. If the prefix
|
||||
does not begin with a /, the temporary components are uploaded
|
||||
relative to the prefix portion of the destination object name. For
|
||||
example, consider an upload that will create a final object named
|
||||
gs://bucket/dir1/dir2/object. Using a prefix of /prefix means
|
||||
temporary components use names like
|
||||
gs://bucket/prefix/COMPONENT_NAME. Using a prefix of prefix means
|
||||
temporary components use names like
|
||||
gs://bucket/dir1/dir2/prefix/COMPONENT_NAME. Note that this can
|
||||
complicate cleaning up temporary components, as they will not all
|
||||
share a common prefix. If this property is not specified, gcloud
|
||||
storage uses the prefix
|
||||
/gcloud/tmp/parallel_composite_uploads/see_gcloud_storage_cp_help_for_details/.
|
||||
If a chosen prefix results in temporary component names longer than
|
||||
the maximum length Cloud Storage allows, gcloud storage performs a
|
||||
non-composite upload.
|
||||
|
||||
parallel_composite_upload_component_size
|
||||
Specifies the ideal size of a component in bytes, which will act as
|
||||
an upper bound to the size of the components if ceil(file_size /
|
||||
|
|
|
|||
|
|
@ -1313,6 +1313,26 @@ AVAILABLE PROPERTIES
|
|||
the default storage class and retention period for the destination
|
||||
bucket meet the criteria for parallel composite upload.
|
||||
|
||||
parallel_composite_upload_component_prefix
|
||||
The prefix used when naming temporary components created by
|
||||
composite uploads. If the prefix begins with a /, the temporary
|
||||
components are uploaded relative to the bucket name. If the prefix
|
||||
does not begin with a /, the temporary components are uploaded
|
||||
relative to the prefix portion of the destination object name. For
|
||||
example, consider an upload that will create a final object named
|
||||
gs://bucket/dir1/dir2/object. Using a prefix of /prefix means
|
||||
temporary components use names like
|
||||
gs://bucket/prefix/COMPONENT_NAME. Using a prefix of prefix means
|
||||
temporary components use names like
|
||||
gs://bucket/dir1/dir2/prefix/COMPONENT_NAME. Note that this can
|
||||
complicate cleaning up temporary components, as they will not all
|
||||
share a common prefix. If this property is not specified, gcloud
|
||||
storage uses the prefix
|
||||
/gcloud/tmp/parallel_composite_uploads/see_gcloud_storage_cp_help_for_details/.
|
||||
If a chosen prefix results in temporary component names longer than
|
||||
the maximum length Cloud Storage allows, gcloud storage performs a
|
||||
non-composite upload.
|
||||
|
||||
parallel_composite_upload_component_size
|
||||
Specifies the ideal size of a component in bytes, which will act as
|
||||
an upper bound to the size of the components if ceil(file_size /
|
||||
|
|
|
|||
|
|
@ -1274,6 +1274,26 @@ AVAILABLE PROPERTIES
|
|||
the default storage class and retention period for the destination
|
||||
bucket meet the criteria for parallel composite upload.
|
||||
|
||||
parallel_composite_upload_component_prefix
|
||||
The prefix used when naming temporary components created by
|
||||
composite uploads. If the prefix begins with a /, the temporary
|
||||
components are uploaded relative to the bucket name. If the prefix
|
||||
does not begin with a /, the temporary components are uploaded
|
||||
relative to the prefix portion of the destination object name. For
|
||||
example, consider an upload that will create a final object named
|
||||
gs://bucket/dir1/dir2/object. Using a prefix of /prefix means
|
||||
temporary components use names like
|
||||
gs://bucket/prefix/COMPONENT_NAME. Using a prefix of prefix means
|
||||
temporary components use names like
|
||||
gs://bucket/dir1/dir2/prefix/COMPONENT_NAME. Note that this can
|
||||
complicate cleaning up temporary components, as they will not all
|
||||
share a common prefix. If this property is not specified, gcloud
|
||||
storage uses the prefix
|
||||
/gcloud/tmp/parallel_composite_uploads/see_gcloud_storage_cp_help_for_details/.
|
||||
If a chosen prefix results in temporary component names longer than
|
||||
the maximum length Cloud Storage allows, gcloud storage performs a
|
||||
non-composite upload.
|
||||
|
||||
parallel_composite_upload_component_size
|
||||
Specifies the ideal size of a component in bytes, which will act as
|
||||
an upper bound to the size of the components if ceil(file_size /
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue