Intelligent query rewriting

The tech preview release of Intelligent Query Rewriting enhances search precision by automatically generating metadata filter expressions from natural language queries. This enables users to retrieve highly relevant information without needing to understand or apply metadata filters manually.

For example, a user searches for “What was Apple’s revenue last year?”, and Intelligent Query Rewriting automatically generates a filter like doc.ticker = 'aapl' AND doc.year = 2023 to refine the search results.

You enable intelligent query rewriting on a per-query basis by setting the intelligent_query_rewriting parameter to true in the search request. .

Supported API endpoints (beta)

• Simple Single Corpus Query. Set the intelligent_query_rewriting parameter in the query string. For other endpoints, include it in the request body.
• Advanced Single Corpus Query
• Multiple Corpora Query

Example intelligent query rewriting request and response

Consider a corpus containing movie data with the metadata filter attribute: doc.production_country (Text)

1. A user submits the following query:
   What are some of the highest grossing movies made in US, UK, or India?
2. Intelligent Query Rewriting processes the query by extracting the following metadata filters:
   doc.production_country IN ('United States of America', 'United Kingdom', 'India')
3. Rephrasing the query removes the filter context:
   What are some of the highest grossing movies?

EXAMPLE REQUEST

Code example with json syntax.json

1

EXAMPLE RESPONSE

Code example with json syntax.json

1

If an error occurs during filter extraction, Intelligent Query Rewriting is aborted for the affected corpus, and the original query is executed. A warning message is returned in the response.

Example error response

EXAMPLE ERROR RESPONSE

Code example with json syntax.json

1

Behavior with existing metadata filters in requests

If the request already contains a metadata_filter and you enable intelligent_query_rewriting, the extracted filter combines with the provided filter using a logical AND.

EXAMPLE REQUEST WITH METADATA FILTER

Code example with json syntax.json

1

EXAMPLE RESPONSE

Code example with json syntax.json

1

Define filter attributes clearly

Providing detailed descriptions of filter attributes improves filter extraction and search accuracy. To ensure intelligent query rewriting works correctly with metadata filters, you must document the expected value format in the description of the filter. For example:

"description": "Company name in ALL CAPS (e.g., MICROSOFT, INTEL, GOOGLE)"

Consider including the following information:

• Content and format descriptions Explain the purpose and structure of each attribute.
  doc.production_country (Text): The production country of a movie.
• Possible values
  For text attributes, list possible values where applicable.
  • direction: Specifies the compass direction. Possible values: [NORTH, SOUTH, EAST, WEST].
  • color: Indicates product color. Possible values: [WHITE, BLACK, GREY].
• Case sensitivity
  Specify if values are case-sensitive, such as all lowercase or PascalCase.
• Value format
  Indicate whether values use abbreviations (USA, UK) or full names (United States of America).

Handling date attributes

While date attributes are not fully supported, they can function as text attributes if stored in the format YYYY-MM-DD. This allows comparison operators (<, >) to work effectively.

doc.release_date = '2024-02-06'