lance-format / lance-format/lance-data-viewer

[feat]: display lineage for datasets

Open
#86 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
60
Forks
9
Avg merge
10m
Merged PRs (30d)
4

Description

Summary

Hi team, lance is well-known for its dataset management, including lineage for dataset.
So I'm wondering if we could to display dataset lineage in the viewer as well?

For example, when users provide a dataset, the whole lineage of the dataset is shown on the screen (with tag / branching / version aside), so users could click in the a detailed "version" and check the schema, metadata, or data for the selected version.

Use case

In production usage, we use a base lance dataset as the foundation, and branch out different versions for experimentation; having a lineage display helps our user to understand the dataset better.

Proposed approach

No response

Design constraint check
  • I have read CONTRIBUTING.md and this proposal does not conflict with the load-bearing design constraints.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating the viewer's existing dataset and version display, then determine how Lance dataset branches, tags, and versions are exposed. Done means users can navigate the lineage and inspect the selected version's schema, metadata, or data.

Written by the indexing model from the issue text.

Assessment

Tech stack
fastapi, python
Domain
data, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.