[rust] Merge fluss-rust repo into fluss
- Dominant language
- Java
- Stars
- 2.1k
- Forks
- 625
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 97
Description
### Search before asking
- [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar.
### Description
- import the standalone fluss-rust tree under fluss-rust/ in the monorepo with full git history preserved
- generate the Rust protocol types from the canonical monorepo proto
- move the Rust client docs/website content into the monorepo docs structure and fix cross-links
- wire Rust crate + bindings (Python/C++/Elixir) packaging and publishing into the monorepo release process
- add the Rust build/test/clippy/rustdoc gates (and bindings) to the monorepo pipelines with proper gating and using Fluss server image from the same source tree.
### Willingness to contribute
- [x] I'm willing to submit a PR!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by comparing the standalone fluss-rust tree with the monorepo and locating the canonical proto, docs structure, release process, and existing pipelines. The work is done when Rust and binding packaging, generated protocol types, documentation links, build/test/clippy/rustdoc gates, and the same-source Fluss server image are integrated and passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, elixir, python, rust
- Domain
- build-system, ci-cd, documentation, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100