This is an automated email from the ASF dual-hosted git repository.
wankai pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/skywalking.git
The following commit(s) were added to refs/heads/master by this push:
new 65137fc27f Bump up SW_STORAGE_BANYANDB_COMPATIBLE_SERVER_API_VERSIONS
to 0.10 (#13684)
65137fc27f is described below
commit 65137fc27fd765bb44007bad7fcbe59a185fa617
Author: Wan Kai <[email protected]>
AuthorDate: Tue Jan 27 11:26:08 2026 +0800
Bump up SW_STORAGE_BANYANDB_COMPATIBLE_SERVER_API_VERSIONS to 0.10 (#13684)
---
docs/en/setup/backend/backend-setup.md | 2 +-
docs/en/setup/backend/configuration-vocabulary.md | 37 +++++++++++-----------
docs/en/setup/backend/storages/banyandb.md | 5 +--
.../server-starter/src/main/resources/bydb.yml | 3 +-
test/e2e-v2/script/env | 2 +-
5 files changed, 26 insertions(+), 23 deletions(-)
diff --git a/docs/en/setup/backend/backend-setup.md
b/docs/en/setup/backend/backend-setup.md
index 587b7ded1a..0460c94040 100755
--- a/docs/en/setup/backend/backend-setup.md
+++ b/docs/en/setup/backend/backend-setup.md
@@ -24,7 +24,7 @@ The compatible BanyanDB API version number could be found in
`/config/bydb.yml`
```
${SW_STORAGE_BANYANDB_COMPATIBLE_SERVER_API_VERSIONS}
```
-The compatible BanyanDB Server version number can get through the [API
versions
mapping](https://skywalking.apache.org/docs/skywalking-banyandb/latest/installation/versions/).
+The compatible BanyanDB Server version number can be found via the [API
versions
mapping](https://skywalking.apache.org/docs/skywalking-banyandb/latest/installation/versions/).
```shell
export BYDB_VERSION=xxx
diff --git a/docs/en/setup/backend/configuration-vocabulary.md
b/docs/en/setup/backend/configuration-vocabulary.md
index 56ec52f16f..882a396e69 100644
--- a/docs/en/setup/backend/configuration-vocabulary.md
+++ b/docs/en/setup/backend/configuration-vocabulary.md
@@ -352,24 +352,25 @@ The following table lists the configuration items:
### Global Configuration
The global settings for the whole BanyanDB:
-| Settings | Value(s) and Explanation
| System Environment
Variable¹ | Default |
-|---------------------------------|-------------------------------------------------------------------------------------------------------|--------------------------------------------------------|-------------------|
-| targets | Hosts with ports of the BanyanDB.
|
SW_STORAGE_BANYANDB_TARGETS | 127.0.0.1:17912 |
-| maxBulkSize | The maximum size of write entities in a
single batch write call. |
SW_STORAGE_BANYANDB_MAX_BULK_SIZE | 10000 |
-| flushInterval | Period of flush interval. In the timeunit
of seconds. |
SW_STORAGE_BANYANDB_FLUSH_INTERVAL | 15 |
-| flushTimeout | The timeout seconds of a bulk flush.
|
SW_STORAGE_BANYANDB_FLUSH_TIMEOUT | 10 |
-| concurrentWriteThreads | Concurrent consumer threads for batch
writing. |
SW_STORAGE_BANYANDB_CONCURRENT_WRITE_THREADS | 15 |
-| profileTaskQueryMaxSize | Max size of ProfileTask to be fetched.
|
SW_STORAGE_BANYANDB_PROFILE_TASK_QUERY_MAX_SIZE | 200 |
-| resultWindowMaxSize | The maximum size of dataset when the OAP
loads cache, such as network aliases. |
SW_STORAGE_BANYAND_QUERY_MAX_WINDOW_SIZE | 10000 |
-| metadataQueryMaxSize | The maximum size of metadata per query.
|
SW_STORAGE_BANYAND_QUERY_MAX_SIZE | 10000 |
-| segmentQueryMaxSize | The maximum size of trace segments per
query. |
SW_STORAGE_BANYAND_QUERY_SEGMENT_SIZE | 200 |
-| asyncProfilerTaskQueryMaxSize | Max size of AsyncProfilerTask to be
fetched. |
SW_STORAGE_BANYANDB_ASYNC_PROFILER_TASK_QUERY_MAX_SIZE | 200 |
-| profileDataQueryScrollBatchSize | The batch size of query profiling data.
|
SW_STORAGE_BANYAND_QUERY_PROFILE_DATA_BATCH_SIZE | 100 |
-| user | The username for BanyanDB authentication.
|
SW_STORAGE_BANYANDB_USER | - |
-| password | The password for BanyanDB authentication.
|
SW_STORAGE_BANYANDB_PASSWORD | - |
-| sslTrustCAPath | If the BanyanDB server is configured with
TLS, config the TLS cert file path and open tls connection. |
SW_STORAGE_BANYANDB_SSL_TRUST_CA_PATH | - |
-| cleanupUnusedTopNRules | Cleanup TopN rules in BanyanDB server that
are not configured in the bydb-topn.yml config. |
SW_STORAGE_BANYANDB_CLEANUP_UNUSED_TOPN_RULES | true |
-| namespace | The namespace in BanyanDB to store the
data of OAP. | SW_NAMESPACE
| default |
+| Settings | Value(s) and Explanation
| System Environment Variable¹
| Default |
+|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|-----------------|
+| targets | Hosts with ports of the BanyanDB.
| SW_STORAGE_BANYANDB_TARGETS
| 127.0.0.1:17912 |
+| maxBulkSize | The maximum size of write entities in a
single batch write call.
| SW_STORAGE_BANYANDB_MAX_BULK_SIZE
| 10000 |
+| flushInterval | Period of flush interval. In the timeunit
of seconds.
| SW_STORAGE_BANYANDB_FLUSH_INTERVAL
| 15 |
+| flushTimeout | The timeout seconds of a bulk flush.
| SW_STORAGE_BANYANDB_FLUSH_TIMEOUT
| 10 |
+| concurrentWriteThreads | Concurrent consumer threads for batch
writing.
| SW_STORAGE_BANYANDB_CONCURRENT_WRITE_THREADS
| 15 |
+| profileTaskQueryMaxSize | Max size of ProfileTask to be fetched.
| SW_STORAGE_BANYANDB_PROFILE_TASK_QUERY_MAX_SIZE
| 200 |
+| resultWindowMaxSize | The maximum size of dataset when the OAP
loads cache, such as network aliases.
| SW_STORAGE_BANYANDB_QUERY_MAX_WINDOW_SIZE
| 10000 |
+| metadataQueryMaxSize | The maximum size of metadata per query.
| SW_STORAGE_BANYANDB_QUERY_MAX_SIZE
| 10000 |
+| segmentQueryMaxSize | The maximum size of trace segments per
query.
| SW_STORAGE_BANYANDB_QUERY_SEGMENT_SIZE
| 200 |
+| asyncProfilerTaskQueryMaxSize | Max size of AsyncProfilerTask to be
fetched.
|
SW_STORAGE_BANYANDB_ASYNC_PROFILER_TASK_QUERY_MAX_SIZE | 200 |
+| profileDataQueryScrollBatchSize | The batch size of query profiling data.
| SW_STORAGE_BANYANDB_QUERY_PROFILE_DATA_BATCH_SIZE
| 100 |
+| user | The username for BanyanDB authentication.
| SW_STORAGE_BANYANDB_USER
| - |
+| password | The password for BanyanDB authentication.
| SW_STORAGE_BANYANDB_PASSWORD
| - |
+| sslTrustCAPath | If the BanyanDB server is configured with
TLS, config the TLS cert file path and open tls connection.
| SW_STORAGE_BANYANDB_SSL_TRUST_CA_PATH
| - |
+| cleanupUnusedTopNRules | Cleanup TopN rules in BanyanDB server that
are not configured in the bydb-topn.yml config.
| SW_STORAGE_BANYANDB_CLEANUP_UNUSED_TOPN_RULES
| true |
+| namespace | The namespace in BanyanDB to store the
data of OAP.
| SW_NAMESPACE
| default |
+| compatibleServerApiVersions | The compatible server API versions of
BanyanDB. The compatible BanyanDB Server version number can be found via the
[API versions
mapping](https://skywalking.apache.org/docs/skywalking-banyandb/latest/installation/versions/).
| SW_STORAGE_BANYANDB_COMPATIBLE_SERVER_API_VERSIONS | 0.10 |
### Group Configuration
The settings for each group:
diff --git a/docs/en/setup/backend/storages/banyandb.md
b/docs/en/setup/backend/storages/banyandb.md
index 03eef785e6..b5044c105a 100644
--- a/docs/en/setup/backend/storages/banyandb.md
+++ b/docs/en/setup/backend/storages/banyandb.md
@@ -7,7 +7,7 @@ The compatible BanyanDB API version number could be found in
`/config/bydb.yml`
```
${SW_STORAGE_BANYANDB_COMPATIBLE_SERVER_API_VERSIONS}
```
-The compatible BanyanDB Server version number can get through the [API
versions
mapping](https://skywalking.apache.org/docs/skywalking-banyandb/latest/installation/versions/).
+The compatible BanyanDB Server version number can be found via the [API
versions
mapping](https://skywalking.apache.org/docs/skywalking-banyandb/latest/installation/versions/).
If the BanyanDB server API version is not compatible with the OAP server, the
OAP server will not start, and the following error message will be displayed:
```shell
@@ -66,7 +66,8 @@ global:
# OAP will create BanyanDB Groups using the format of "{namespace}_{group
name}", such as "sw_records".
namespace: ${SW_NAMESPACE:"sw"}
# The compatible server API versions of BanyanDB.
- compatibleServerApiVersions:
${SW_STORAGE_BANYANDB_COMPATIBLE_SERVER_API_VERSIONS:"0.9"}
+ # The compatible BanyanDB Server version number can be found via the [API
versions
mapping](https://skywalking.apache.org/docs/skywalking-banyandb/latest/installation/versions/).
+ compatibleServerApiVersions:
${SW_STORAGE_BANYANDB_COMPATIBLE_SERVER_API_VERSIONS:"0.10"}
groups:
# The group settings of record.
diff --git a/oap-server/server-starter/src/main/resources/bydb.yml
b/oap-server/server-starter/src/main/resources/bydb.yml
index 4a2b946935..b1ce48367b 100644
--- a/oap-server/server-starter/src/main/resources/bydb.yml
+++ b/oap-server/server-starter/src/main/resources/bydb.yml
@@ -54,7 +54,8 @@ global:
# OAP will create BanyanDB Groups using the format of "{namespace}_{group
name}", such as "sw_records".
namespace: ${SW_NAMESPACE:"sw"}
# The compatible server API versions of BanyanDB.
- compatibleServerApiVersions:
${SW_STORAGE_BANYANDB_COMPATIBLE_SERVER_API_VERSIONS:"0.9"}
+ # The compatible BanyanDB Server version number can be found via the [API
versions
mapping](https://skywalking.apache.org/docs/skywalking-banyandb/latest/installation/versions/).
+ compatibleServerApiVersions:
${SW_STORAGE_BANYANDB_COMPATIBLE_SERVER_API_VERSIONS:"0.10"}
groups:
# The group settings of record.
diff --git a/test/e2e-v2/script/env b/test/e2e-v2/script/env
index 2facf48972..0850fba48e 100644
--- a/test/e2e-v2/script/env
+++ b/test/e2e-v2/script/env
@@ -23,7 +23,7 @@
SW_AGENT_CLIENT_JS_COMMIT=f08776d909eb1d9bc79c600e493030651b97e491
SW_AGENT_CLIENT_JS_TEST_COMMIT=4f1eb1dcdbde3ec4a38534bf01dded4ab5d2f016
SW_KUBERNETES_COMMIT_SHA=6fe5e6f0d3b7686c6be0457733e825ee68cb9b35
SW_ROVER_COMMIT=79292fe07f17f98f486e0c4471213e1961fb2d1d
-SW_BANYANDB_COMMIT=a69048c4ff85f437002edacf83918c8f8ba5951a
+SW_BANYANDB_COMMIT=208982aaa11092bc38018a9e1b24eda67e829312
SW_AGENT_PHP_COMMIT=d1114e7be5d89881eec76e5b56e69ff844691e35
SW_PREDICTOR_COMMIT=54a0197654a3781a6f73ce35146c712af297c994
