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/docs/core/flow_def.mdx
+4-2
Original file line number
Diff line number
Diff line change
@@ -259,8 +259,10 @@ Export must happen at the top level of a flow, i.e. not within any child scopes
259
259
260
260
*`name`: the name to identify the export target.
261
261
*`target_spec`: the storage spec as the export target.
262
-
*`primary_key_fields` (optional): the fields to be used as primary key. Types of the fields must be supported as key fields. See [Key Types](data_types#key-types) for more details.
263
-
*`vector_index` (optional): the fields to create vector index. Each item is a tuple of a field name and a similarity metric. See [Vector Type](data_types#vector-type) for more details about supported similarity metrics.
262
+
*`primary_key_fields` (`Sequence[str]`): the fields to be used as primary key. Types of the fields must be supported as key fields. See [Key Types](data_types#key-types) for more details.
263
+
*`vector_indexes` (`Sequence[VectorIndexDef]`, optional): the fields to create vector index. `VectorIndexDef` has the following fields:
264
+
*`field_name`: the field to create vector index.
265
+
*`metric`: the similarity metric to use. See [Vector Type](data_types#vector-type) for more details about supported similarity metrics.
264
266
*`setup_by_user` (optional):
265
267
whether the export target is setup by user.
266
268
By default, CocoIndex is managing the target setup (surfaced by the `cocoindex setup` CLI subcommand), e.g. create related tables/collections/etc. with compatible schema, and update them upon change.
0 commit comments