querypie · jk-kim0 · Jul 13, 2026 · Jul 13, 2026 · Jul 13, 2026
@@ -14,9 +14,8 @@ This feature allows you to upload custom JDBC drivers to register and use Custom
 Previously, only the DB Vendors provided by QueryPie by default (MySQL, PostgreSQL, etc.) were available, but with this feature you can also connect to unsupported databases (e.g., Cubrid, Tibero, Altibase) by uploading their JDBC drivers directly.
 
 <Callout type="info">
-This feature is provided as **Beta**.
-To use it, you must set the **Custom JDBC Configuration** option to `Enable` in the Experimental section on the `Admin > Databases > General > Configurations` page.
-After activation, the `Admin > Databases > Connection Management > Custom JDBC Configs` menu will appear.
+This feature is available in version 11.6.x and later.
+(Provided as Beta from 11.6.0 through 11.6.4 and as a GA feature in 11.6.5)
 </Callout>
 
 ### Registering a Custom JDBC Vendor

@@ -12,9 +12,7 @@ import { Callout } from 'nextra/components'
 Starting from QueryPie ACP 11.6.0, the Custom JDBC Configs feature allows administrators to register a JDBC Driver and create a Databricks connection with policies applied.<br/>The query parser (QSI) supported by QueryPie ACP for Databricks is ANSI query, so Databricks-specific syntax may not work correctly.
 
 <Callout type="info">
-This feature is provided as **Beta**.
-To use it, you must set the **Custom JDBC Configuration** option to `Enable` in the Experimental section on the `Admin > Databases > General > Configurations` page.
-After activation, the `Admin > Databases > Connection Management > Custom JDBC Configs` menu will appear.
+This feature is available in version 11.6.x and later. (Provided as Beta from 11.6.0 through 11.6.4 and as a GA feature in 11.6.5)
 </Callout>
 
 ### Registering Databricks as a Custom JDBC Vendor
