- 2.47.0 (latest)
- 2.46.0
- 2.45.0
- 2.44.0
- 2.43.0
- 2.42.0
- 2.41.0
- 2.40.0
- 2.39.0
- 2.37.0
- 2.36.0
- 2.35.0
- 2.34.0
- 2.33.0
- 2.32.0
- 2.31.0
- 2.30.0
- 2.29.0
- 2.28.0
- 2.27.0
- 2.24.0
- 2.23.0
- 2.22.0
- 2.21.0
- 2.20.0
- 2.19.0
- 2.18.0
- 2.17.0
- 2.16.0
- 2.15.0
- 2.14.0
- 2.13.0
- 2.12.0
- 2.11.0
- 2.9.0
- 2.8.0
- 2.7.0
- 2.6.0
- 2.5.0
- 2.4.0
- 2.3.5
- 2.2.0
- 2.1.13
public interface BatchDocumentOutputConfigOrBuilder extends MessageOrBuilder
Implements
MessageOrBuilderMethods
getDestinationCase()
public abstract BatchDocumentOutputConfig.DestinationCase getDestinationCase()
Returns | |
---|---|
Type | Description |
BatchDocumentOutputConfig.DestinationCase |
getGcsDestination()
public abstract GcsDestination getGcsDestination()
Google Cloud Storage destination for output content. For every single input document (for example, gs://a/b/c.[extension]), we generate at most 2 * n output files. (n is the # of target_language_codes in the BatchTranslateDocumentRequest).
While the input documents are being processed, we write/update an index
file index.csv
under gcs_destination.output_uri_prefix
(for example,
gs://translation_output/index.csv) The index file is generated/updated as
new files are being translated. The format is:
input_document,target_language_code,translation_output,error_output, glossary_translation_output,glossary_error_output
input_document
is one file we matched using gcs_source.input_uri.
target_language_code
is provided in the request.
translation_output
contains the translations. (details provided below)
error_output
contains the error message during processing of the file.
Both translations_file and errors_file could be empty strings if we have
no content to output.
glossary_translation_output
and glossary_error_output
are the
translated output/error when we apply glossaries. They could also be
empty if we have no content to output.
Once a row is present in index.csv, the input/output matching never changes. Callers should also expect all the content in input_file are processed and ready to be consumed (that is, no partial output file is written).
Since index.csv will be keeping updated during the process, please make sure there is no custom retention policy applied on the output bucket that may avoid file updating. (https://cloud.google.com/storage/docs/bucket-lock#retention-policy)
The naming format of translation output files follows (for target
language code [trg]): translation_output
:
gs://translation_output/a_b_c_[trg]translation.[extension]
glossary_translation_output
:
gs://translation_test/a_b_c[trg]_glossary_translation.[extension]
. The
output document will maintain the same file format as the input document.
The naming format of error output files follows (for target language code
[trg]): error_output
: gs://translation_test/a_b_c_[trg]errors.txt
glossary_error_output
:
gs://translation_test/a_b_c[trg]_glossary_translation.txt
. The error
output is a txt file containing error details.
.google.cloud.translation.v3.GcsDestination gcs_destination = 1;
Returns | |
---|---|
Type | Description |
GcsDestination |
The gcsDestination. |
getGcsDestinationOrBuilder()
public abstract GcsDestinationOrBuilder getGcsDestinationOrBuilder()
Google Cloud Storage destination for output content. For every single input document (for example, gs://a/b/c.[extension]), we generate at most 2 * n output files. (n is the # of target_language_codes in the BatchTranslateDocumentRequest).
While the input documents are being processed, we write/update an index
file index.csv
under gcs_destination.output_uri_prefix
(for example,
gs://translation_output/index.csv) The index file is generated/updated as
new files are being translated. The format is:
input_document,target_language_code,translation_output,error_output, glossary_translation_output,glossary_error_output
input_document
is one file we matched using gcs_source.input_uri.
target_language_code
is provided in the request.
translation_output
contains the translations. (details provided below)
error_output
contains the error message during processing of the file.
Both translations_file and errors_file could be empty strings if we have
no content to output.
glossary_translation_output
and glossary_error_output
are the
translated output/error when we apply glossaries. They could also be
empty if we have no content to output.
Once a row is present in index.csv, the input/output matching never changes. Callers should also expect all the content in input_file are processed and ready to be consumed (that is, no partial output file is written).
Since index.csv will be keeping updated during the process, please make sure there is no custom retention policy applied on the output bucket that may avoid file updating. (https://cloud.google.com/storage/docs/bucket-lock#retention-policy)
The naming format of translation output files follows (for target
language code [trg]): translation_output
:
gs://translation_output/a_b_c_[trg]translation.[extension]
glossary_translation_output
:
gs://translation_test/a_b_c[trg]_glossary_translation.[extension]
. The
output document will maintain the same file format as the input document.
The naming format of error output files follows (for target language code
[trg]): error_output
: gs://translation_test/a_b_c_[trg]errors.txt
glossary_error_output
:
gs://translation_test/a_b_c[trg]_glossary_translation.txt
. The error
output is a txt file containing error details.
.google.cloud.translation.v3.GcsDestination gcs_destination = 1;
Returns | |
---|---|
Type | Description |
GcsDestinationOrBuilder |
hasGcsDestination()
public abstract boolean hasGcsDestination()
Google Cloud Storage destination for output content. For every single input document (for example, gs://a/b/c.[extension]), we generate at most 2 * n output files. (n is the # of target_language_codes in the BatchTranslateDocumentRequest).
While the input documents are being processed, we write/update an index
file index.csv
under gcs_destination.output_uri_prefix
(for example,
gs://translation_output/index.csv) The index file is generated/updated as
new files are being translated. The format is:
input_document,target_language_code,translation_output,error_output, glossary_translation_output,glossary_error_output
input_document
is one file we matched using gcs_source.input_uri.
target_language_code
is provided in the request.
translation_output
contains the translations. (details provided below)
error_output
contains the error message during processing of the file.
Both translations_file and errors_file could be empty strings if we have
no content to output.
glossary_translation_output
and glossary_error_output
are the
translated output/error when we apply glossaries. They could also be
empty if we have no content to output.
Once a row is present in index.csv, the input/output matching never changes. Callers should also expect all the content in input_file are processed and ready to be consumed (that is, no partial output file is written).
Since index.csv will be keeping updated during the process, please make sure there is no custom retention policy applied on the output bucket that may avoid file updating. (https://cloud.google.com/storage/docs/bucket-lock#retention-policy)
The naming format of translation output files follows (for target
language code [trg]): translation_output
:
gs://translation_output/a_b_c_[trg]translation.[extension]
glossary_translation_output
:
gs://translation_test/a_b_c[trg]_glossary_translation.[extension]
. The
output document will maintain the same file format as the input document.
The naming format of error output files follows (for target language code
[trg]): error_output
: gs://translation_test/a_b_c_[trg]errors.txt
glossary_error_output
:
gs://translation_test/a_b_c[trg]_glossary_translation.txt
. The error
output is a txt file containing error details.
.google.cloud.translation.v3.GcsDestination gcs_destination = 1;
Returns | |
---|---|
Type | Description |
boolean |
Whether the gcsDestination field is set. |