Merge branch 'main' into table_maintenance_pypaimon

Author: nuts-rice

.github/workflows/ci.yml

@@ -58,7 +58,7 @@ jobs:
         run: cargo fmt --all -- --check
 
       - name: Clippy
-        run: cargo clippy --all-targets --workspace --features fulltext,vortex,mosaic -- -D warnings
+        run: cargo clippy --all-targets --workspace --features fulltext,vortex -- -D warnings
 
   build:
     runs-on: ${{ matrix.os }}
@@ -71,7 +71,7 @@ jobs:
     steps:
       - uses: actions/checkout@v7
       - name: Build
-        run: cargo build --features fulltext,vortex,mosaic
+        run: cargo build --features fulltext,vortex
 
   unit:
     runs-on: ${{ matrix.os }}
@@ -85,7 +85,7 @@ jobs:
       - uses: actions/checkout@v7
 
       - name: Test
-        run: cargo test -p paimon --all-targets --features fulltext,vortex,mosaic
+        run: cargo test -p paimon --all-targets --features fulltext,vortex
         env:
           RUST_LOG: DEBUG
           RUST_BACKTRACE: full

CONTRIBUTING.md

@@ -45,6 +45,30 @@ This is a pure Rust project, so only `cargo` is needed. Here are some common com
 2. Open a pull request on the project's GitHub page. Provide a clear description of your changes and why they are necessary.
 3. Wait for reviews and address any feedback. Once the pull request is approved and merged, your changes will be part of the project.
 
+## AI-Assisted Contributions
+
+Apache Paimon Rust has the following policy for AI-assisted pull requests:
+
+- The PR author should **understand the core ideas** behind the implementation **end-to-end** and be able to justify the design and code during review.
+- **Call out unknowns and assumptions.** It is acceptable not to fully understand some details of AI-generated code, but authors should identify these cases and point them out to reviewers. This allows reviewers to apply their knowledge of the codebase and evaluate potential concerns, such as correctness, concurrency, compatibility, or performance risks.
+
+### Why fully AI-generated PRs without understanding are not helpful
+
+AI tools cannot reliably make complex changes to Apache Paimon Rust on their own, which is why we rely on pull requests and code review.
+
+The purposes of code review are:
+
+1. Complete the intended task correctly.
+2. Share knowledge between authors and reviewers as a long-term investment in the project.
+
+A fully AI-generated contribution without sufficient author understanding does not meet these purposes. Maintainers could use AI tools directly, while contributors acting only as a proxy gain little knowledge of the project.
+
+Review capacity is limited, so large pull requests that appear to lack the required understanding may not be reviewed and may eventually be closed or redirected.
+
+### Better ways to contribute than an "AI dump"
+
+Consider writing a high-quality issue with a clear problem statement and a minimal reproducible example. This often makes it easier for the community to investigate the problem and develop an appropriate solution.
+
 ### Read the design docs
 
 For a deeper understanding of the project, read the design documentation available on our [Paimon Rust](https://paimon.apache.org/docs/rust/).

bindings/c/Cargo.toml

@@ -25,11 +25,13 @@ license.workspace = true
 version.workspace = true
 
 [lib]
-crate-type = ["cdylib", "staticlib"]
+crate-type = ["cdylib", "staticlib", "rlib"]
 doc = false
 
 [dependencies]
 paimon = { path = "../../crates/paimon" }
 tokio = { workspace = true, features = ["rt-multi-thread"] }
 futures = "0.3"
+arrow = { workspace = true }
 arrow-array = { workspace = true }
+arrow-schema = { workspace = true }

bindings/c/DEPENDENCIES.rust.tsv

@@ -58,6 +58,7 @@ impl paimon_error {
             | paimon::Error::ColumnAlreadyExist { .. } => PaimonErrorCode::AlreadyExists,
             paimon::Error::ConfigInvalid { .. }
             | paimon::Error::DataTypeInvalid { .. }
+            | paimon::Error::DataInvalid { .. }
             | paimon::Error::IdentifierInvalid { .. } => PaimonErrorCode::InvalidInput,
             paimon::Error::IoUnexpected { .. } => PaimonErrorCode::IoError,
             _ => PaimonErrorCode::Unexpected,

bindings/c/src/error.rs

@@ -24,7 +24,10 @@ mod error;
 mod identifier;
 mod result;
 mod table;
+#[cfg(test)]
+mod tests;
 mod types;
+mod write;
 
 use std::sync::OnceLock;
 use tokio::runtime::Runtime;

bindings/c/src/lib.rs

@@ -77,3 +77,29 @@ pub struct paimon_result_next_batch {
     pub batch: paimon_arrow_batch,
     pub error: *mut paimon_error,
 }
+
+// === Write/Commit result types ===
+
+#[repr(C)]
+pub struct paimon_result_write_builder {
+    pub write_builder: *mut paimon_write_builder,
+    pub error: *mut paimon_error,
+}
+
+#[repr(C)]
+pub struct paimon_result_table_write {
+    pub write: *mut paimon_table_write,
+    pub error: *mut paimon_error,
+}
+
+#[repr(C)]
+pub struct paimon_result_table_commit {
+    pub commit: *mut paimon_table_commit,
+    pub error: *mut paimon_error,
+}
+
+#[repr(C)]
+pub struct paimon_result_prepare_commit {
+    pub messages: *mut paimon_commit_messages,
+    pub error: *mut paimon_error,
+}