You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/en/blog_post/20240402_OpenmldbVsRedis.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ We plan to test with 1 million (referred to as 1M) keys, each corresponding to 1
44
44
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:
Copy file name to clipboardExpand all lines: docs/en/deploy/compile.md
+7-7Lines changed: 7 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -5,25 +5,25 @@
5
5
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.
6
6
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.
7
7
8
-
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.8.5](https://github.com/4paradigm/OpenMLDB/releases/tag/v0.8.5) under `hybridsql:0.8.5` ，If you prefer to compile on the latest code in `main` branch, pull `hybridsql:latest` image instead.
8
+
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.0](https://github.com/4paradigm/OpenMLDB/releases/tag/v0.9.0) under `hybridsql:0.9.0` ，If you prefer to compile on the latest code in `main` branch, pull `hybridsql:latest` image instead.
9
9
10
10
1. Pull the docker image
11
11
12
12
```bash
13
-
docker pull 4pdosc/hybridsql:0.8
13
+
docker pull 4pdosc/hybridsql:0.9
14
14
```
15
15
16
16
2. Create a docker container
17
17
18
18
```bash
19
-
docker run -it 4pdosc/hybridsql:0.8 bash
19
+
docker run -it 4pdosc/hybridsql:0.9 bash
20
20
```
21
21
22
-
3. Download the OpenMLDB source code inside the docker container, and set the branch into v0.8.5
22
+
3. Download the OpenMLDB source code inside the docker container, and set the branch into v0.9.0
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
209
209
210
210
- Do not change the `Use workflow from` setting to a specific tag; it can be another branch.
211
211
- Choose the desired `OS name`, which in this case is `centos6`.
212
-
- If you are not compiling the main branch, provide the name of the branch, tag (e.g., v0.8.5), or SHA you want to compile in the `The branch, tag, or SHA to checkout, otherwise use the branch` field.
212
+
- If you are not compiling the main branch, provide the name of the branch, tag (e.g., v0.9.0), or SHA you want to compile in the `The branch, tag, or SHA to checkout, otherwise use the branch` field.
213
213
- The compilation output will be accessible in "runs", as shown in an example [here](https://github.com/4paradigm/OpenMLDB/actions/runs/6044951902).
214
214
- The workflow will definitely produce the OpenMLDB binary file.
215
215
- 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.
Copy file name to clipboardExpand all lines: docs/en/deploy/install_deploy.md
+34-34Lines changed: 34 additions & 34 deletions
Original file line number
Diff line number
Diff line change
@@ -56,17 +56,17 @@ If your operating system is not mentioned above or if you want to compile from s
56
56
57
57
### Linux Platform Compatibility Pre-test
58
58
59
-
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.8.5-linux.tar.gz`, and execute:
59
+
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.0-linux.tar.gz`, and execute:
60
60
61
61
```
62
-
tar -zxvf openmldb-0.8.5-linux.tar.gz
63
-
./openmldb-0.8.5-linux/bin/openmldb --version
62
+
tar -zxvf openmldb-0.9.0-linux.tar.gz
63
+
./openmldb-0.9.0-linux/bin/openmldb --version
64
64
```
65
65
66
66
The result should display the version number of the program, as shown below:
67
67
68
68
```
69
-
openmldb version 0.8.5-xxxx
69
+
openmldb version 0.9.0-xxxx
70
70
Debug build (NDEBUG not #defined)
71
71
```
72
72
@@ -181,9 +181,9 @@ DataCollector and SyncTool currently do not support one-click deployment. Please
**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'
431
431
432
432
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.
433
433
434
-
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.8.5-2`.
434
+
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.0-2`.
435
435
436
436
```
437
-
tar -zxvf openmldb-0.8.5-linux.tar.gz
438
-
mv openmldb-0.8.5-linux openmldb-tablet-0.8.5-2
439
-
cd openmldb-tablet-0.8.5-2
437
+
tar -zxvf openmldb-0.9.0-linux.tar.gz
438
+
mv openmldb-0.9.0-linux openmldb-tablet-0.9.0-2
439
+
cd openmldb-tablet-0.9.0-2
440
440
```
441
441
442
442
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
**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
502
502
503
503
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.
504
504
505
-
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.8.5-2`.
505
+
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.0-2`.
506
506
507
507
```
508
-
tar -zxvf openmldb-0.8.5-linux.tar.gz
509
-
mv openmldb-0.8.5-linux openmldb-ns-0.8.5-2
510
-
cd openmldb-ns-0.8.5-2
508
+
tar -zxvf openmldb-0.9.0-linux.tar.gz
509
+
mv openmldb-0.9.0-linux openmldb-ns-0.9.0-2
510
+
cd openmldb-ns-0.9.0-2
511
511
```
512
512
513
513
Then modify the configuration and start.
@@ -548,10 +548,10 @@ Before running APIServer, ensure that the TabletServer and NameServer processes
Copy file name to clipboardExpand all lines: docs/en/integration/deploy_integration/airflow_provider_demo.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ For smooth function, we recommend starting OpenMLDB using the docker image and i
36
36
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.
37
37
38
38
```
39
-
docker run -p 8080:8080 -v `pwd`/airflow_demo_files:/work/airflow_demo_files -it 4pdosc/openmldb:0.8.5 bash
39
+
docker run -p 8080:8080 -v `pwd`/airflow_demo_files:/work/airflow_demo_files -it 4pdosc/openmldb:0.9.0 bash
40
40
```
41
41
42
42
#### Download and Install Airflow and Airflow OpenMLDB Provider
Copy file name to clipboardExpand all lines: docs/en/integration/deploy_integration/dolphinscheduler_task_demo.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ In addition to SQL execution in OpenMLDB, real-time prediction also requires mod
31
31
32
32
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.
33
33
```
34
-
docker run -it -p 12345:12345 4pdosc/openmldb:0.8.5 bash
34
+
docker run -it -p 12345:12345 4pdosc/openmldb:0.9.0 bash
35
35
```
36
36
```{attention}
37
37
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.
Copy file name to clipboardExpand all lines: docs/en/integration/online_datasources/kafka_connector_demo.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -49,7 +49,7 @@ This article will use Docker mode to start OpenMLDB, so there is no need to down
49
49
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.
50
50
51
51
```
52
-
docker run -it -v `pwd`:/work/kafka 4pdosc/openmldb:0.8.5 bash
52
+
docker run -it -v `pwd`:/work/kafka 4pdosc/openmldb:0.9.0 bash
Copy file name to clipboardExpand all lines: docs/en/quickstart/sdk/java_sdk.md
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -12,12 +12,12 @@ In Java SDK, the default execution mode for JDBC Statements is online, while the
12
12
<dependency>
13
13
<groupId>com.4paradigm.openmldb</groupId>
14
14
<artifactId>openmldb-jdbc</artifactId>
15
-
<version>0.8.5</version>
15
+
<version>0.9.0</version>
16
16
</dependency>
17
17
<dependency>
18
18
<groupId>com.4paradigm.openmldb</groupId>
19
19
<artifactId>openmldb-native</artifactId>
20
-
<version>0.8.5</version>
20
+
<version>0.9.0</version>
21
21
</dependency>
22
22
```
23
23
@@ -29,16 +29,16 @@ In Java SDK, the default execution mode for JDBC Statements is online, while the
29
29
<dependency>
30
30
<groupId>com.4paradigm.openmldb</groupId>
31
31
<artifactId>openmldb-jdbc</artifactId>
32
-
<version>0.8.5</version>
32
+
<version>0.9.0</version>
33
33
</dependency>
34
34
<dependency>
35
35
<groupId>com.4paradigm.openmldb</groupId>
36
36
<artifactId>openmldb-native</artifactId>
37
-
<version>0.8.5-macos</version>
37
+
<version>0.9.0-macos</version>
38
38
</dependency>
39
39
```
40
40
41
-
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.8.5-macos`, while the version of openmldb-jdbc remains unchanged.
41
+
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.0-macos`, while the version of openmldb-jdbc remains unchanged.
42
42
43
43
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).
44
44
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`.
0 commit comments