Duckdb 1.4.0 Lts

Posted4 months agoActive4 months ago

whyho

71 points

7 comments

duckdb.orgTechstory

supportivepositive

Debate

20/100

DuckdbDatabase ManagementData AnalysisLts Release

Key topics

Duckdb

Database Management

Data Analysis

Lts Release

The release of DuckDB 1.4.0 LTS brings new features and a commitment to Long Term Support, sparking discussion around the implications of LTS and new features like interpolation and Iceberg write capabilities.

Snapshot generated from the HN discussion

Discussion Activity

Light discussion

First comment

Peak period

3-4h

Avg / period

1.2

Key moments

01Story posted
Sep 16, 2025 at 7:01 AM EDT
4 months ago
Step 01
02First comment
Sep 16, 2025 at 9:24 AM EDT
2h after posting
Step 02
03Peak activity
2 comments in 3-4h
Hottest window of the conversation
Step 03
04Latest activity
Sep 16, 2025 at 4:11 PM EDT
4 months ago
Step 04

Generating AI Summary...

Analyzing up to 500 comments to identify key contributors and discussion patterns

Discussion (7 comments)

Showing 7 comments

ZeroCool2u

4 months ago

2 replies

The Fill function for interpolation is really nice, but there's so many different ways to perform interpolation I'd like a lot more detail on what methods are available and which is used by default.

tanelpoder

4 months ago

1 reply

Indeed. Previously, when computing latency histograms from sampled events, I've abused DuckDB SQL cross join/cartesian products to generate zero values for "empty buckets" within a single SQL statement [1]. But makes the SQL unnecessarily complex & slower too, so I quickly moved that empty bucket rendering functionality to the frontend...

[1]: Example DuckDB SQL with generated bucket lists and cross join + outer join: https://github.com/tanelpoder/0xtools/blob/master/tools/sql/...

hawkfish-rmgw

4 months ago

Feature author here. The new FILL uses linear interpolation (and extrapolation at the ends). There were a bunch of other algorithms requested (e.g., cubic splines), but the syntax was not clear.

I think the real solution is to add support for non-aggregate window functions in the catalogue. Right now, they are all hard-coded, but if they were extensible, there are a number applications in addition to filling that could be supported.

geysersam

4 months ago

You can always manually define your interpolation:

  coalesce(x, (lag(x, 1)+lag(x, -1))/2)

is kind of the same as fill.

From there you can go crazy and define whatever insane interpolations you want.

One limitation is that you can't distinguish the data boundaries from missing values (nulls at the edges vs. nulls in the bulk).

I guess another limitation is if you have multiple nulls after each other...

datadrivenangel

4 months ago

LTS is a move in the right direction. One year is somewhat short, but with no backwards breaking changes that's fine.

zui

4 months ago

Awesome that the iceberg write is now possible from duckdb!

https://github.com/duckdb/duckdb-iceberg

e12e

4 months ago

> Starting with this release, every other DuckDB version is going to be a Long Term Support (LTS) edition. For LTS DuckDB versions, community support will last a year after the release (for now). DuckDB Labs is also starting to offer support for older LTS versions after their community support has expired.

A fixed date is great - but it's difficult to see a single year as "long term" support.

Will be interesting to what commercial support options will emerge.

View full discussion on Hacker News

ID: 45260611Type: storyLast synced: 11/20/2025, 3:44:06 PM

Want the full context?

Jump to the original sources

Read the primary article or dive into the live Hacker News thread when you're ready.

Open link View on HN