microsoft / microsoft/LakeBench
Proposal: ruff + CLI + cloud engines + TPC-DI + Databricks (5-PR stack)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 54
- Forks
- 21
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 15
Description
I've got a set of changes I'd like to contribute as a 5-part stack, each based on main:
- lint — adopt ruff + pre-commit, enforce in CI
- cloud engines — Livy / Spark Connect + AST-based multi-part name qualification (fixes a silent catalog-dropping bug; makes fuzzy column remap opt-in)
- cli —
lakebenchCLI + profiles (fixes atoken_envcredential-dropping bug) - tpcdi — TPC-DI benchmark port across six engines
- databricks — Databricks Connect engine
Each is independently green (ruff + tests). Do you prefer a base-chained stack of PRs, or sequential PRs against main (open #1, merge, rebase next)? Happy to do whichever fits your review workflow. I'll also call out two design questions inline (the Databricks constructor re-exec, and the W291/W293 lint ignore).
Contributor guide
No contributing guide indexed for this repository
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 from the repository's main branch and review the proposed five areas separately: ruff and pre-commit CI, cloud engines, the lakebench CLI and profiles, TPC-DI, and Databricks Connect. Run the existing tests and lint checks for each independently green part, then resolve the requested PR-order and design questions before defining completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, spark
- Domain
- build-system, cli, cloud, data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100