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
Incremental loads: refresh.mode: incremental merges only the rows changed since the last run
into each table with a primary key (DuckDB MERGE INTO ... UPDATE BY NAME / INSERT BY NAME), and refresh.detect_deletes (default on) removes rows whose key is gone. Primary keys come from the
driver's ADBC GetObjects metadata. Oracle finds changed rows with ORA_ROWSCN against the
previous run's snapshot SCN (commit-ordered, so late commits and RAC sequence caches can't
cause misses). Tables without a usable key, and sources without change tracking, keep changed-mode behavior; plan says which is which.
Fixed
Stopping a run (SIGINT, or the SIGTERM Kubernetes sends when it evicts a pod) cancelled at most
the main thread's statement, or none: killed mid-load, the process left GizmoSQL sessions
holding open transactions, and the next run's replace of those tables failed with "Catalog
write-write conflict". Now every in-flight statement in every worker is cancelled, the run is
logged as interrupted (exit 130/143) and notifications fire.