@@ -32,7 +30,8 @@ After activation, the `Admin > Databases > Connection Management > Custom JDBC C
 8. Enter `443` in the Default Port.
 9. Enter `--add-opens=java.base/java.nio=ALL-UNNAMED` in the JVM Arguments.
 10. Click the `Select JAR file to upload` button in the Driver JAR File section and upload the JDBC Driver.<br/>Databricks: [JDBC Driver Download](https://www.databricks.com/spark/jdbc-drivers-download)
-11. Click the `Save` button to save the configuration.
+11. Dictionary
+12. Click the `Save` button to save the configuration.
 
 ### Creating a Databricks Connection with a Custom Vendor
 

@@ -9,36 +9,38 @@ import { Callout } from 'nextra/components'
 
 ### Overview
 
-**QSI Parser** is an option that can be selected when creating or editing a DB Connection with a Custom JDBC Vendor.
-QSI Parser refers to the parser that QueryPie uses to analyze SQL, and selecting a Parser that matches the syntax characteristics of the DB Vendor can improve query analysis and policy application compatibility.
-
 <Callout type="info">
-This feature is provided together with the **Custom JDBC Vendor** feature.
-To use it, you must first set the **Custom JDBC Configuration** option to `Enable` in the Experimental section on the `Admin > Databases > General > Configurations` page, and register the Custom JDBC Vendor you want to use at `Admin > Databases > Connection Management > Custom JDBC Configs`.
+This feature is available in version 11.6.x and later. (Provided as Beta from 11.6.0 through 11.6.4 and as a GA feature in 11.6.5)
 </Callout>
 
-### Configuring the QSI Parser
+**QSI Parser** is an option that can be selected when creating or editing a DB Connection for a Custom JDBC Vendor or a database with selectable parsers.
+QSI Parser refers to the parser that QueryPie uses to analyze SQL, and selecting a Parser that matches the syntax characteristics of the DB Vendor can improve query analysis and policy application compatibility.
 
-Configure the QSI Parser for a DB Connection that uses a Custom JDBC Vendor.
+| **Database**       | **Selectable Parsers**                  | Version where parser selection became available |
+| ------------------ | --------------------------------------- | ----------------------------------------------- |
+| Custom Jdbc Vendor | `ANSI`, `PostgreSQL`, `MySQL`, `Trino`  | `11.6.1` and later                              |
+| Tibero             | `ANSI`, `Trino`                         | `11.6.1` and later                              |
+| Presto             | `ANSI`, `Trino`                         | `11.6.1` and later                              |
+| Teradata           | `ANSI`, `PostgreSQL`, `Trino`           | `11.6.1` and later                              |
+| Cubrid             | `ANSI`, `MySQL`                         | `11.6.2` and later                              |
+| Snowflake          | `ANSI`, `PostgreSQL`, `Trino`           | `11.6.3` and later                              |
 
-<figure data-layout="center" data-align="center">
-<img src="/administrator-manual/databases/connection-management/custom-jdbc-configs/qsi-parser-selection/database-settings_connection-management_db-connections_qsi-parser.png" alt="database-settings_connection-management_db-connections_qsi-parser.png" width="680" />
-</figure>
+### Configuring the QSI Parser
+
+Configure the QSI Parser for a DB Connection where parser selection is available.
 
 1. Navigate to `Admin > Databases > Connection Management > DB Connections`.
 2. Click the `Create Connection` button in the upper right corner, or select an existing connection to go to the edit screen.
-3. Scroll down and select the Custom JDBC Vendor you want to use from the **Custom JDBC Vendors** section.
+3. Scroll down and select the Custom JDBC Vendor you want to use from the **Custom JDBC Vendors** section. (Or select one of the previously mentioned Tibero, Presto, Teradata, Cubrid, or Snowflake entries.)
 4. Enter the connection information in the `Connection Information` section.
-5. When the **QSI Parser** field appears, select the appropriate Parser for the Vendor.
-    * For Custom JDBC Vendors, a list of compatible Parsers is provided in a dropdown.
+5. Select the **Use QSI Parser** checkbox.<br/>
+  <figure data-layout="center" data-align="center">
+  <img src="/administrator-manual/databases/connection-management/custom-jdbc-configs/qsi-parser-selection/image-20260713-045912.png" alt="image-20260713-045912.png" width="654" />
+  </figure>
+    * A list of compatible Parsers is provided in a dropdown.
     * Examples: `ANSI SQL`, `Oracle`, `PostgreSQL`, `MySQL`, `Trino`
 6. Enter the remaining connection information and click the `Next` button to proceed to the connection creation complete screen.
 
-<Callout type="important">
-As of the 11.6.0 admin UI, the **QSI Parser** field is only displayed when a Custom JDBC Vendor is selected.
-Additionally, the dropdown is only shown when there are two or more selectable Parsers for the Vendor.
-</Callout>
-
 ### QSI Parser Selection Criteria
 
 It is recommended to select the QSI Parser that most closely matches the SQL syntax of the target database.
@@ -59,7 +61,7 @@ Select a Parser from the same family as the SQL syntax verified when registering
 You can change the QSI Parser of an existing DB Connection.
 
 1. Select the connection you want to edit from `Admin > Databases > Connection Management > DB Connections`.
-2. Change the **QSI Parser** value in the `Connection Information` section.
+2. Change the **QSI Parser** value in the `Connection Information` section. (You can also clear the Use QSI Parser checkbox if needed. **If policies are configured, they may be invalidated, so review carefully before changing this setting.**)
 3. Click the `Save Changes` button to save.
 
 After changing the setting, query analysis results for the connection may differ, so verify the behavior with representative SQL queries if needed.
@@ -16,9 +16,8 @@ For example, you can exclude (SKIP) heartbeat queries periodically executed by C
 When multiple rules are registered, they are evaluated in order of Priority, and the first matching rule is applied.
 
 <Callout type="info">
-This feature is provided as **Beta**.
-To use it, you must set the **Query Rules** option to `Enable` in the Experimental section on the `Admin > Databases > General > Configurations` page.
-After enabling, the `Admin > Databases > Policies > Query Rules` menu will appear.
+This feature is available in **version 11.6.x and later**.
+(Provided as `Beta` from 11.6.0 through 11.6.4 and as a `GA` feature in 11.6.5)
 </Callout>
 
 <Callout type="important">

@@ -11,20 +11,20 @@ This page provides information about official releases of QueryPie ACP.
 
 These are the official QueryPie ACP releases currently available for installation and operation.
 
-| **Version** | **Build Tag**    | **Release Note**                                  | **Release Date** | **Status**                   |
-| ----------- | ---------------- | ------------------------------------------------- | ---------------- | ---------------------------- |
-| 11.6.5      | `11.6.5-ba8dd33` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | Jul 2, 2026      | Ready for Community Edition  |
-| 11.6.4      | `11.6.4-9be1f67` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | Jun 23, 2026     | Outdated                     |
-| 11.6.3      | `11.6.3-fc0a230` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | May 28, 2026     | Deprecated                   |
-| 11.6.2      | `11.6.2-151a452` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | Apr 16, 2026     | Deprecated                   |
-| 11.6.1      | `11.6.1-44ad3a9` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | Mar 20, 2026     | Deprecated                   |
-| 11.6.0      | `11.6.0-886d8e8` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | Feb 13, 2026     | Deprecated                   |
-| 11.5.7      | `11.5.7-2db5ae7` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | Jul 2, 2026      | Ready for Enterprise Edition |
-| 11.5.6      | `11.5.6-ec6acc4` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | May 28, 2026     | Deprecated                   |
-| 11.5.5      | `11.5.5-7c5b73d` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | Apr 16, 2026     | Deprecated                   |
-| 11.5.4      | `11.5.4-702dd33` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | Mar 20, 2026     | Deprecated                   |
-| 11.5.1      | `11.5.1-e0fc574` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | Jan 23, 2026     | Deprecated                   |
-| 11.5.0      | `11.5.0-dce9f84` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | Dec 16, 2025     | Deprecated                   |
+| **Version** | **Build Tag**    | **Release Note**                                  | **Release Date** | **Status**                                         |
+| ----------- | ---------------- | ------------------------------------------------- | ---------------- | -------------------------------------------------- |
+| 11.6.5      | `11.6.5-ba8dd33` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | Jul 2, 2026      | Ready for Community Edition and Enterprise Edition |
+| 11.6.4      | `11.6.4-9be1f67` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | Jun 23, 2026     | Outdated                                           |
+| 11.6.3      | `11.6.3-fc0a230` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | May 28, 2026     | Deprecated                                         |
+| 11.6.2      | `11.6.2-151a452` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | Apr 16, 2026     | Deprecated                                         |
+| 11.6.1      | `11.6.1-44ad3a9` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | Mar 20, 2026     | Deprecated                                         |
+| 11.6.0      | `11.6.0-886d8e8` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | Feb 13, 2026     | Deprecated                                         |
+| 11.5.7      | `11.5.7-2db5ae7` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | Jul 2, 2026      | Ready for Enterprise Edition                       |
+| 11.5.6      | `11.5.6-ec6acc4` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | May 28, 2026     | Deprecated                                         |
+| 11.5.5      | `11.5.5-7c5b73d` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | Apr 16, 2026     | Deprecated                                         |
+| 11.5.4      | `11.5.4-702dd33` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | Mar 20, 2026     | Deprecated                                         |
+| 11.5.1      | `11.5.1-e0fc574` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | Jan 23, 2026     | Deprecated                                         |
+| 11.5.0      | `11.5.0-dce9f84` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | Dec 16, 2025     | Deprecated                                         |
 
 #### Status
 
@@ -37,13 +37,13 @@ These are the official QueryPie ACP releases currently available for installatio
 
 QueryPie ACP provides container images through the following container registries.
 
-#### Docker Hub (Recommended)
+#### Docker Hub
 
 Registry location: `docker.io/querypie` ([https://hub.docker.com/u/querypie](https://hub.docker.com/u/querypie))
 
 Example: `docker pull docker.io/querypie/querypie:11.6.4`
 
-* Available for Community / Standard / Enterprise Editions.
+* This container registry is provided for Community Edition and Standard Edition users.
 * Recommended for new installations.
 * No authentication required.
 * Provides `linux/amd64`, `linux/arm64`, and multi-platform images.
@@ -52,7 +52,8 @@ Example: `docker pull docker.io/querypie/querypie:11.6.4`
 
 Registry location: `harbor.chequer.io/querypie`
 
-This is a private container registry provided for compatibility with existing installation and operation environments. You must authenticate using the `docker login` command to download container images.
+This is a private container registry provided for Enterprise Edition users.
+All legacy versions used by customers are provided. You must authenticate using the `docker login` command to download container images.
 Please contact your technical support partner to obtain the username and password for accessing this container registry.
 
 #### Edition Compatibility

@@ -14,14 +14,13 @@ It also offers user- and admin-friendly features that improve productivity.
 Manage your dispersed assets and permissions in one place with QueryPie ACP.
 
 <figure data-layout="center" data-align="center">
-<img src="/overview/QueryPie-ACP-Overview.png" alt="How QueryPie Access Control Platform Works" width="760" />
+<img src="/overview/QueryPie_ACP.png" alt="How QueryPie Access Control Platform Works" width="760" />
 <figcaption>
 How QueryPie Access Control Platform Works
 </figcaption>
 </figure>
 
 
-
 ### Using This Manual
 
 QueryPie ACP continuously explores ways to securely protect sensitive data within enterprises, even in cloud environments.

@@ -14,9 +14,8 @@ import { Callout } from 'nextra/components'
 従来はQueryPieがデフォルトで提供するDB Vendor（MySQL、PostgreSQLなど）のみ使用可能でしたが、この機能を通じてサポートされていないDB（例：Cubrid、Tibero、Altibaseなど）もJDBCドライバを直接アップロードして接続できます。
 
 <Callout type="info">
-本機能は**ベータ（Beta）**として提供されます。
-使用するには、`Admin > Databases > General > Configurations` ページのExperimentalセクションで **Custom JDBC Configuration** オプションを `Enable` に設定する必要があります。
-有効化後、`Admin > Databases > Connection Management > Custom JDBC Configs` メニューが表示されます。
+本機能は11.6.xバージョン以降で提供されます。
+（11.6.0〜11.6.4まではBeta、11.6.5で正式機能として提供）
 </Callout>
 
 ### Custom JDBC Vendorを登録する

@@ -12,9 +12,7 @@ import { Callout } from 'nextra/components'
 QueryPie ACP 11.6.0から提供されるCustom JDBC Configs機能を通じて、管理者がJDBC Driverを登録し、Databricksコネクションを作成してポリシーを適用できます。<br/>QueryPie ACPでDatabricksに対してサポートするquery parser（QSI）はANSI queryであるため、Databricks特化構文については正常に動作しない場合があります。
 
 <Callout type="info">
-本機能は**ベータ（Beta）**として提供されます。
-使用するには、`Admin > Databases > General > Configurations` ページのExperimentalセクションで **Custom JDBC Configuration** オプションを `Enable` に設定する必要があります。
-有効化後、`Admin > Databases > Connection Management > Custom JDBC Configs` メニューが表示されます。
+本機能は11.6.xバージョン以降で提供されます。（11.6.0〜11.6.4まではBeta、11.6.5で正式機能として提供）
 </Callout>
 
 ### Custom JDBC VendorとしてDatabricksを登録する
@@ -32,7 +30,8 @@ QueryPie ACP 11.6.0から提供されるCustom JDBC Configs機能を通じて、
 8. Default Portに `443` を入力します。
 9. JVM Argumentsに `--add-opens=java.base/java.nio=ALL-UNNAMED` を入力します。
 10. Driver JAR Fileセクションで `Select JAR file to upload` ボタンをクリックしてJDBC Driverをアップロードします。<br/>Databricks：[JDBC Driverダウンロード](https://www.databricks.com/spark/jdbc-drivers-download)
-11. `Save` ボタンを押して設定を保存します。
+11. Dictionary
+12. `Save` ボタンを押して設定を保存します。
 
 ### Custom VendorでDatabricks Connectionを作成する