本页尚未翻译

本页内容仍为英文原文，源自官方文档 basics/limits。中文翻译正在分批进行中。

Limits

Find fixed constraints, configurable bounds and what happens when you reach them.

This page lists limits for job events, SQL error reports, sampling and full-text indexing. Each table identifies the affected API and what happens when a request reaches its limit. SQL and server job limits apply to Enterprise.

Naming Rules is the reference for name lengths, characters and namespace depth. Client and server versions can differ in which rules they enforce.

Fixed API limits

Operation	Scope	Limit and behavior
Job event retrieval	Enterprise	At most 10,000 rows per response. Results can be truncated without a truncation indicator.
SHOW ERRORS ... LIMIT	Enterprise SQL	Accepts 1 through 100,000. Values outside the range are rejected.
SHOW ERRORS without FOR JOB	Enterprise SQL	Inspects up to the 32 most recent failed jobs. Use FOR JOB to inspect a specific job.
Percentage sampling	Enterprise SQL	TABLESAMPLE accepts percentages from 0 through 100. Values outside the range are rejected.
Row-count sampling	Enterprise SQL	TABLESAMPLE (... ROWS) requires a whole number.

See SQL job commands and Sampling for syntax and restrictions on supported table types.

Data-type and index constraints belong to the operation you choose. Check Data types and Vector indexes before choosing a schema or index. For materialized views, confirm your source table meets your deployment's requirements with your administrator before creating one over it.

Configurable limits

Setting	What it controls
Job event limit	Requests more or fewer event rows. The default is 1,000; the 10,000-row maximum still applies.
FTS max_token_length	The maximum indexed token length. The default is 40; longer tokens are excluded from the index.
Enterprise capacity and quotas	Storage, request rate and concurrency are governed by your deployment's resources and configuration. Confirm these with your administrator or LanceDB support.

Handling rejected or incomplete results

• Rejected requests: correct the input before retrying, such as a sampling percentage outside the accepted range.
• Truncated responses: do not assume that a returned event list is the full history. Increasing limit cannot exceed the maximum; use filters to narrow the events you inspect.
• Excluded data: an FTS token-length setting can affect which words are searchable. Choose it for your text and indexing requirements.

Learn more

• Naming Rules: choose portable names and paths.
• Job Framework: track work and inspect events.
• Full-text indexes: configure tokenization.
• SQL and SDKs: check interface support.
• Enterprise support: discuss deployment capacity.