lance-format / lance-format/lance

Improve spark data source for lance

Open
#3,260 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Rust
Stars
7.1k
Forks
852
Avg merge
3d 18h
Merged PRs (30d)
272

Description

Here I will submit a series of features to improve the spark connector more effectively.

Reader
  • Support pushdown for more filters for spark connectors.
    • Pushdown IN to lance scan #3314
  • Support topN push down for spark connector. #3261
  • Support simple aggreator(count) pushdown for spark connector.
  • Support runtime filter pushdown for spark connector.
  • Support get the statistics(row_number and data size) for spark optimizer. #3304
  • Use the lance index to query data for the spark connector.
  • Support pushdown the fragment ids into the lance scanner
  • And so on
Writer
  • Support overwrite operator for spark sink #3313
  • Support merge operator to fast add a new column for spark sink.
  • Support AQE for partition number choosen.
  • And so on
Catalog
  • Impl the fs catalog for spark connector.
  • Impl the hms catalog for spark connector.
  • And so on
Configuration
  • Support set options in lance spark datasource api #3366
  • Separate the write params and read options for spark connector.
  • Refactor the spark connector configuration since some configurations should persist in the catalog.

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

This is a broad tracking issue covering reader, writer, catalog, and configuration work for the Spark connector. No files, tests, or single entry point are named; choose one unchecked item and first locate the corresponding connector area before defining its completion criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
spark
Domain
data-engineering
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.