lance-format/lance

feat: bytes read and bytes write mectirc for per lance scanner and writer

Open

#3,570 opened on Mar 20, 2025

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Rust (695 forks)github user discovery
help wanted

Repository metrics

Stars
 (6,582 stars)
PR merge metrics
 (Avg merge 6d 1h) (219 merged PRs in 30d)

Description

When we scan the lance dataset, it's better to provide the read metrics, especially for the io bytes and IOPS metric.

The Spark web UI has some task-level metrics, for example, the input bytes. But now Lance can't provide it.

Image

The same metrics are required when we write a lance dataset.

Contributor guide

Research direction
Examine the existing scanner and writer implementations to identify where bytes are read/written, then add metrics collection and expose them via a metrics system.
Tech stack
rust
Domain
databasedata
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
RustLance internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50