From bb661a8ba7469fc00f44ebc5c6f9d699a8a7535f Mon Sep 17 00:00:00 2001 From: Zhang Hao Date: Fri, 26 Jul 2024 17:28:59 +0800 Subject: [PATCH] docs: update version 0.9.2 in docs --- demo/java_quickstart/demo/pom.xml | 2 +- demo/predict-taxi-trip-duration/README.md | 4 +- .../README.md | 2 +- docs/en/blog_post/20240402_OpenmldbVsRedis.md | 2 +- .../20240523_OpenmldbFeatureSignatures.md | 2 +- docs/en/deploy/compile.md | 10 +-- docs/en/deploy/install_deploy.md | 68 +++++++++--------- .../deploy_integration/OpenMLDB_Byzer_taxi.md | 2 +- .../airflow_provider_demo.md | 2 +- .../dolphinscheduler_task_demo.md | 2 +- .../kafka_connector_demo.md | 2 +- .../pulsar_connector_demo.md | 2 +- docs/en/quickstart/openmldb_quickstart.md | 2 +- docs/en/quickstart/sdk/java_sdk.md | 10 +-- docs/en/reference/ip_tips.md | 6 +- docs/en/tutorial/standalone_use.md | 2 +- docs/en/use_case/JD_recommendation.md | 2 +- docs/en/use_case/talkingdata_demo.md | 2 +- .../use_case/taxi_tour_duration_prediction.md | 2 +- docs/zh/blog_post/20240402_OpenmldbVsRedis.md | 2 +- .../20240523_OpenmldbFeatureSignatures.md | 2 +- docs/zh/deploy/compile.md | 10 +-- docs/zh/deploy/install_deploy.md | 70 +++++++++---------- .../deploy_integration/OpenMLDB_Byzer_taxi.md | 2 +- .../airflow_provider_demo.md | 2 +- .../dolphinscheduler_task_demo.md | 2 +- .../kafka_connector_demo.md | 2 +- .../pulsar_connector_demo.md | 2 +- docs/zh/quickstart/openmldb_quickstart.md | 2 +- docs/zh/quickstart/sdk/java_sdk.md | 10 +-- docs/zh/reference/ip_tips.md | 12 ++-- docs/zh/tutorial/standalone_use.md | 2 +- docs/zh/use_case/JD_recommendation.md | 2 +- docs/zh/use_case/talkingdata_demo.md | 2 +- .../use_case/taxi_tour_duration_prediction.md | 2 +- release/conf/openmldb-env.sh | 2 +- 36 files changed, 127 insertions(+), 127 deletions(-) diff --git a/demo/java_quickstart/demo/pom.xml b/demo/java_quickstart/demo/pom.xml index 3af812f8c6e..70c901fa7be 100644 --- a/demo/java_quickstart/demo/pom.xml +++ b/demo/java_quickstart/demo/pom.xml @@ -29,7 +29,7 @@ com.4paradigm.openmldb openmldb-jdbc - 0.9.1 + 0.9.2 org.testng diff --git a/demo/predict-taxi-trip-duration/README.md b/demo/predict-taxi-trip-duration/README.md index 33da4f2086a..a80a418f06e 100644 --- a/demo/predict-taxi-trip-duration/README.md +++ b/demo/predict-taxi-trip-duration/README.md @@ -28,7 +28,7 @@ w2 as (PARTITION BY passenger_count ORDER BY pickup_datetime ROWS_RANGE BETWEEN **Start docker** ``` -docker run -it 4pdosc/openmldb:0.9.1 bash +docker run -it 4pdosc/openmldb:0.9.2 bash ``` **Initialize environment** ```bash @@ -138,7 +138,7 @@ python3 predict.py **Start docker** ```bash -docker run -it 4pdosc/openmldb:0.9.1 bash +docker run -it 4pdosc/openmldb:0.9.2 bash ``` **Initialize environment** diff --git a/demo/talkingdata-adtracking-fraud-detection/README.md b/demo/talkingdata-adtracking-fraud-detection/README.md index f687b7249a9..77e9214588d 100644 --- a/demo/talkingdata-adtracking-fraud-detection/README.md +++ b/demo/talkingdata-adtracking-fraud-detection/README.md @@ -15,7 +15,7 @@ We recommend you to use docker to run the demo. OpenMLDB and dependencies have b **Start docker** ``` -docker run -it 4pdosc/openmldb:0.9.1 bash +docker run -it 4pdosc/openmldb:0.9.2 bash ``` #### Run locally diff --git a/docs/en/blog_post/20240402_OpenmldbVsRedis.md b/docs/en/blog_post/20240402_OpenmldbVsRedis.md index 780e0512835..415c9b37b05 100644 --- a/docs/en/blog_post/20240402_OpenmldbVsRedis.md +++ b/docs/en/blog_post/20240402_OpenmldbVsRedis.md @@ -44,7 +44,7 @@ We plan to test with 1 million (referred to as 1M) keys, each corresponding to 1 Deployment can be done through containerization or directly on physical machines using software packages. There is no significant difference between the two methods. Below is an example of using containerization for deployment: - OpenMLDB - - Docker image: `docker pull 4pdosc/openmldb:0.9.1` + - Docker image: `docker pull 4pdosc/openmldb:0.9.2` - Documentation: [https://openmldb.ai/docs/zh/main/quickstart/openmldb_quickstart.html](https://openmldb.ai/docs/zh/main/quickstart/openmldb_quickstart.html) - Redis: diff --git a/docs/en/blog_post/20240523_OpenmldbFeatureSignatures.md b/docs/en/blog_post/20240523_OpenmldbFeatureSignatures.md index e55a1f5ee71..abb91bd4bf0 100644 --- a/docs/en/blog_post/20240523_OpenmldbFeatureSignatures.md +++ b/docs/en/blog_post/20240523_OpenmldbFeatureSignatures.md @@ -30,7 +30,7 @@ These functions must be used in conjunction with the sample format functions `cs First, follow the [quick start](https://openmldb.ai/docs/en/main/tutorial/standalone_use.html) guide to get the image and start the OpenMLDB server and client. ```bash -docker run -it 4pdosc/openmldb:0.9.0 bash +docker run -it 4pdosc/openmldb:0.9.2 bash /work/init.sh /work/openmldb/sbin/openmldb-cli.sh ``` diff --git a/docs/en/deploy/compile.md b/docs/en/deploy/compile.md index dbf7451da0f..f6425c168d7 100644 --- a/docs/en/deploy/compile.md +++ b/docs/en/deploy/compile.md @@ -5,7 +5,7 @@ This section describes the steps to compile and use OpenMLDB inside its official docker image [hybridsql](https://hub.docker.com/r/4pdosc/hybridsql), mainly for quick start and development purposes in the docker container. The docker image has packed the required tools and dependencies, so there is no need to set them up separately. To compile without the official docker image, refer to the section [Detailed Instructions for Build](#detailed-instructions-for-build) below. -Keep in mind that you should always use the same version of both compile image and [OpenMLDB version](https://github.com/4paradigm/OpenMLDB/releases). This section demonstrates compiling for [OpenMLDB v0.9.1](https://github.com/4paradigm/OpenMLDB/releases/tag/v0.9.1) under `hybridsql:0.9.1` ，If you prefer to compile on the latest code in `main` branch, pull `hybridsql:latest` image instead. +Keep in mind that you should always use the same version of both compile image and [OpenMLDB version](https://github.com/4paradigm/OpenMLDB/releases). This section demonstrates compiling for [OpenMLDB v0.9.2](https://github.com/4paradigm/OpenMLDB/releases/tag/v0.9.2) under `hybridsql:0.9.2` ，If you prefer to compile on the latest code in `main` branch, pull `hybridsql:latest` image instead. 1. Pull the docker image @@ -19,11 +19,11 @@ Keep in mind that you should always use the same version of both compile image a docker run -it 4pdosc/hybridsql:0.9 bash ``` -3. Download the OpenMLDB source code inside the docker container, and set the branch into v0.9.1 +3. Download the OpenMLDB source code inside the docker container, and set the branch into v0.9.2 ```bash cd ~ - git clone -b v0.9.1 https://github.com/4paradigm/OpenMLDB.git + git clone -b v0.9.2 https://github.com/4paradigm/OpenMLDB.git ``` 4. Compile OpenMLDB @@ -150,7 +150,7 @@ The built jar packages are in the `target` path of each submodule. If you want t 1. Downloading the pre-built OpenMLDB Spark distribution: ```bash -wget https://github.com/4paradigm/spark/releases/download/v3.2.1-openmldb0.9.1/spark-3.2.1-bin-openmldbspark.tgz +wget https://github.com/4paradigm/spark/releases/download/v3.2.1-openmldb0.9.2/spark-3.2.1-bin-openmldbspark.tgz ``` Alternatively, you can also download the source code and compile from scratch: @@ -209,7 +209,7 @@ After forking the OpenMLDB repository, you can trigger the `Other OS Build` work - Do not change the `Use workflow from` setting to a specific tag; it can be another branch. - Choose the desired `OS name`, which in this case is `centos6`. -- If you are not compiling the main branch, provide the name of the branch, tag (e.g., v0.9.1), or SHA you want to compile in the `The branch, tag, or SHA to checkout, otherwise use the branch` field. +- If you are not compiling the main branch, provide the name of the branch, tag (e.g., v0.9.2), or SHA you want to compile in the `The branch, tag, or SHA to checkout, otherwise use the branch` field. - The compilation output will be accessible in "runs", as shown in an example [here](https://github.com/4paradigm/OpenMLDB/actions/runs/6044951902). - The workflow will definitely produce the OpenMLDB binary file. - If you don't need the Java or Python SDK, you can configure `java sdk enable` or `python sdk enable` to be "OFF" to save compilation time. diff --git a/docs/en/deploy/install_deploy.md b/docs/en/deploy/install_deploy.md index 1bff9d29b0f..0bbdc165101 100644 --- a/docs/en/deploy/install_deploy.md +++ b/docs/en/deploy/install_deploy.md @@ -56,17 +56,17 @@ If your operating system is not mentioned above or if you want to compile from s ### Linux Platform Compatibility Pre-test -Due to the variations among Linux platforms, the distribution package may not be entirely compatible with your machine. Therefore, it's recommended to conduct a preliminary compatibility test. Download the pre-compiled package `openmldb-0.9.1-linux.tar.gz`, and execute: +Due to the variations among Linux platforms, the distribution package may not be entirely compatible with your machine. Therefore, it's recommended to conduct a preliminary compatibility test. Download the pre-compiled package `openmldb-0.9.2-linux.tar.gz`, and execute: ``` -tar -zxvf openmldb-0.9.1-linux.tar.gz -./openmldb-0.9.1-linux/bin/openmldb --version +tar -zxvf openmldb-0.9.2-linux.tar.gz +./openmldb-0.9.2-linux/bin/openmldb --version ``` The result should display the version number of the program, as shown below: ``` -openmldb version 0.9.1-xxxx +openmldb version 0.9.2-xxxx Debug build (NDEBUG not #defined) ``` @@ -181,9 +181,9 @@ DataCollector and SyncTool currently do not support one-click deployment. Please ### Download OpenMLDB ``` -wget https://github.com/4paradigm/OpenMLDB/releases/download/v0.9.1/openmldb-0.9.1-linux.tar.gz -tar -zxvf openmldb-0.9.1-linux.tar.gz -cd openmldb-0.9.1-linux +wget https://github.com/4paradigm/OpenMLDB/releases/download/v0.9.2/openmldb-0.9.2-linux.tar.gz +tar -zxvf openmldb-0.9.2-linux.tar.gz +cd openmldb-0.9.2-linux ``` ### Environment Configuration @@ -192,7 +192,7 @@ The environment variables are defined in `conf/openmldb-env.sh`, as shown in the | Environment Variable | Default Value | Note | | --------------------------------- | ------------------------------------------------------- | ------------------------------------------------------------ | -| OPENMLDB_VERSION | 0.9.1 | OpenMLDB version | +| OPENMLDB_VERSION | 0.9.2 | OpenMLDB version | | OPENMLDB_MODE | standalone | standalone or cluster | | OPENMLDB_HOME | root directory of the release folder | openmldb root directory | | SPARK_HOME | $OPENMLDB_HOME/spark | Spark root directory, if the directory does not exist, it will be downloaded automatically.| @@ -365,10 +365,10 @@ Note that at least two TabletServers need to be deployed, otherwise errors may o **1. Download the OpenMLDB deployment package** ``` -wget https://github.com/4paradigm/OpenMLDB/releases/download/v0.9.1/openmldb-0.9.1-linux.tar.gz -tar -zxvf openmldb-0.9.1-linux.tar.gz -mv openmldb-0.9.1-linux openmldb-tablet-0.9.1 -cd openmldb-tablet-0.9.1 +wget https://github.com/4paradigm/OpenMLDB/releases/download/v0.9.2/openmldb-0.9.2-linux.tar.gz +tar -zxvf openmldb-0.9.2-linux.tar.gz +mv openmldb-0.9.2-linux openmldb-tablet-0.9.2 +cd openmldb-tablet-0.9.2 ``` **2. Modify the configuration file `conf/tablet.flags`** @@ -431,12 +431,12 @@ For clustered versions, the number of TabletServers must be 2 or more. If there' To start the next TabletServer on a different machine, simply repeat the aforementioned steps on that machine. If starting the next TabletServer on the same machine, ensure it's in a different directory, and do not reuse a directory where the TabletServer is already running. -For instance, you can decompress the package again (avoid using a directory where TabletServer is already running, as files generated after startup may be affected), and name the directory `openmldb-tablet-0.9.1-2`. +For instance, you can decompress the package again (avoid using a directory where TabletServer is already running, as files generated after startup may be affected), and name the directory `openmldb-tablet-0.9.2-2`. ``` -tar -zxvf openmldb-0.9.1-linux.tar.gz -mv openmldb-0.9.1-linux openmldb-tablet-0.9.1-2 -cd openmldb-tablet-0.9.1-2 +tar -zxvf openmldb-0.9.2-linux.tar.gz +mv openmldb-0.9.2-linux openmldb-tablet-0.9.2-2 +cd openmldb-tablet-0.9.2-2 ``` Modify the configuration again and start the TabletServer. Note that if all TabletServers are on the same machine, use different port numbers to avoid the "Fail to listen" error in the log (`logs/tablet.WARNING`). @@ -454,10 +454,10 @@ Please ensure that all TabletServer have been successfully started before deploy **1. Download the OpenMLDB deployment package** ```` -wget https://github.com/4paradigm/OpenMLDB/releases/download/v0.9.1/openmldb-0.9.1-linux.tar.gz -tar -zxvf openmldb-0.9.1-linux.tar.gz -mv openmldb-0.9.1-linux openmldb-ns-0.9.1 -cd openmldb-ns-0.9.1 +wget https://github.com/4paradigm/OpenMLDB/releases/download/v0.9.2/openmldb-0.9.2-linux.tar.gz +tar -zxvf openmldb-0.9.2-linux.tar.gz +mv openmldb-0.9.2-linux openmldb-ns-0.9.2 +cd openmldb-ns-0.9.2 ```` **2. Modify the configuration file conf/nameserver.flags** @@ -502,12 +502,12 @@ You can have only one NameServer, but if you need high availability, you can dep To start the next NameServer on another machine, simply repeat the above steps on that machine. If starting the next NameServer on the same machine, ensure it's in a different directory and do not reuse the directory where NameServer has already been started. -For instance, you can decompress the package again (avoid using the directory where NameServer is already running, as files generated after startup may be affected) and name the directory `openmldb-ns-0.9.1-2`. +For instance, you can decompress the package again (avoid using the directory where NameServer is already running, as files generated after startup may be affected) and name the directory `openmldb-ns-0.9.2-2`. ``` -tar -zxvf openmldb-0.9.1-linux.tar.gz -mv openmldb-0.9.1-linux openmldb-ns-0.9.1-2 -cd openmldb-ns-0.9.1-2 +tar -zxvf openmldb-0.9.2-linux.tar.gz +mv openmldb-0.9.2-linux openmldb-ns-0.9.2-2 +cd openmldb-ns-0.9.2-2 ``` Then modify the configuration and start. @@ -548,10 +548,10 @@ Before running APIServer, ensure that the TabletServer and NameServer processes **1. Download the OpenMLDB deployment package** ``` -wget https://github.com/4paradigm/OpenMLDB/releases/download/v0.9.1/openmldb-0.9.1-linux.tar.gz -tar -zxvf openmldb-0.9.1-linux.tar.gz -mv openmldb-0.9.1-linux openmldb-apiserver-0.9.1 -cd openmldb-apiserver-0.9.1 +wget https://github.com/4paradigm/OpenMLDB/releases/download/v0.9.2/openmldb-0.9.2-linux.tar.gz +tar -zxvf openmldb-0.9.2-linux.tar.gz +mv openmldb-0.9.2-linux openmldb-apiserver-0.9.2 +cd openmldb-apiserver-0.9.2 ``` **2. Modify the configuration file conf/apiserver.flags** @@ -615,18 +615,18 @@ Download the Spark distribution from the [Spark official website](https://spark. Alternatively, use the OpenMLDB Spark distribution. ```shell -wget https://github.com/4paradigm/spark/releases/download/v3.2.1-openmldb0.9.1/spark-3.2.1-bin-openmldbspark.tgz -# Image address (China)：https://www.openmldb.com/download/v0.9.1/spark-3.2.1-bin-openmldbspark.tgz +wget https://github.com/4paradigm/spark/releases/download/v3.2.1-openmldb0.9.2/spark-3.2.1-bin-openmldbspark.tgz +# Image address (China)：https://www.openmldb.com/download/v0.9.2/spark-3.2.1-bin-openmldbspark.tgz tar -zxvf spark-3.2.1-bin-openmldbspark.tgz export SPARK_HOME=`pwd`/spark-3.2.1-bin-openmldbspark/ ``` OpenMLDB deployment package： ``` -wget https://github.com/4paradigm/OpenMLDB/releases/download/v0.9.1/openmldb-0.9.1-linux.tar.gz -tar -zxvf openmldb-0.9.1-linux.tar.gz -mv openmldb-0.9.1-linux openmldb-taskmanager-0.9.1 -cd openmldb-taskmanager-0.9.1 +wget https://github.com/4paradigm/OpenMLDB/releases/download/v0.9.2/openmldb-0.9.2-linux.tar.gz +tar -zxvf openmldb-0.9.2-linux.tar.gz +mv openmldb-0.9.2-linux openmldb-taskmanager-0.9.2 +cd openmldb-taskmanager-0.9.2 ``` **2. Modify the configuration file conf/taskmanager.properties** diff --git a/docs/en/integration/deploy_integration/OpenMLDB_Byzer_taxi.md b/docs/en/integration/deploy_integration/OpenMLDB_Byzer_taxi.md index cda984ed4f5..a3ba6d87e8d 100644 --- a/docs/en/integration/deploy_integration/OpenMLDB_Byzer_taxi.md +++ b/docs/en/integration/deploy_integration/OpenMLDB_Byzer_taxi.md @@ -13,7 +13,7 @@ This article demonstrates how to use [OpenMLDB](https://github.com/4paradigm/Ope The command is as follows: ``` -docker run --network host -dit --name openmldb -v /mlsql/admin/:/byzermnt 4pdosc/openmldb:0.9.1 bash +docker run --network host -dit --name openmldb -v /mlsql/admin/:/byzermnt 4pdosc/openmldb:0.9.2 bash docker exec -it openmldb bash /work/init.sh echo "create database db1;" | /work/openmldb/bin/openmldb --zk_cluster=127.0.0.1:2181 --zk_root_path=/openmldb --role=sql_client diff --git a/docs/en/integration/deploy_integration/airflow_provider_demo.md b/docs/en/integration/deploy_integration/airflow_provider_demo.md index 39186654e3e..51ff8362deb 100644 --- a/docs/en/integration/deploy_integration/airflow_provider_demo.md +++ b/docs/en/integration/deploy_integration/airflow_provider_demo.md @@ -36,7 +36,7 @@ For smooth function, we recommend starting OpenMLDB using the docker image and i Since Airflow Web requires an external port for login, the container's port must be exposed. Then map the downloaded file from the previous step to the `/work/airflow/dags` directory. This step is crucial for Airflow to load the DAGs from this folder correctly. ``` -docker run -p 8080:8080 -v `pwd`/airflow_demo_files:/work/airflow_demo_files -it 4pdosc/openmldb:0.9.1 bash +docker run -p 8080:8080 -v `pwd`/airflow_demo_files:/work/airflow_demo_files -it 4pdosc/openmldb:0.9.2 bash ``` #### Download and Install Airflow and Airflow OpenMLDB Provider diff --git a/docs/en/integration/deploy_integration/dolphinscheduler_task_demo.md b/docs/en/integration/deploy_integration/dolphinscheduler_task_demo.md index 8330f5a3025..8f8f9769455 100644 --- a/docs/en/integration/deploy_integration/dolphinscheduler_task_demo.md +++ b/docs/en/integration/deploy_integration/dolphinscheduler_task_demo.md @@ -31,7 +31,7 @@ In addition to SQL execution in OpenMLDB, real-time prediction also requires mod The test can be executed on macOS or Linux, and we recommend running this demo within the provided OpenMLDB docker image. In this setup, both OpenMLDB and DolphinScheduler will be launched inside the container, with the port of DolphinScheduler exposed. ``` -docker run -it -p 12345:12345 4pdosc/openmldb:0.9.1 bash +docker run -it -p 12345:12345 4pdosc/openmldb:0.9.2 bash ``` ```{attention} For proper configuration of DolphinScheduler, the tenant should be set up as a user of the operating system, and this user must have sudo permissions. It is advised to download and initiate DolphinScheduler within the OpenMLDB container. Otherwise, please ensure that the user has sudo permissions. diff --git a/docs/en/integration/online_datasources/kafka_connector_demo.md b/docs/en/integration/online_datasources/kafka_connector_demo.md index 6cc8c79379d..eb6bcfd22ee 100644 --- a/docs/en/integration/online_datasources/kafka_connector_demo.md +++ b/docs/en/integration/online_datasources/kafka_connector_demo.md @@ -49,7 +49,7 @@ This article will use Docker mode to start OpenMLDB, so there is no need to down We recommend that you bind all three downloaded file packages to the `kafka` directory. Alternatively, you can download the file packages after starting the container. For our demonstration, we assume that the file packages are all in the `/work/kafka` directory. ``` -docker run -it -v `pwd`:/work/kafka 4pdosc/openmldb:0.9.1 bash +docker run -it -v `pwd`:/work/kafka 4pdosc/openmldb:0.9.2 bash ``` ### Note diff --git a/docs/en/integration/online_datasources/pulsar_connector_demo.md b/docs/en/integration/online_datasources/pulsar_connector_demo.md index 42e7b12b789..e5478e2164d 100644 --- a/docs/en/integration/online_datasources/pulsar_connector_demo.md +++ b/docs/en/integration/online_datasources/pulsar_connector_demo.md @@ -43,7 +43,7 @@ Currently, only the OpenMLDB cluster version can act as the receiver of sinks, a We recommend using the 'host network' mode to run Docker and bind the file directory 'files' where the SQL script is located. ``` -docker run -dit --network host -v `pwd`/files:/work/pulsar_files --name openmldb 4pdosc/openmldb:0.9.1 bash +docker run -dit --network host -v `pwd`/files:/work/pulsar_files --name openmldb 4pdosc/openmldb:0.9.2 bash docker exec -it openmldb bash ``` diff --git a/docs/en/quickstart/openmldb_quickstart.md b/docs/en/quickstart/openmldb_quickstart.md index 9a0fd5e2ad7..c27be0a2714 100644 --- a/docs/en/quickstart/openmldb_quickstart.md +++ b/docs/en/quickstart/openmldb_quickstart.md @@ -18,7 +18,7 @@ This sample program is developed and deployed based on OpenMLDB CLI, so you need Execute the following command in the command line to pull the OpenMLDB image and start the Docker container: ```bash -docker run -it 4pdosc/openmldb:0.9.1 bash +docker run -it 4pdosc/openmldb:0.9.2 bash ``` ``` {note} diff --git a/docs/en/quickstart/sdk/java_sdk.md b/docs/en/quickstart/sdk/java_sdk.md index 83e5c376e7e..8d8e809b61e 100644 --- a/docs/en/quickstart/sdk/java_sdk.md +++ b/docs/en/quickstart/sdk/java_sdk.md @@ -12,12 +12,12 @@ In Java SDK, the default execution mode for JDBC Statements is online, while the com.4paradigm.openmldb openmldb-jdbc - 0.9.1 + 0.9.2 com.4paradigm.openmldb openmldb-native - 0.9.1 + 0.9.2 ``` @@ -29,16 +29,16 @@ In Java SDK, the default execution mode for JDBC Statements is online, while the com.4paradigm.openmldb openmldb-jdbc - 0.9.1 + 0.9.2 com.4paradigm.openmldb openmldb-native - 0.9.1-macos + 0.9.2-macos ``` -Note: Since the openmldb-native package contains the C++ static library compiled for OpenMLDB, it defaults to the Linux static library. For macOS, the version of openmldb-native should be changed to `0.9.1-macos`, while the version of openmldb-jdbc remains unchanged. +Note: Since the openmldb-native package contains the C++ static library compiled for OpenMLDB, it defaults to the Linux static library. For macOS, the version of openmldb-native should be changed to `0.9.2-macos`, while the version of openmldb-jdbc remains unchanged. The macOS version of openmldb-native only supports macOS 12. To run it on macOS 11 or macOS 10.15, the openmldb-native package needs to be compiled from the source code on the corresponding OS. For detailed compilation methods, please refer to [Java SDK](../../deploy/compile.md#Build-java-sdk-with-multi-processes). When using a self-compiled openmldb-native package, it is recommended to install it into your local Maven repository using `mvn install`. After that, you can reference it in your project's pom.xml file. It's not advisable to reference it using `scope=system`. diff --git a/docs/en/reference/ip_tips.md b/docs/en/reference/ip_tips.md index 310679140c5..8ffe4e22e1c 100644 --- a/docs/en/reference/ip_tips.md +++ b/docs/en/reference/ip_tips.md @@ -38,12 +38,12 @@ Expose the port through `-p` when starting the container, and the client can acc The stand-alone version needs to expose the ports of three components (nameserver, tabletserver, apiserver): ``` -docker run -p 6527:6527 -p 9921:9921 -p 8080:8080 -it 4pdosc/openmldb:0.9.1 bash +docker run -p 6527:6527 -p 9921:9921 -p 8080:8080 -it 4pdosc/openmldb:0.9.2 bash ``` The cluster version needs to expose the zk port and the ports of all components: ``` -docker run -p 2181:2181 -p 7527:7527 -p 10921:10921 -p 10922:10922 -p 8080:8080 -p 9902:9902 -it 4pdosc/openmldb:0.9.1 bash +docker run -p 2181:2181 -p 7527:7527 -p 10921:10921 -p 10922:10922 -p 8080:8080 -p 9902:9902 -it 4pdosc/openmldb:0.9.2 bash ``` ```{tip} @@ -57,7 +57,7 @@ If the OpenMLDB service process is distributed, the "port number is occupied" ap #### Host Network Or more conveniently, use host networking without port isolation, for example: ``` -docker run --network host -it 4pdosc/openmldb:0.9.1 bash +docker run --network host -it 4pdosc/openmldb:0.9.2 bash ``` But in this case, it is easy to find that the port is occupied by other processes in the host. If occupancy occurs, change the port number carefully. diff --git a/docs/en/tutorial/standalone_use.md b/docs/en/tutorial/standalone_use.md index e0d6a704494..2e7961f55bd 100644 --- a/docs/en/tutorial/standalone_use.md +++ b/docs/en/tutorial/standalone_use.md @@ -11,7 +11,7 @@ This article provides a guide on developing and deploying with OpenMLDB CLI. To Execute the following command to fetch the OpenMLDB image and initiate a Docker container: ```bash -docker run -it 4pdosc/openmldb:0.9.1 bash +docker run -it 4pdosc/openmldb:0.9.2 bash ``` Upon successful container launch, all subsequent commands in this tutorial will assume execution within the container. diff --git a/docs/en/use_case/JD_recommendation.md b/docs/en/use_case/JD_recommendation.md index 02c5a8d2d33..8fdca081016 100644 --- a/docs/en/use_case/JD_recommendation.md +++ b/docs/en/use_case/JD_recommendation.md @@ -60,7 +60,7 @@ Pull the OpenMLDB docker image and run. Since the OpenMLDB cluster needs to communicate with other components, we will use the host network straightaway. In this example, we will use downloaded scripts in the docker, therefore we map the `demodir` directory into the docker container. ```bash -docker run -dit --name=openmldb --network=host -v $demodir:/work/oneflow_demo 4pdosc/openmldb:0.9.1 bash +docker run -dit --name=openmldb --network=host -v $demodir:/work/oneflow_demo 4pdosc/openmldb:0.9.2 bash docker exec -it openmldb bash ``` diff --git a/docs/en/use_case/talkingdata_demo.md b/docs/en/use_case/talkingdata_demo.md index 50eed548296..2eddc17724c 100644 --- a/docs/en/use_case/talkingdata_demo.md +++ b/docs/en/use_case/talkingdata_demo.md @@ -13,7 +13,7 @@ It is recommended to run this demo in Docker. Please make sure that OpenMLDB and **Start the OpenMLDB Docker Image** ``` -docker run -it 4pdosc/openmldb:0.9.1 bash +docker run -it 4pdosc/openmldb:0.9.2 bash ``` #### 1.1.2 Run Locally diff --git a/docs/en/use_case/taxi_tour_duration_prediction.md b/docs/en/use_case/taxi_tour_duration_prediction.md index fefb25d40e7..dd99c6e4c11 100644 --- a/docs/en/use_case/taxi_tour_duration_prediction.md +++ b/docs/en/use_case/taxi_tour_duration_prediction.md @@ -15,7 +15,7 @@ This article is centered around the development and deployment of OpenMLDB CLI. Execute the following command from the command line to pull the OpenMLDB image and start the Docker container: ```bash -docker run -it 4pdosc/openmldb:0.9.1 bash +docker run -it 4pdosc/openmldb:0.9.2 bash ``` This image comes pre-installed with OpenMLDB and encompasses all the scripts, third-party libraries, open-source tools, and training data necessary for this case. diff --git a/docs/zh/blog_post/20240402_OpenmldbVsRedis.md b/docs/zh/blog_post/20240402_OpenmldbVsRedis.md index 9ab49a7a001..73ab1f801fd 100644 --- a/docs/zh/blog_post/20240402_OpenmldbVsRedis.md +++ b/docs/zh/blog_post/20240402_OpenmldbVsRedis.md @@ -47,7 +47,7 @@ OpenMLDB 是一款开源的高性能全内存 SQL 数据库，在时序数据存 #### 操作步骤（复现路径） 1. 部署 OpenMLDB 和 Redis：部署可以使用容器化部署或者使用软件包在物理机上直接部署，经过对比，两者无明显差异。下边以容器化部署为例进行举例描述。 - OpenMLDB： - - 镜像：`docker pull 4pdosc/openmldb:0.9.1` + - 镜像：`docker pull 4pdosc/openmldb:0.9.2` - 文档：https://openmldb.ai/docs/zh/main/quickstart/openmldb_quickstart.html - Redis： - 镜像：`docker pull redis:7.2.4` diff --git a/docs/zh/blog_post/20240523_OpenmldbFeatureSignatures.md b/docs/zh/blog_post/20240523_OpenmldbFeatureSignatures.md index 8a690290ca6..7fa7b62ec2a 100644 --- a/docs/zh/blog_post/20240523_OpenmldbFeatureSignatures.md +++ b/docs/zh/blog_post/20240523_OpenmldbFeatureSignatures.md @@ -26,7 +26,7 @@ OpenMLDB 的特征签名功能是在标准 SQL 的基础上，基于一系列 Op 首先参照[快速入门](https://openmldb.ai/docs/zh/main/tutorial/standalone_use.html)获取镜像并启动 OpenMLDB 服务端和客户端。 ```bash -docker run -it 4pdosc/openmldb:0.9.0 bash +docker run -it 4pdosc/openmldb:0.9.2 bash /work/init.sh /work/openmldb/sbin/openmldb-cli.sh ``` diff --git a/docs/zh/deploy/compile.md b/docs/zh/deploy/compile.md index e120275415d..a525416e976 100644 --- a/docs/zh/deploy/compile.md +++ b/docs/zh/deploy/compile.md @@ -4,7 +4,7 @@ 此节介绍在官方编译镜像 [hybridsql](https://hub.docker.com/r/4pdosc/hybridsql) 中编译 OpenMLDB，主要可以用于在容器内试用和开发目的。镜像内置了编译所需要的工具和依赖，因此不需要额外的步骤单独配置它们。关于基于非 docker 的编译使用方式，请参照下面的 [从源码全量编译](#从源码全量编译) 章节。 -对于编译镜像的版本，需要注意拉取的镜像版本和 [OpenMLDB 发布版本](https://github.com/4paradigm/OpenMLDB/releases)保持一致。以下例子演示了在 `hybridsql:0.9.1` 镜像版本上编译 [OpenMLDB v0.9.1](https://github.com/4paradigm/OpenMLDB/releases/tag/v0.9.1) 的代码，如果要编译最新 `main` 分支的代码，则需要拉取 `hybridsql:latest` 版本镜像。 +对于编译镜像的版本，需要注意拉取的镜像版本和 [OpenMLDB 发布版本](https://github.com/4paradigm/OpenMLDB/releases)保持一致。以下例子演示了在 `hybridsql:0.9.2` 镜像版本上编译 [OpenMLDB v0.9.2](https://github.com/4paradigm/OpenMLDB/releases/tag/v0.9.2) 的代码，如果要编译最新 `main` 分支的代码，则需要拉取 `hybridsql:latest` 版本镜像。 1. 下载 docker 镜像 ```bash @@ -16,10 +16,10 @@ docker run -it 4pdosc/hybridsql:0.9 bash ``` -3. 在 docker 容器内, 克隆 OpenMLDB, 并切换分支到 v0.9.1 +3. 在 docker 容器内, 克隆 OpenMLDB, 并切换分支到 v0.9.2 ```bash cd ~ - git clone -b v0.9.1 https://github.com/4paradigm/OpenMLDB.git + git clone -b v0.9.2 https://github.com/4paradigm/OpenMLDB.git ``` 4. 在 docker 容器内编译 OpenMLDB @@ -144,7 +144,7 @@ make SQL_JAVASDK_ENABLE=ON NPROC=4 1. 下载预编译的OpenMLDB Spark发行版。 ```bash -wget https://github.com/4paradigm/spark/releases/download/v3.2.1-openmldb0.9.1/spark-3.2.1-bin-openmldbspark.tgz +wget https://github.com/4paradigm/spark/releases/download/v3.2.1-openmldb0.9.2/spark-3.2.1-bin-openmldbspark.tgz ``` 或者下载源代码并从头开始编译。 @@ -203,7 +203,7 @@ bash steps/centos6_build.sh Fork OpenMLDB仓库后，可以使用在`Actions`中触发workflow `Other OS Build`，编译产出在`Actions`的`Artifacts`中。workflow 配置方式： - 不要更换`Use workflow from`为某个tag，可以是其他分支。 - 选择`os name`为`centos6`。 -- 如果不是编译main分支，在`The branch, tag or SHA to checkout, otherwise use the branch`中填写想要的分支名、Tag(e.g. v0.9.1)或SHA。 +- 如果不是编译main分支，在`The branch, tag or SHA to checkout, otherwise use the branch`中填写想要的分支名、Tag(e.g. v0.9.2)或SHA。 - 编译产出在触发后的runs界面中，参考[成功产出的runs链接](https://github.com/4paradigm/OpenMLDB/actions/runs/6044951902)。 - 一定会产出openmldb binary文件。 - 如果不需要Java或Python SDK，可配置`java sdk enable`或`python sdk enable`为`OFF`，节约编译时间。 diff --git a/docs/zh/deploy/install_deploy.md b/docs/zh/deploy/install_deploy.md index 8c09f693130..d874f95c72f 100644 --- a/docs/zh/deploy/install_deploy.md +++ b/docs/zh/deploy/install_deploy.md @@ -50,17 +50,17 @@ strings /lib64/libc.so.6 | grep ^GLIBC_ ### Linux 平台预测试 -由于 Linux 平台的多样性，发布包可能在你的机器上不兼容，请先通过简单的运行测试。比如，下载预编译包 `openmldb-0.9.1-linux.tar.gz` 以后，运行： +由于 Linux 平台的多样性，发布包可能在你的机器上不兼容，请先通过简单的运行测试。比如，下载预编译包 `openmldb-0.9.2-linux.tar.gz` 以后，运行： ``` -tar -zxvf openmldb-0.9.1-linux.tar.gz -./openmldb-0.9.1-linux/bin/openmldb --version +tar -zxvf openmldb-0.9.2-linux.tar.gz +./openmldb-0.9.2-linux/bin/openmldb --version ``` 结果应显示该程序的版本号，类似 ``` -openmldb version 0.9.1-xxxx +openmldb version 0.9.2-xxxx Debug build (NDEBUG not #defined) ``` @@ -175,9 +175,9 @@ DataCollector和SyncTool暂不支持一键部署。请参考手动部署方式 ### 下载OpenMLDB发行版 ``` -wget https://github.com/4paradigm/OpenMLDB/releases/download/v0.9.1/openmldb-0.9.1-linux.tar.gz -tar -zxvf openmldb-0.9.1-linux.tar.gz -cd openmldb-0.9.1-linux +wget https://github.com/4paradigm/OpenMLDB/releases/download/v0.9.2/openmldb-0.9.2-linux.tar.gz +tar -zxvf openmldb-0.9.2-linux.tar.gz +cd openmldb-0.9.2-linux ``` ### 脚本使用逻辑 @@ -192,9 +192,9 @@ cd openmldb-0.9.1-linux | 环境变量 | 默认值 | 定义 | | -------------------------------- | ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------- | -| OPENMLDB_VERSION | 0.9.1 | OpenMLDB版本，主要用于Spark下载，一般不改动。 | +| OPENMLDB_VERSION | 0.9.2 | OpenMLDB版本，主要用于Spark下载，一般不改动。 | | OPENMLDB_MODE | cluster | standalone或者cluster | -| OPENMLDB_HOME | 当前发行版的根目录 | openmldb发行版根目录，不则使用当前根目录，也就是openmldb-0.9.1-linux所在目录。 | +| OPENMLDB_HOME | 当前发行版的根目录 | openmldb发行版根目录，不则使用当前根目录，也就是openmldb-0.9.2-linux所在目录。 | | SPARK_HOME | $OPENMLDB_HOME/spark | Spark发行版根目录，如果该目录不存在，自动从网上下载。**此路径也将成为TaskManager运行机器上的Spark安装目录。** | | RUNNER_EXISTING_SPARK_HOME | | 配置此项，运行TaskManager的机器将使用该Spark环境，将不下载、部署OpenMLDB Spark发行版。 | | OPENMLDB_USE_EXISTING_ZK_CLUSTER | false | 是否使用已经运行的ZooKeeper集群。如果是`true`，将跳过ZooKeeper集群的部署与管理。 | @@ -415,10 +415,10 @@ bash bin/zkCli.sh -server 172.27.128.33:7181 **1. 下载OpenMLDB部署包** ``` -wget https://github.com/4paradigm/OpenMLDB/releases/download/v0.9.1/openmldb-0.9.1-linux.tar.gz -tar -zxvf openmldb-0.9.1-linux.tar.gz -mv openmldb-0.9.1-linux openmldb-tablet-0.9.1 -cd openmldb-tablet-0.9.1 +wget https://github.com/4paradigm/OpenMLDB/releases/download/v0.9.2/openmldb-0.9.2-linux.tar.gz +tar -zxvf openmldb-0.9.2-linux.tar.gz +mv openmldb-0.9.2-linux openmldb-tablet-0.9.2 +cd openmldb-tablet-0.9.2 ``` **2. 修改配置文件`conf/tablet.flags`** ```bash @@ -469,12 +469,12 @@ Start tablet success 在另一台机器启动下一个TabletServer只需在该机器上重复以上步骤。如果是在同一个机器上启动下一个TabletServer，请保证是在另一个目录中，不要重复使用已经启动过TabletServer的目录。 -比如，可以再次解压压缩包（不要cp已经启动过TabletServer的目录，启动后的生成文件会造成影响），并命名目录为`openmldb-tablet-0.9.1-2`。 +比如，可以再次解压压缩包（不要cp已经启动过TabletServer的目录，启动后的生成文件会造成影响），并命名目录为`openmldb-tablet-0.9.2-2`。 ``` -tar -zxvf openmldb-0.9.1-linux.tar.gz -mv openmldb-0.9.1-linux openmldb-tablet-0.9.1-2 -cd openmldb-tablet-0.9.1-2 +tar -zxvf openmldb-0.9.2-linux.tar.gz +mv openmldb-0.9.2-linux openmldb-tablet-0.9.2-2 +cd openmldb-tablet-0.9.2-2 ``` 再修改配置并启动。注意，TabletServer如果都在同一台机器上，请使用不同端口号，否则日志(logs/tablet.WARNING)中将会有"Fail to listen"信息。 @@ -488,10 +488,10 @@ cd openmldb-tablet-0.9.1-2 ``` **1. 下载OpenMLDB部署包** ```` -wget https://github.com/4paradigm/OpenMLDB/releases/download/v0.9.1/openmldb-0.9.1-linux.tar.gz -tar -zxvf openmldb-0.9.1-linux.tar.gz -mv openmldb-0.9.1-linux openmldb-ns-0.9.1 -cd openmldb-ns-0.9.1 +wget https://github.com/4paradigm/OpenMLDB/releases/download/v0.9.2/openmldb-0.9.2-linux.tar.gz +tar -zxvf openmldb-0.9.2-linux.tar.gz +mv openmldb-0.9.2-linux openmldb-ns-0.9.2 +cd openmldb-ns-0.9.2 ```` **2. 修改配置文件conf/nameserver.flags** ```bash @@ -529,12 +529,12 @@ NameServer 可以只存在一台，如果你需要高可用性，可以部署多 在另一台机器启动下一个 NameServer 只需在该机器上重复以上步骤。如果是在同一个机器上启动下一个 NameServer，请保证是在另一个目录中，不要重复使用已经启动过 namserver 的目录。 -比如，可以再次解压压缩包（不要cp已经启动过 namserver 的目录，启动后的生成文件会造成影响），并命名目录为`openmldb-ns-0.9.1-2`。 +比如，可以再次解压压缩包（不要cp已经启动过 namserver 的目录，启动后的生成文件会造成影响），并命名目录为`openmldb-ns-0.9.2-2`。 ``` -tar -zxvf openmldb-0.9.1-linux.tar.gz -mv openmldb-0.9.1-linux openmldb-ns-0.9.1-2 -cd openmldb-ns-0.9.1-2 +tar -zxvf openmldb-0.9.2-linux.tar.gz +mv openmldb-0.9.2-linux openmldb-ns-0.9.2-2 +cd openmldb-ns-0.9.2-2 ``` 然后再修改配置并启动。 @@ -572,10 +572,10 @@ APIServer负责接收http请求，转发给OpenMLDB集群并返回结果。它 **1. 下载OpenMLDB部署包** ``` -wget https://github.com/4paradigm/OpenMLDB/releases/download/v0.9.1/openmldb-0.9.1-linux.tar.gz -tar -zxvf openmldb-0.9.1-linux.tar.gz -mv openmldb-0.9.1-linux openmldb-apiserver-0.9.1 -cd openmldb-apiserver-0.9.1 +wget https://github.com/4paradigm/OpenMLDB/releases/download/v0.9.2/openmldb-0.9.2-linux.tar.gz +tar -zxvf openmldb-0.9.2-linux.tar.gz +mv openmldb-0.9.2-linux openmldb-apiserver-0.9.2 +cd openmldb-apiserver-0.9.2 ``` **2. 修改配置文件conf/apiserver.flags** @@ -637,18 +637,18 @@ Spark发行版： 或者使用 OpenMLDB Spark 发行版。 ```shell -wget https://github.com/4paradigm/spark/releases/download/v3.2.1-openmldb0.9.1/spark-3.2.1-bin-openmldbspark.tgz -# 中国镜像地址：https://www.openmldb.com/download/v0.9.1/spark-3.2.1-bin-openmldbspark.tgz +wget https://github.com/4paradigm/spark/releases/download/v3.2.1-openmldb0.9.2/spark-3.2.1-bin-openmldbspark.tgz +# 中国镜像地址：https://www.openmldb.com/download/v0.9.2/spark-3.2.1-bin-openmldbspark.tgz tar -zxvf spark-3.2.1-bin-openmldbspark.tgz export SPARK_HOME=`pwd`/spark-3.2.1-bin-openmldbspark/ ``` OpenMLDB部署包： ``` -wget https://github.com/4paradigm/OpenMLDB/releases/download/v0.9.1/openmldb-0.9.1-linux.tar.gz -tar -zxvf openmldb-0.9.1-linux.tar.gz -mv openmldb-0.9.1-linux openmldb-taskmanager-0.9.1 -cd openmldb-taskmanager-0.9.1 +wget https://github.com/4paradigm/OpenMLDB/releases/download/v0.9.2/openmldb-0.9.2-linux.tar.gz +tar -zxvf openmldb-0.9.2-linux.tar.gz +mv openmldb-0.9.2-linux openmldb-taskmanager-0.9.2 +cd openmldb-taskmanager-0.9.2 ``` **2. 修改配置文件conf/taskmanager.properties** diff --git a/docs/zh/integration/deploy_integration/OpenMLDB_Byzer_taxi.md b/docs/zh/integration/deploy_integration/OpenMLDB_Byzer_taxi.md index 45316c6d24e..d9ea4efb466 100644 --- a/docs/zh/integration/deploy_integration/OpenMLDB_Byzer_taxi.md +++ b/docs/zh/integration/deploy_integration/OpenMLDB_Byzer_taxi.md @@ -13,7 +13,7 @@ 执行命令如下： ``` -docker run --network host -dit --name openmldb -v /mlsql/admin/:/byzermnt 4pdosc/openmldb:0.9.1 bash +docker run --network host -dit --name openmldb -v /mlsql/admin/:/byzermnt 4pdosc/openmldb:0.9.2 bash docker exec -it openmldb bash /work/init.sh echo "create database db1;" | /work/openmldb/bin/openmldb --zk_cluster=127.0.0.1:2181 --zk_root_path=/openmldb --role=sql_client diff --git a/docs/zh/integration/deploy_integration/airflow_provider_demo.md b/docs/zh/integration/deploy_integration/airflow_provider_demo.md index 263823eb171..971aefabc3d 100644 --- a/docs/zh/integration/deploy_integration/airflow_provider_demo.md +++ b/docs/zh/integration/deploy_integration/airflow_provider_demo.md @@ -35,7 +35,7 @@ ls airflow_demo_files 登录Airflow Web需要对外端口，所以此处暴露容器的端口。并且直接将上一步下载的文件映射到`/work/airflow/dags`，接下来Airflow将加载此文件夹的DAG。 ``` -docker run -p 8080:8080 -v `pwd`/airflow_demo_files:/work/airflow_demo_files -it 4pdosc/openmldb:0.9.1 bash +docker run -p 8080:8080 -v `pwd`/airflow_demo_files:/work/airflow_demo_files -it 4pdosc/openmldb:0.9.2 bash ``` #### 下载安装Airflow与Airflow OpenMLDB Provider diff --git a/docs/zh/integration/deploy_integration/dolphinscheduler_task_demo.md b/docs/zh/integration/deploy_integration/dolphinscheduler_task_demo.md index 0d010d5c68f..70c5eb77c32 100644 --- a/docs/zh/integration/deploy_integration/dolphinscheduler_task_demo.md +++ b/docs/zh/integration/deploy_integration/dolphinscheduler_task_demo.md @@ -31,7 +31,7 @@ OpenMLDB 希望能达成开发即上线的目标，让开发回归本质，而 测试可以在macOS或Linux上运行，推荐在我们提供的 OpenMLDB 镜像内进行演示测试。我们将在这个容器中启动OpenMLDB和DolphinScheduler，暴露DolphinScheduler的web端口： ``` -docker run -it -p 12345:12345 4pdosc/openmldb:0.9.1 bash +docker run -it -p 12345:12345 4pdosc/openmldb:0.9.2 bash ``` ```{attention} DolphinScheduler 需要配置租户，是操作系统的用户，并且该用户需要有 sudo 权限。所以推荐在 OpenMLDB 容器内下载并启动 DolphinScheduler。否则，请准备有sudo权限的操作系统用户。 diff --git a/docs/zh/integration/online_datasources/kafka_connector_demo.md b/docs/zh/integration/online_datasources/kafka_connector_demo.md index 96bac884b71..2a7aec89909 100644 --- a/docs/zh/integration/online_datasources/kafka_connector_demo.md +++ b/docs/zh/integration/online_datasources/kafka_connector_demo.md @@ -47,7 +47,7 @@ Kafka利用OpenMLDB Kafka Connector导入数据到OpenMLDB集群，其性能将 我们推荐你将下载的三个文件包都绑定到文件目录`kafka`。当然，也可以在启动容器后，再进行文件包的下载。我们假设文件包都在`/work/kafka`目录中。 ``` -docker run -it -v `pwd`:/work/kafka 4pdosc/openmldb:0.9.1 bash +docker run -it -v `pwd`:/work/kafka 4pdosc/openmldb:0.9.2 bash ``` ### 注意事项 diff --git a/docs/zh/integration/online_datasources/pulsar_connector_demo.md b/docs/zh/integration/online_datasources/pulsar_connector_demo.md index 4ad1ff1788a..f1f1ecada8a 100644 --- a/docs/zh/integration/online_datasources/pulsar_connector_demo.md +++ b/docs/zh/integration/online_datasources/pulsar_connector_demo.md @@ -35,7 +35,7 @@ Apache Pulsar是一个云原生的，分布式消息流平台。它可以作为O ``` 我们更推荐你使用‘host network’模式运行docker，以及绑定文件目录‘files’，sql脚本在该目录中。 ``` -docker run -dit --network host -v `pwd`/files:/work/pulsar_files --name openmldb 4pdosc/openmldb:0.9.1 bash +docker run -dit --network host -v `pwd`/files:/work/pulsar_files --name openmldb 4pdosc/openmldb:0.9.2 bash docker exec -it openmldb bash ``` diff --git a/docs/zh/quickstart/openmldb_quickstart.md b/docs/zh/quickstart/openmldb_quickstart.md index fd16b1ba7c3..608689a080d 100644 --- a/docs/zh/quickstart/openmldb_quickstart.md +++ b/docs/zh/quickstart/openmldb_quickstart.md @@ -19,7 +19,7 @@ OpenMLDB 的主要使用场景为作为机器学习的实时特征平台。其 在命令行执行以下命令拉取 OpenMLDB 镜像，并启动 Docker 容器： ```bash -docker run -it 4pdosc/openmldb:0.9.1 bash +docker run -it 4pdosc/openmldb:0.9.2 bash ``` ```{note} diff --git a/docs/zh/quickstart/sdk/java_sdk.md b/docs/zh/quickstart/sdk/java_sdk.md index e6a48b6706c..4315ce0d438 100644 --- a/docs/zh/quickstart/sdk/java_sdk.md +++ b/docs/zh/quickstart/sdk/java_sdk.md @@ -12,12 +12,12 @@ Java SDK中，JDBC Statement的默认执行模式为在线，SqlClusterExecutor com.4paradigm.openmldb openmldb-jdbc - 0.9.1 + 0.9.2 com.4paradigm.openmldb openmldb-native - 0.9.1 + 0.9.2 ``` @@ -29,16 +29,16 @@ Java SDK中，JDBC Statement的默认执行模式为在线，SqlClusterExecutor com.4paradigm.openmldb openmldb-jdbc - 0.9.1 + 0.9.2 com.4paradigm.openmldb openmldb-native - 0.9.1-macos + 0.9.2-macos ``` -注意：由于 openmldb-native 中包含了 OpenMLDB 编译的 C++ 静态库，默认是 Linux 静态库，macOS 上需将上述 openmldb-native 的 version 改成 `0.9.1-macos`，openmldb-jdbc 的版本保持不变。 +注意：由于 openmldb-native 中包含了 OpenMLDB 编译的 C++ 静态库，默认是 Linux 静态库，macOS 上需将上述 openmldb-native 的 version 改成 `0.9.2-macos`，openmldb-jdbc 的版本保持不变。 openmldb-native 的 macOS 版本只支持 macOS 12，如需在 macOS 11 或 macOS 10.15上运行，需在相应 OS 上源码编译 openmldb-native 包，详细编译方法见[并发编译 Java SDK](https://openmldb.ai/docs/zh/main/deploy/compile.html#java-sdk)。使用自编译的 openmldb-native 包，推荐使用`mvn install`安装到本地仓库，然后在 pom 中引用本地仓库的 openmldb-native 包，不建议用`scope=system`的方式引用。 diff --git a/docs/zh/reference/ip_tips.md b/docs/zh/reference/ip_tips.md index d0e19bbc59d..4fe447e117f 100644 --- a/docs/zh/reference/ip_tips.md +++ b/docs/zh/reference/ip_tips.md @@ -52,15 +52,15 @@ curl http:///dbs/foo -X POST -d'{"mode":"online", "sql":"show component - 暴露端口，也需要修改apiserver的endpoint改为`0.0.0.0`。这样可以使用127.0.0.1或是公网ip访问到 APIServer。 单机版： ``` - docker run -p 8080:8080 -it 4pdosc/openmldb:0.9.1 bash + docker run -p 8080:8080 -it 4pdosc/openmldb:0.9.2 bash ``` 集群版： ``` - docker run -p 9080:9080 -it 4pdosc/openmldb:0.9.1 bash + docker run -p 9080:9080 -it 4pdosc/openmldb:0.9.2 bash ``` - 使用host网络，可以不用修改endpoint配置。缺点是容易引起端口冲突。 ``` - docker run --network host -it 4pdosc/openmldb:0.9.1 bash + docker run --network host -it 4pdosc/openmldb:0.9.2 bash ``` 如果是跨主机访问容器 onebox 中的 APIServer，可以**任选一种**下面的方式： @@ -126,17 +126,17 @@ cd /work/openmldb/conf/ && ls | grep -v _ | xargs sed -i s/0.0.0.0//g && cd 单机版需要暴露三个组件（nameserver，tabletserver，APIServer）的端口： ``` -docker run -p 6527:6527 -p 9921:9921 -p 8080:8080 -it 4pdosc/openmldb:0.9.1 bash +docker run -p 6527:6527 -p 9921:9921 -p 8080:8080 -it 4pdosc/openmldb:0.9.2 bash ``` 集群版需要暴露zk端口与所有组件的端口： ``` -docker run -p 2181:2181 -p 7527:7527 -p 10921:10921 -p 10922:10922 -p 8080:8080 -p 9902:9902 -it 4pdosc/openmldb:0.9.1 bash +docker run -p 2181:2181 -p 7527:7527 -p 10921:10921 -p 10922:10922 -p 8080:8080 -p 9902:9902 -it 4pdosc/openmldb:0.9.2 bash ``` - 使用host网络，可以不用修改 endpoint 配置。如果有端口冲突，请修改 server 的端口配置。 ``` -docker run --network host -it 4pdosc/openmldb:0.9.1 bash +docker run --network host -it 4pdosc/openmldb:0.9.2 bash ``` 如果是跨主机使用 CLI/SDK 访问问容器onebox，只能通过`--network host`，并更改所有endpoint为公网IP，才能顺利访问。 diff --git a/docs/zh/tutorial/standalone_use.md b/docs/zh/tutorial/standalone_use.md index 50032ef8bd5..1719cd6c4e6 100644 --- a/docs/zh/tutorial/standalone_use.md +++ b/docs/zh/tutorial/standalone_use.md @@ -11,7 +11,7 @@ 执行以下命令拉取 OpenMLDB 镜像，并启动 Docker 容器： ```bash -docker run -it 4pdosc/openmldb:0.9.1 bash +docker run -it 4pdosc/openmldb:0.9.2 bash ``` 成功启动容器以后，本教程中的后续命令默认均在容器内执行。 diff --git a/docs/zh/use_case/JD_recommendation.md b/docs/zh/use_case/JD_recommendation.md index 3d22b2fc609..8fa85b0e910 100644 --- a/docs/zh/use_case/JD_recommendation.md +++ b/docs/zh/use_case/JD_recommendation.md @@ -74,7 +74,7 @@ docker pull oneflowinc/oneflow-serving:nightly 由于 OpenMLDB 集群需要和其他组件网络通信，我们直接使用 host 网络。本例将在容器中使用已下载的脚本，所以请将数据脚本所在目录 `demodir` 映射为容器中的目录： ```bash -docker run -dit --name=openmldb --network=host -v $demodir:/work/oneflow_demo 4pdosc/openmldb:0.9.1 bash +docker run -dit --name=openmldb --network=host -v $demodir:/work/oneflow_demo 4pdosc/openmldb:0.9.2 bash docker exec -it openmldb bash ``` diff --git a/docs/zh/use_case/talkingdata_demo.md b/docs/zh/use_case/talkingdata_demo.md index 5cce2584e77..2ae66d7fe04 100755 --- a/docs/zh/use_case/talkingdata_demo.md +++ b/docs/zh/use_case/talkingdata_demo.md @@ -16,7 +16,7 @@ **启动 Docker** ``` -docker run -it 4pdosc/openmldb:0.9.1 bash +docker run -it 4pdosc/openmldb:0.9.2 bash ``` #### 1.1.2 在本地运行 diff --git a/docs/zh/use_case/taxi_tour_duration_prediction.md b/docs/zh/use_case/taxi_tour_duration_prediction.md index 1b676fd17c0..c5a788a5ad1 100644 --- a/docs/zh/use_case/taxi_tour_duration_prediction.md +++ b/docs/zh/use_case/taxi_tour_duration_prediction.md @@ -15,7 +15,7 @@ 在命令行执行以下命令拉取 OpenMLDB 镜像，并启动 Docker 容器： ```bash -docker run -it 4pdosc/openmldb:0.9.1 bash +docker run -it 4pdosc/openmldb:0.9.2 bash ``` 该镜像预装了OpenMLDB，并预置了本案例所需要的所有脚本、三方库、开源工具以及训练数据。 diff --git a/release/conf/openmldb-env.sh b/release/conf/openmldb-env.sh index 92dad03700c..746575c1f7c 100644 --- a/release/conf/openmldb-env.sh +++ b/release/conf/openmldb-env.sh @@ -1,5 +1,5 @@ #! /usr/bin/env bash -export OPENMLDB_VERSION=0.9.1 +export OPENMLDB_VERSION=0.9.2 # openmldb mode: standalone / cluster export OPENMLDB_MODE=${OPENMLDB_MODE:=cluster} # openmldb root path