[**@lancedb/lancedb**](../README.md) • **Docs** *** [@lancedb/lancedb](../globals.md) / QueryExecutionOptions # Interface: QueryExecutionOptions Options that control the behavior of a particular query execution ## Properties ### blobMode? ```ts optional blobMode: BlobMode; ``` How to return blob v2 columns. Applies to `toArrow()` and `toArray()`. - `"descriptions"` (default): each blob is a descriptor. Read the bytes with [Table.fetchBlobs](../classes/Table.md#fetchblobs) or [Table.fetchBlobFiles](../classes/Table.md#fetchblobfiles). - `"bytes"`: each blob column, including blobs nested in structs, holds the bytes as `LargeBinary`. The query also reads `_rowid` to fetch them, and leaves it out of the result unless [QueryBase.withRowId](../classes/QueryBase.md#withrowid) was called. All the bytes are held in memory. Selecting a parent struct or directly aliasing a blob or struct also returns bytes. Blobs inside lists keep their descriptors. Arbitrary projection expressions are not materialized as bytes. The rows and bytes come from the same snapshot. Remote queries require authoritative query version and snapshot identity headers, verified again by the blob response. Older servers can still return `"descriptions"`. Local queries retry up to three times if the table changes while they run. #### Example ```ts const rows = await table .query() .select(["id", "image"]) .toArray({ blobMode: "bytes" }); const image: Uint8Array | null = rows[0].image; ``` *** ### maxBatchLength? ```ts optional maxBatchLength: number; ``` The maximum number of rows to return in a single batch Batches may have fewer rows if the underlying data is stored in smaller chunks. *** ### timeoutMs? ```ts optional timeoutMs: number; ``` Timeout for query execution in milliseconds The timeout also covers reading the results, so consuming them slowly can exceed it.