lance-format / lance-format/lance
feat: bytes read and bytes write mectirc for per lance scanner and writer
Open
Nobody has claimed this yet.
help wanted
- Dominant language
- Rust
- Stars
- 7.1k
- Forks
- 852
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 272
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.
The same metrics are required when we write a lance dataset.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Lance scanner and writer implementations and reviewing any existing metrics instrumentation. Determine how per-scan read bytes and IOPS, and per-write bytes and IOPS, should be exposed; done means both scanning and writing provide the requested task-level metrics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- data-engineering, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100