Skip to content

ducklake_flush_inlined_data make time-travel inconsistent #673

@qsliu2017

Description

@qsliu2017

What happens?

ducklake_flush_inlined_data only flush visible rows of inline table at the version of flush, making time-travel inconsistent.

To Reproduce

attach 'ducklake:my_ducklake.ducklake' as my_ducklake;
use my_ducklake;
create table t1 (a int);
CALL my_ducklake.set_option('data_inlining_row_limit', 50, table_name => 't1');
insert into t1 values (1), (2), (3);
delete from t1 where a = 2;

from t1 at (version => 2);

CALL ducklake_flush_inlined_data('my_ducklake');

-- this result is inconsistent
from t1 at (version => 2);

OS:

N/A

DuckDB Version:

bea03d5c8bfb130994d97852b185f84520cfb6db

DuckLake Version:

f7d151e

DuckDB Client:

cli

Hardware:

No response

Full Name:

qsliu

Affiliation:

zbyte, inc.

What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.

I have tested with a source build

Did you include all relevant data sets for reproducing the issue?

Yes

Did you include all code required to reproduce the issue?

  • Yes, I have

Did you include all relevant configuration (e.g., CPU architecture, Python version, Linux distribution) to reproduce the issue?

  • Yes, I have

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions