Docs: Draft VIDEX plugin + VIDEX-Server guide#303
Merged
mariadb-stefan-hinz merged 1 commit intomariadb-corporation:mainfrom Jan 26, 2026
Merged
Docs: Draft VIDEX plugin + VIDEX-Server guide#303mariadb-stefan-hinz merged 1 commit intomariadb-corporation:mainfrom
mariadb-stefan-hinz merged 1 commit intomariadb-corporation:mainfrom
Conversation
Contributor
Author
|
Hi @grooverdan @vuvova, we’ve added the initial version of the VIDEX documentation to address https://jira.mariadb.org/browse/MDEV-38409. Could you please review it? |
grooverdan
reviewed
Jan 19, 2026
| - A running MariaDB server you can connect to (the “target”). | ||
| - A MariaDB build that includes the `VIDEX` engine plugin (the “MariaDB-VIDEX”). | ||
| - For a quick start, the target MariaDB and MariaDB-VIDEX can be the same instance. | ||
| - Docker (to run VIDEX-Server and videx-sync). |
Contributor
There was a problem hiding this comment.
Docker -> A container runtime
mariadb-stefan-hinz
merged commit 806bb55
into
mariadb-corporation:main
1 of 2 checks passed
mariadb-stefan-hinz
added a commit
that referenced
this pull request
Jan 26, 2026
…nly one file. Add VIDEX to SUMMARY.md so that it shows up online.
Contributor
|
Build-time enablement section is gone, or maybe you’re talking about another section?
Cheers,
Stefan
--
Stefan Hinz
Documentation Consultant
***@***.***
+49-177-7841069
… On 2. Feb 2026, at 00:02, Sergei Golubchik ***@***.***> wrote:
@vuvova commented on this pull request.
In server/server-usage/storage-engines/videx/videx-storage-engine.md <#303 (comment)>:
> +
+---
+
+## 4. Install / enable the VIDEX plugin (MariaDB)
+
+### 4.1 Verify the engine
+
+Connect to your MariaDB instance and check whether `VIDEX` engine is available:
+
+```sql
+SHOW ENGINES;
+```
+
+If you see a row for `VIDEX` with `SUPPORT` as `YES` or `DEFAULT`, the engine is available.
+
+### 4.2 Build-time enablement
@grooverdan <https://github.com/grooverdan> I agree, and I've heard others expressing a similar sentiment, that 4.2 session shouldn't be here. May be we'll remove it.
—
Reply to this email directly, view it on GitHub <#303 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BOOL2ACWIYSVF4KGFF3UEPL4J2AYZAVCNFSM6AAAAACSDP3LJGVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTOMZWG44DMNBXGQ>.
You are receiving this because you modified the open/close state.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds an initial draft documentation page for the VIDEX storage engine.
server/server-usage/storage-engines/videx/videx-storage-engine.mdvidex-syncworkflow to build a VIDEX schemaEXPLAINbetween the original schema and the VIDEX schemavidex-server+ runvidex-sync).Related:
bytedance/videx: Docker: Add a separate videx-server image to support launching the server and executing the videx-sync scripts. bytedance/videx#82kangrongme/videx-server:0.2.0