[Feature] Support Mosaic file format

Open
#236 0 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp
Domain
databases

Research direction

Start by tracing the Paimon C++ file-format SPI and comparing its current schema, reader, writer, and statistics handling with Apache Paimon Java 2.0's Mosaic behavior. The work is done when Mosaic is registered, projection and column-bucket metadata are supported, and C++ round-trip plus Java-produced compatibility tests pass.

Written by the indexing model from the issue text.

Description

enhancement
Search before asking
  • I searched in the issues and found nothing similar.
Motivation

Apache Paimon Java 2.0 supports Mosaic, a hybrid format designed for wide tables using column bucketing and parallel I/O. Paimon C++ cannot currently access tables using this format.

Solution

Add Mosaic support to the Paimon C++ file-format SPI:

  • Register the mosaic file-format factory.
  • Implement compatible schema, reader, writer, and statistics handling.
  • Support column projection and Mosaic column-bucket metadata.
  • Add C++ round-trip tests and Java-produced file compatibility tests.
Anything else?

We will also support formats such as Lance and Vortex in the future.

Are you willing to submit a PR?
  • I'm willing to submit a PR!
Dominant language
C++
Stars
65
Forks
29
Avg merge
2d 30m
Merged PRs (30d)
77

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.

More from apache/paimon-cpp

All issues in apache/paimon-cpp

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.