DocumentArgs constructor

const DocumentArgs({ required Input<String> branchId, required Input<String> collectionId, Input<GoogleCloudDiscoveryengineV1alphaDocumentContent>? content, required Input<String> dataStoreId, required Input<String> documentId, Input<String>? id, Input<String>? jsonData, Input<String>? location, Input<String>? name, Input<String>? parentDocumentId, Input<String>? project, Input<String>? schemaId, Input<Map<String, String>>? structData, })

Creates a new DocumentArgs. branchId Required. collectionId Required. content The unstructured data linked to this document. Content must be set if this document is under a CONTENT_REQUIRED data store. dataStoreId Required. documentId Required. The ID to use for the Document, which will become the final component of the Document.name. If the caller does not have permission to create the Document, regardless of whether or not it exists, a PERMISSION_DENIED error is returned. This field must be unique among all Documents with the same parent. Otherwise, an ALREADY_EXISTS error is returned. This field must conform to RFC-1034 standard with a length limit of 63 characters. Otherwise, an INVALID_ARGUMENT error is returned. id Immutable. The identifier of the document. Id should conform to RFC-1034 standard with a length limit of 63 characters. jsonData The JSON string representation of the document. It should conform to the registered Schema or an INVALID_ARGUMENT error is thrown. location Optional. name Immutable. The full resource name of the document. Format: projects/{project}/locations/{location}/collections/{collection}/dataStores/{data_store}/branches/{branch}/documents/{document_id}. This field must be a UTF-8 encoded string with a length limit of 1024 characters. parentDocumentId The identifier of the parent document. Currently supports at most two level document hierarchy. Id should conform to RFC-1034 standard with a length limit of 63 characters. project Optional. schemaId The identifier of the schema located in the same data store. structData The structured JSON data for the document. It should conform to the registered Schema or an INVALID_ARGUMENT error is thrown.

Implementation

const DocumentArgs({
  required this.branchId,
  required this.collectionId,
  this.content,
  required this.dataStoreId,
  required this.documentId,
  this.id,
  this.jsonData,
  this.location,
  this.name,
  this.parentDocumentId,
  this.project,
  this.schemaId,
  this.structData,
});