ClickHouse (Bulk)

This page contains the latest information of the releases of RepoDb.ClickHouse.BulkOperations library.

View the NuGet package here or download it directly here.

RepoDb.ClickHouse.BulkOperations (v1.17.0-alpha1)

Released: October 1, 2026

• Adopted the Roslyn and Meziantou static code analyzers across the codebase and applied the resulting fixes — including ConfigureAwait(false) on async calls, ArgumentNullException over NullReferenceException, and other code-quality corrections. #1328 #1331
• Updated the NuGet package icon to the new logo and refreshed the README with a consistent header, description and a link to the get started tutorial.
• Introduced ClickHouseBulkColumnMappingsBehavior (Automatic, Strict, StrictBypass) and the new BulkColumnMappingsBehavior property on ClickHouseBulkDbSetting — opt into fail-fast validation of the source-to-destination column mapping for BulkInsert, BulkMerge, BulkUpdate and BulkDelete when no explicit mappings are passed. #1360
• Referenced the RepoDb package v1.17.0-alpha3.
• Referenced the RepoDb.ClickHouse package v1.17.0-alpha1.

RepoDb.ClickHouse.BulkOperations (v1.16.0)

Released: September 9, 2026

Version bump only, aligning with the RepoDB ecosystem-wide v1.16.0 release — no functional changes since v1.0.0.

• Referenced the RepoDb package v1.16.0.
• Referenced the RepoDb.ClickHouse package v1.16.0.

RepoDb.ClickHouse.BulkOperations (v1.0.0)

Released: September 8, 2026

First general availability (non-preview) release of the ClickHouse Bulk Operations package, promoting the preview below to stable v1.0.0. No functional changes since the preview — see that entry for the full feature set and known limitations.

RepoDb.ClickHouse.BulkOperations - Preview

Released: 2026-08-30

New

First release of the bulk operations extension for RepoDb.ClickHouse, providing BulkInsert, BulkMerge, BulkUpdate, BulkDelete, and BulkDeleteByKey, each with an Async overload, callable against a ClickHouseConnection, a table name, or a DataTable. #1242

What’s included

• BulkInsert, BulkMerge, BulkUpdate, BulkDelete, and BulkDeleteByKey — matched by qualifiers or primary key; see Operations (ClickHouse) for the full SQL generated by each.
• An internal ClickHouseBulkCopy class, adapting ClickHouse.Driver’s own native Copy.ClickHouseBulkCopy to the ColumnMappings-based API the rest of the library expects.
• ClickHouseBulkImportIdentityBehavior (KeepIdentity default; ReturnIdentity always throws NotSupportedException, since ClickHouse has no identity/scope-identity mechanism).
• ClickHouseBulkImportPseudoTableType (Auto, Memory, Physical) — selects the staging-table strategy backing BulkMerge/BulkUpdate/BulkDelete/BulkDeleteByKey. BulkInsert never uses a pseudo table.
• ClickHouseBulkInsertMapItem — explicit source-to-destination column mapping for BulkInsert/BulkMerge/BulkUpdate, with an optional explicit ClickHouse type name override.
• ClickHouseBulkDbSetting and IClickHouseBulkDbSetting — a ClickHouseDbSetting subclass (and its interface) adding IsWaitForMutationsEnabled, which BulkMerge/BulkUpdate/BulkDelete consult to decide whether to block until their ALTER TABLE mutation completes. Not registered by default — pass an instance to UseClickHouse() or register it via DbSettingMapper to opt in.
• Referenced the RepoDb package.
• Referenced the RepoDb.ClickHouse package.
• Referenced the ClickHouse.Driver package v1.3.0.

Known limitations (v1)

• ClickHouseBulkImportPseudoTableType.Auto and Memory both currently resolve to Physical regardless of row count — the internal resolution logic returns Physical on every outcome, so the session-private Memory-engine staging path is implemented but not yet exercised.
• BulkMerge, BulkUpdate, BulkDelete and BulkDeleteByKey report the number of rows staged into the pseudo table, not a confirmed post-mutation count — ALTER TABLE ... UPDATE/DELETE are asynchronous mutations, and neither they nor a plain INSERT report a reliable affected-row figure through ClickHouse.Driver.
• Every bulk call against BulkMerge/BulkUpdate/BulkDelete/BulkDeleteByKey creates its own physical staging table (DROP TABLE IF EXISTS + CREATE TABLE ... ENGINE = MergeTree ORDER BY tuple() AS SELECT ... WHERE (1 = 0)) and drops it once the call completes, rather than reusing one across calls.
• BulkInsert/BulkMerge never return generated identity values — identityBehavior: ReturnIdentity always throws NotSupportedException.