Skip to content

feat: introduce time travel for data fusion#195

Merged
XiaoHongbo-Hope merged 6 commits intoapache:mainfrom
JingsongLi:timeTravel
Apr 3, 2026
Merged

feat: introduce time travel for data fusion#195
XiaoHongbo-Hope merged 6 commits intoapache:mainfrom
JingsongLi:timeTravel

Conversation

@JingsongLi
Copy link
Copy Markdown
Contributor

@JingsongLi JingsongLi commented Apr 2, 2026

Purpose

Introduce time travel support for the DataFusion integration, allowing users to query historical snapshots via standard SQL syntax FOR SYSTEM_TIME AS OF.

Brief change log

Tests

provision.py & read_tables.rs

API and Format

Documentation

@JingsongLi JingsongLi changed the title feat: introduce time travel for data fusion [WIP] feat: introduce time travel for data fusion Apr 2, 2026
@JingsongLi JingsongLi changed the title [WIP] feat: introduce time travel for data fusion feat: introduce time travel for data fusion Apr 2, 2026
source: None
});
}
Ok(snapshot)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This get_snapshot() path now returns the deserialized snapshot directly, but it no longer checks snapshot.id() == snapshot_id.

That means a mismatched snapshot-{id} file will be accepted silently, and both the new time-travel path and the normal latest-snapshot path can read the wrong snapshot instead of failing fast.

I think we should keep the same id-consistency check here before merging.

Copy link
Copy Markdown
Contributor

@QuakeWang QuakeWang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

@XiaoHongbo-Hope
Copy link
Copy Markdown
Contributor

+1

@XiaoHongbo-Hope XiaoHongbo-Hope merged commit 9478259 into apache:main Apr 3, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants