mirror of
https://github.com/milvus-io/milvus.git
synced 2026-07-21 10:15:43 +00:00
wei liuandGitHub
7fc234d1fe
issue: [#45691](https://github.com/milvus-io/milvus/issues/45691) ## Summary Bump rust toolchain `1.89 → 1.92` only in installation paths (Dockerfiles + install scripts). ## Why milvus-storage HEAD upgrades `iceberg` crate `0.8 → 0.9`, which declares `edition = "2024"` and `rust-version = "1.92"`. The new MSRV requires the builder image to ship rust 1.92 before milvus can take that milvus-storage commit. This PR is the **first step**: 1. Bump rust toolchain in installation scripts and Dockerfiles. 2. Once merged, builder image is republished with rust 1.92. 3. Follow-up PR will bump `.env` `DATE_VERSION` to the new tag, switch `cargo +1.89` → `cargo +1.92` in `internal/core/thirdparty/{tantivy,opendal}/CMakeLists.txt`, and bump milvus-storage to the iceberg-0.9 commit. This split avoids the chicken-egg problem: changing the cargo pin or milvus-storage version in this PR would fail CI, since the currently pinned builder image only ships rust 1.89. ## Files changed | File | Change | |---|---| | `scripts/install_deps.sh` | `RUST_VERSION="1.89"` → `1.92` | | `scripts/3rdparty_build.sh` | rust toolchain `1.89` → `1.92` (mac + linux paths) | | `build/docker/builder/{cpu,gpu}/*/Dockerfile` (7 files) | rustup `--default-toolchain=1.89` → `1.92` | | `DEVELOPMENT.md` | doc table rust version | ## Test plan - [ ] CI passes on existing builder image (no behaviour change for current build path) - [ ] After merge, builder image is republished with rust 1.92 - [ ] Follow-up PR can then bump `.env` and milvus-storage Signed-off-by: Wei Liu <wei.liu@zilliz.com>
Compile and install milvus cluster
Environment
OS: Ubuntu 20.04
go：1.21
cmake: >=3.18
gcc: >= 11
Install dependencies
Install compile dependencies
$ sudo apt install -y g++ gcc make libssl-dev zlib1g-dev libboost-regex-dev \
libboost-program-options-dev libboost-system-dev libboost-filesystem-dev \
libboost-serialization-dev python3-dev libboost-python-dev libcurl4-openssl-dev gfortran libtbb-dev
$ export GO111MODULE=on
$ go get github.com/golang/protobuf/protoc-gen-go@v1.3.2
Install OpenBlas library
install using apt
sudo apt install -y libopenblas-dev
or build from source code
$ wget https://github.com/xianyi/OpenBLAS/archive/v0.3.9.tar.gz && \
$ tar zxvf v0.3.9.tar.gz && cd OpenBLAS-0.3.9 && \
$ make TARGET=CORE2 DYNAMIC_ARCH=1 DYNAMIC_OLDER=1 USE_THREAD=0 USE_OPENMP=0 FC=gfortran CC=gcc COMMON_OPT="-O3 -g -fPIC" FCOMMON_OPT="-O3 -g -fPIC -frecursive" NMAX="NUM_THREADS=128" LIBPREFIX="libopenblas" INTERFACE64=0 NO_STATIC=1 && \
$ make PREFIX=/usr install
Compile
Generate the go files from proto file
$ make check-proto-product
Check code specifications
$ make verifiers
Compile milvus
$ make milvus
Install docker-compose
refer: https://docs.docker.com/compose/install/
$ sudo curl -L "https://github.com/docker/compose/releases/download/1.27.4/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
$ sudo chmod +x /usr/local/bin/docker-compose
$ sudo ln -s /usr/local/bin/docker-compose /usr/bin/docker-compose
$ docker-compose --version
$ docker compose --version
Start service
Start third-party service:
$ cd [milvus project path]/deployments/docker/cluster
$ docker-compose up -d
$ docker compose up -d
Start milvus cluster:
$ cd [milvus project path]
$ ./scripts/start_cluster.sh
Run unittest
Run all unittest including go and cpp cases:
$ make unittest
You also can run go unittest only:
$ make test-go
Run cpp unittest only:
$ make test-cpp
Run code coverage
Run code coverage including go and cpp:
$ make codecov
You also can run go code coverage only:
$ make codecov-go
Run cpp code coverage only:
$ make codecov-cpp