kQjrddlmZddlmZddlmZmZmZmZddl m Z er ddl m Z ddl mZGdd eZy ) ) annotations) timedelta) TYPE_CHECKINGListOptionalUnion)Expr)DATA)MergeInsertResultceZdZdZd dZdd d dZddZ d ddZddZdd Z dd Z d dd Z y)LanceMergeInsertBuilderzBuilder for a LanceDB merge insert operation See [`merge_insert`][lancedb.table.Table.merge_insert] for more context c||_||_d|_d|_d|_d|_d|_d|_d|_d|_ d|_ d|_ y)NFT) _table_on_when_matched_update_all"_when_matched_update_all_condition_when_not_matched_insert_all"_when_not_matched_by_source_delete%_when_not_matched_by_source_condition*_when_not_matched_by_source_condition_expr_timeout _use_index_use_rte_validate_single_shard)selftableons R/home/oem/CyberBrain26-unified/.venv/lib/python3.12/site-packages/lancedb/merge.py__init__z LanceMergeInsertBuilder.__init__s_ (-%26/,1)27/592:>7  &*#N)wherec"d|_||_|S)a Rows that exist in both the source table (new data) and the target table (old data) will be updated, replacing the old row with the corresponding matching row. If there are multiple matches then the behavior is undefined. Currently this causes multiple copies of the row to be created but that behavior is subject to change. Parameters ---------- where: Optional[str], default None An optional filter to limit which rows are updated. Column references in this expression must be prefixed with "target." to refer to the existing table data. For example, to only update rows where the existing color is red, use: ``where="target.color = 'red'"`` T)rr)rr"s rwhen_matched_update_allz/LanceMergeInsertBuilder.when_matched_update_all+s*)-%27/ r!cd|_|S)zw Rows that exist only in the source table (new data) should be inserted into the target table. T)r)rs rwhen_not_matched_insert_allz3LanceMergeInsertBuilder.when_not_matched_insert_allDs -1) r!cd|_t|tr|j|_d|_|S||_d|_|S)aP Rows that exist only in the target table (old data) will be deleted. An optional condition can be provided to limit what data is deleted. Parameters ---------- condition: str or :class:`~lancedb.expr.Expr` or None, default None If None then all such rows will be deleted. Otherwise the condition will be used as a filter to limit what rows are deleted. Can be a SQL string or a type-safe :class:`~lancedb.expr.Expr` built with :func:`~lancedb.expr.col` and :func:`~lancedb.expr.lit`. TN)r isinstancer _innerrr)r conditions r!when_not_matched_by_source_deletez9LanceMergeInsertBuilder.when_not_matched_by_source_deleteLsK 37/ i &>G>N>ND ;9=D 6 :CD 6>BD ; r!c||_|S)a Controls whether to use indexes for the merge operation. When set to `True` (the default), the operation will use an index if available on the join key for improved performance. When set to `False`, it forces a full table scan even if an index exists. This can be useful for benchmarking or when the query optimizer chooses a suboptimal path. Parameters ---------- use_index: bool Whether to use indices for the merge operation. Defaults to `True`. )r)r use_indexs rr-z!LanceMergeInsertBuilder.use_indexes$ r!c||_|S)a Control RTE routing for this merge. By default (unset), a `merge_insert` on a table with an RTE write spec is routed through Lance's MemWAL shard writer, and a table without one uses the standard path. Parameters ---------- enable: bool ``True`` forces RTE routing and errors if the table has no RTE write spec. ``False`` forces the standard write path even when a spec is set. )r)renables ruse_rtezLanceMergeInsertBuilder.use_rtevs  r!c||_|S)u Controls how an LSM merge checks that its input targets a single shard. When a table has an RTE write spec, every row in a `merge_insert` call must route to the same shard. When `True` (the default), every row is inspected to verify this. When `False`, only the first row is inspected and the shard it routes to is used for the whole input — a faster path for callers that have already pre-sharded their input. Has no effect on tables without an RTE write spec. Parameters ---------- validate_single_shard: bool Whether to check every row routes to one shard. Defaults to `True`. )r)rvalidate_single_shards rr2z-LanceMergeInsertBuilder.validate_single_shards&'<# r!cP|||_|jj||||S)a Executes the merge insert operation Nothing is returned but the [`Table`][lancedb.table.Table] is updated Parameters ---------- new_data: DATA New records which will be matched against the existing records to potentially insert or update into the table. This parameter can be anything you use for [`add`][lancedb.table.Table.add] on_bad_vectors: str, default "error" What to do if any of the vectors are not the same size or contains NaNs. One of "error", "drop", "fill". fill_value: float, default 0. The value to use when filling vectors. Only used if on_bad_vectors="fill". timeout: Optional[timedelta], default None Maximum time to run the operation before cancelling it. By default, there is a 30-second timeout that is only enforced after the first attempt. This is to prevent spending too long retrying to resolve conflicts. For example, if a write attempt takes 20 seconds and fails, the second attempt will be cancelled after 10 seconds, hitting the 30-second timeout. However, a write that takes one hour and succeeds on the first attempt will not be cancelled. When this is set, the timeout is enforced on all attempts, including the first. Returns ------- MergeInsertResult version: the new version number of the table after doing merge insert. )rr _do_merge)rnew_dataon_bad_vectors fill_valuetimeouts rexecutezLanceMergeInsertBuilder.executes-R  #DM{{$$T8^ZPPr!)rz'Table'rz List[str])r"z Optional[str]returnr)r:r)N)r*zUnion[str, Expr, None]r:r)r-boolr:r)r/r;r:r)r2r;r:r)errorgN) r5r r6strr7floatr8zOptional[timedelta]r:r ) __name__ __module__ __qualname____doc__r r$r&r+r-r0r2r9r!rrrs +$)-% 237/ 2"$%) 2&'+ +Q+Q+Q +Q % +Q  +Qr!rN) __future__rdatetimertypingrrrrexprr commonr _lancedbr objectrrCr!rrKs1 #77 vQfvQr!