- JSON representation
- SearchParams
- SearchResultList
- SearchResult
- UnstructuredDocumentInfo
- DocumentContext
- ExtractiveSegment
- ExtractiveAnswer
- ChunkInfo
- DocumentMetadata
Search specification.
JSON representation |
---|
{ // Union field |
Fields | |
---|---|
Union field input . Search parameters to control the search behavior. Or provide search result list to generate answer. input can be only one of the following: |
|
search |
Search parameters. |
search |
Search result list. |
SearchParams
Search parameters.
JSON representation |
---|
{ "maxReturnResults": integer, "filter": string, "boostSpec": { object ( |
Fields | |
---|---|
max |
Number of search results to return. The default value is 10. |
filter |
The filter syntax consists of an expression language for constructing a predicate from one or more fields of the documents being filtered. Filter expression is case-sensitive. This will be used to filter search results which may affect the Answer response. If this field is unrecognizable, an Filtering in Vertex AI Search is done by mapping the LHS filter key to a key property defined in the Vertex AI Search backend -- this mapping is defined by the customer in their schema. For example a media customers might have a field 'name' in their schema. In this case the filter would look like this: filter --> name:'ANY("king kong")' For more information about filtering including syntax and filter operators, see Filter |
boost |
Boost specification to boost certain documents in search results which may affect the answer query response. For more information on boosting, see Boosting |
order |
The order in which documents are returned. Documents can be ordered by a field in an If this field is unrecognizable, an |
search |
Specifies the search result mode. If unspecified, the search result mode defaults to |
data |
Specs defining dataStores to filter on in a search call and configurations for those dataStores. This is only considered for engines with multiple dataStores use case. For single dataStore within an engine, they should use the specs at the top level. |
natural |
Optional. Specification to enable natural language understanding capabilities for search requests. |
SearchResultList
Search result list.
JSON representation |
---|
{
"searchResults": [
{
object ( |
Fields | |
---|---|
search |
Search results. |
SearchResult
Search result.
JSON representation |
---|
{ // Union field |
Fields | |
---|---|
Union field content . Search result content. content can be only one of the following: |
|
unstructured |
Unstructured document information. |
chunk |
Chunk information. |
UnstructuredDocumentInfo
Unstructured document information.
JSON representation |
---|
{ "document": string, "uri": string, "title": string, "documentContexts": [ { object ( |
Fields | |
---|---|
document |
Document resource name. |
uri |
URI for the document. |
title |
Title. |
document |
List of document contexts. The content will be used for Answer Generation. This is supposed to be the main content of the document that can be long and comprehensive. |
extractive |
List of extractive segments. |
extractiveAnswers[] |
Deprecated: This field is deprecated and will have no effect on the Answer generation. Please use documentContexts and extractiveSegments fields. List of extractive answers. |
DocumentContext
Document context.
JSON representation |
---|
{ "pageIdentifier": string, "content": string } |
Fields | |
---|---|
page |
Page identifier. |
content |
Document content to be used for answer generation. |
ExtractiveSegment
Extractive segment. Guide Answer generation will only use it if documentContexts is empty. This is supposed to be shorter snippets.
JSON representation |
---|
{ "pageIdentifier": string, "content": string } |
Fields | |
---|---|
page |
Page identifier. |
content |
Extractive segment content. |
ExtractiveAnswer
Extractive answer. Guide
JSON representation |
---|
{ "pageIdentifier": string, "content": string } |
Fields | |
---|---|
page |
Page identifier. |
content |
Extractive answer content. |
ChunkInfo
Chunk information.
JSON representation |
---|
{
"chunk": string,
"content": string,
"documentMetadata": {
object ( |
Fields | |
---|---|
chunk |
Chunk resource name. |
content |
Chunk textual content. |
document |
Metadata of the document from the current chunk. |
DocumentMetadata
Document metadata contains the information of the document of the current chunk.
JSON representation |
---|
{ "uri": string, "title": string } |
Fields | |
---|---|
uri |
Uri of the document. |
title |
Title of the document. |