This is an automated email from the ASF dual-hosted git repository.
jerryjing pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/paimon.git
The following commit(s) were added to refs/heads/master by this push:
new 5ea9713dc0 [index]Fix: add glibc limited for tantivy jni (#7569)
5ea9713dc0 is described below
commit 5ea9713dc03404ccbd28f9141d3f1a5714ee0888
Author: jerry <[email protected]>
AuthorDate: Wed Apr 1 10:57:14 2026 +0800
[index]Fix: add glibc limited for tantivy jni (#7569)
---
paimon-tantivy/paimon-tantivy-jni/README.md | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/paimon-tantivy/paimon-tantivy-jni/README.md
b/paimon-tantivy/paimon-tantivy-jni/README.md
index f7bf86b800..0627885a85 100644
--- a/paimon-tantivy/paimon-tantivy-jni/README.md
+++ b/paimon-tantivy/paimon-tantivy-jni/README.md
@@ -15,6 +15,17 @@ Output artifacts in `rust/target/release/`:
- macOS: `libtantivy_jni.dylib`
- Linux: `libtantivy_jni.so`
+> **Important (Linux glibc compatibility):** The `.so` must be compiled on a
system with a
+> glibc version **equal to or older than** the target runtime environment. For
example, if
+> your production cluster runs CentOS 7 (glibc 2.17), you must build on CentOS
7 or an
+> equivalent system — building on a newer OS (e.g., Ubuntu 22.04 with glibc
2.35) will
+> produce a `.so` that fails at runtime with:
+> ```
+> /lib64/libm.so.6: version `GLIBC_2.27' not found
+> ```
+> A safe practice is to always build on the oldest supported Linux distribution
+> (e.g., CentOS 7) to maximize compatibility.
+
### 2. Copy native library to resources
```bash
