• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

supabase / etl / 44674430984
79%

Build:
DEFAULT BRANCH: main
Ran 20 Nov 2026 04:33AM UTC
Jobs 1
Files 273
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

20 Nov 2026 04:26AM UTC coverage: 78.537% (+0.03%) from 78.505%
44674430984

push

github

web-flow
perf(ducklake): set writer options in one commit (#1287)

* perf(ducklake): set writer options in one commit

Every DuckLake connection setup runs four `set_option` calls for the
Parquet writer settings. Outside a transaction, each call commits to
the catalog on its own. In prod this phase (`configure_parquet`) takes
5.8 s at the median and 14.2 s at p90 per connection setup, about
1.4 s per catalog commit.

Wrap the four calls in one transaction, so they are written in a
single catalog commit.

Measured on a local Postgres catalog: catalog transactions for one
connection setup went from 77 (3 runs) to 65 (65, 71, 65 in 3 runs).
Each DuckLake commit takes about four catalog transactions, so three
fewer commits save about twelve.

New integration test checks that connection setup stores the options
in the catalog. It fails if the transaction is not committed.
DuckLake tests: 308 passed.

* refactor(ducklake): share the writer options builder

`etl-maintenance` kept its own copy of `configure_parquet_settings_sql`,
still issuing four bare `set_option` calls. Its connection setup runs
that step for every pooled connection, so the single-commit change did
not reach the maintenance runner.

Move the builder into `etl_maintenance::ducklake::writer_options`, next
to the already shared `duckdb_version_check_sql`, and call it from both
the destination and the runner. The catalog name is a parameter, since
each crate keeps its own `LAKE_CATALOG`. The duplicated option
constants go away, and the destination's SQL-text checks for these
options are covered by the shared builder's tests.

DuckLake unit tests: 250 passed. DuckLake integration tests, including
the ones that run maintenance: 97 passed.

35 of 35 new or added lines in 3 files covered. (100.0%)

15 existing lines in 5 files now uncovered.

62702 of 79838 relevant lines covered (78.54%)

58729.3 hits per line

Coverage Regressions

Lines Coverage ∆ File
6
91.5
0.96% crates/etl-destinations/src/ducklake/encoding.rs
5
90.29
-0.16% crates/etl/src/replication/apply/mod.rs
2
89.84
-0.52% crates/etl/src/runtime/table_sync/worker.rs
1
98.26
-0.22% crates/etl-destinations/src/ducklake/schema.rs
1
87.27
-0.21% crates/etl-postgres/src/tokio/test_utils.rs
Jobs
ID Job ID Ran Files Coverage
1 44674430984.1 20 Nov 2026 04:33AM UTC 273
78.54
GitHub Action Run
Source Files on build 44674430984
  • Tree
  • List 273
  • Changed 11
  • Source Changed 2
  • Coverage Changed 11
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #44674430984
  • 7a75cbdd on github
  • Prev Build on main (#44555919278)
  • Next Build on main (#44704739944)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc