Google Cloud Discovery Engine V1beta Client - Class GcsSource (0.4.0)

Version 0.4.0

• 0.11.2 (latest)
• 0.11.1
• 0.8.0
• 0.7.1
• 0.6.0
• 0.5.0
• 0.4.0
• 0.3.0
• 0.2.0
• 0.1.1

Beta

This library is covered by the Pre-GA Offerings Terms of the Terms of Service. Pre-GA libraries might have limited support, and changes to pre-GA libraries might not be compatible with other pre-GA versions. For more information, see the launch stage descriptions.

Reference documentation and code samples for the Google Cloud Discovery Engine V1beta Client class GcsSource.

Cloud Storage location for input content.

Generated from protobuf message google.cloud.discoveryengine.v1beta.GcsSource

Namespace

Google \ Cloud \ DiscoveryEngine \ V1beta

Methods

__construct

Constructor.

Parameters
Name	Description
data	array Optional. Data for populating the Message object.
↳ input_uris	array Required. Cloud Storage URIs to input files. URI can be up to 2000 characters long. URIs can match the full object path (for example, gs://bucket/directory/object.json) or a pattern matching one or more files, such as gs://bucket/directory/*.json. A request can contain at most 100 files (or 100,000 files if data_schema is content). Each file can be up to 2 GB (or 100 MB if data_schema is content).
↳ data_schema	string The schema to use when parsing the data from the source. Supported values for document imports: * document (default): One JSON Document per line. Each document must have a valid Document.id. * content: Unstructured data (e.g. PDF, HTML). Each file matched by input_uris will become a document, with the ID set to the first 128 bits of SHA256(URI) encoded as a hex string. * custom: One custom data JSON per row in arbitrary format that conforms the defined Schema of the data store. This can only be used by the GENERIC Data Store vertical. * csv: A CSV file with header conforming the defined Schema of the data store. Each entry after the header will be imported as a Document. This can only be used by the GENERIC Data Store vertical. Supported values for user even imports: * user_event (default): One JSON UserEvent per line.

getInputUris

Required. Cloud Storage URIs to input files. URI can be up to 2000 characters long. URIs can match the full object path (for example, gs://bucket/directory/object.json) or a pattern matching one or more files, such as gs://bucket/directory/*.json.

A request can contain at most 100 files (or 100,000 files if data_schema is content). Each file can be up to 2 GB (or 100 MB if data_schema is content).

Returns
Type	Description
Google\Protobuf\Internal\RepeatedField

setInputUris

Required. Cloud Storage URIs to input files. URI can be up to 2000 characters long. URIs can match the full object path (for example, gs://bucket/directory/object.json) or a pattern matching one or more files, such as gs://bucket/directory/*.json.

A request can contain at most 100 files (or 100,000 files if data_schema is content). Each file can be up to 2 GB (or 100 MB if data_schema is content).

Parameter
Name	Description
var	string[]

Returns
Type	Description
$this

getDataSchema

The schema to use when parsing the data from the source.

Supported values for document imports:

• document (default): One JSON Document per line. Each document must have a valid Document.id.
• content: Unstructured data (e.g. PDF, HTML). Each file matched by input_uris will become a document, with the ID set to the first 128 bits of SHA256(URI) encoded as a hex string.
• custom: One custom data JSON per row in arbitrary format that conforms the defined Schema of the data store. This can only be used by the GENERIC Data Store vertical.
• csv: A CSV file with header conforming the defined Schema of the data store. Each entry after the header will be imported as a Document. This can only be used by the GENERIC Data Store vertical. Supported values for user even imports:
• user_event (default): One JSON UserEvent per line.

Returns
Type	Description
string

setDataSchema

The schema to use when parsing the data from the source.

Supported values for document imports:

• document (default): One JSON Document per line. Each document must have a valid Document.id.
• content: Unstructured data (e.g. PDF, HTML). Each file matched by input_uris will become a document, with the ID set to the first 128 bits of SHA256(URI) encoded as a hex string.
• custom: One custom data JSON per row in arbitrary format that conforms the defined Schema of the data store. This can only be used by the GENERIC Data Store vertical.
• csv: A CSV file with header conforming the defined Schema of the data store. Each entry after the header will be imported as a Document. This can only be used by the GENERIC Data Store vertical. Supported values for user even imports:
• user_event (default): One JSON UserEvent per line.

Parameter
Name	Description
var	string

Returns
Type	Description
$this