GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Supporting snapshot based time travel for Feast · Issue #5782 · feast-dev/feast

Supporting snapshot based time travel for Feast #5782

New issue
Copy link
New issue
Copy link
Open
Open
Supporting snapshot based time travel for Feast#5782
Copy link
Labels
kind/featureNew feature or requestNew feature or requestpriority/p1

Description

@haoxu0
haoxu0
opened on Dec 16, 2025
Issue body actions

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

The current Feast use timestamp to support time travel. With the upcoming integration with Iceberg, deltalake etc, we need to support snapshots based time travel as well.

  • How materialize can use snapshot to incrementally load data.
  • How get_historical_features can use snapshot to get the features at that time point.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Reacted by Jacob Weinhold, Francisco Javier Arceo and mg011

Activity

  1. haoxu0
    added
    kind/featureNew feature or requestNew feature or request
    on Dec 16, 2025
  2. haoxu0 commented on Dec 16, 2025

    @haoxu0
    haoxu0
    on Dec 16, 2025
    CollaboratorAuthor
    More actions

    @franciscojavierarceo @jfw-ppi

  3. franciscojavierarceo commented on Dec 19, 2025

    @franciscojavierarceo
    franciscojavierarceo
    on Dec 19, 2025
    Member
    More actions

    FYI @ntkathole

  4. jfw-ppi commented on Dec 21, 2025

    @jfw-ppi
    jfw-ppi
    on Dec 21, 2025
    Collaborator
    More actions

    With snapshot-based time travel, would we ensure that the response schema remains defined by the FeatureView and does not implicitly vary based on the store or snapshot? If a snapshot is schema-incompatible, should this fail explicitly rather than changing behavior per store?

  5. franciscojavierarceo
    added
    priority/p1
    on Feb 26, 2026
  6. ntkathole
    added 4 commits that reference this issue on Oct 7, 2026

    feat: Add a non-JVM read path for Lance data sources

    e7e2adf

    feat: Add a non-JVM read path for Lance data sources (#6943)

    e2a53bb

    chore(release): release 0.67.0

    2dfb9e6

    fix: Merge upstream feast-dev/feast master - resolve CSV conflict (#247)

    2b0b7d7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureNew feature or requestNew feature or requestpriority/p1

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.