You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/src/operations/ddl/create-index.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ Creates a scalar index on a Lance table to accelerate queries.
7
7
8
8
## Overview
9
9
10
-
The `CREATE INDEX` command builds an index on one or more columns of a Lance table. Indexing can improve the performance of queries that filter on the indexed columns. Depending on the index method, Lance Spark either uses a fragment-parallel build path or delegates to Lance's built-in single-phase index creation path.
10
+
The `CREATE INDEX` command builds an index on one or more columns of a Lance table. Indexing can improve the performance of queries that filter on the indexed columns. Depending on the index method, Lance Spark either uses a fragment-parallel build path or a driver-coordinated commit flow after parallel executor builds.
11
11
12
12
## Basic Usage
13
13
@@ -151,12 +151,12 @@ Consider creating an index when:
151
151
152
152
The `CREATE INDEX` command operates as follows:
153
153
154
-
1.**Index Build Execution**: Lance Spark chooses an execution path based on the index method. Methods such as `btree`can use fragment-parallel execution, while `zonemap` is built through Lance's single-phase create-index API.
155
-
2.**Metadata Finalization**: Lance records the new index metadata as part of the index creation flow.
154
+
1.**Index Build Execution**: Lance Spark chooses an execution path based on the index method. Methods such as `btree`, `fts`, and `zonemap`can build physical index segments in parallel across fragments. Range-mode `btree` uses Spark repartitioning and sorted preprocessed data.
155
+
2.**Metadata Finalization**: Lance Spark merges or commits the resulting index metadata on the driver so the new logical index becomes visible atomically.
156
156
3.**Transactional Commit**: A new table version is committed with the new index information. The operation is atomic and ensures that concurrent reads are not affected.
157
157
158
158
## Notes and Limitations
159
159
160
160
-**Index Methods**: The `zonemap`, `btree`, and `fts` methods are supported for scalar index creation.
161
161
-**Zonemap Column Count**: Zonemap indexes currently support a single column only. The generic `CREATE INDEX` grammar accepts a column list, but Lance rejects multi-column zonemap creation.
162
-
-**Index Replacement**: If you create an index with the same name as an existing one, the old index will be replaced by the new one. This is because the underlying implementation uses `replace(true)`.
162
+
-**Index Replacement**: If you create an index with the same name as an existing one, the old index will be replaced by the new one.
0 commit comments