Skip to content

Commit 561102c

Browse files
committed
AUTO: Sync ScalarDB docs in English to docs site repo
1 parent 118fe55 commit 561102c

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

versioned_docs/version-3.14/roadmap.mdx

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -61,28 +61,28 @@ If you have a feature request or want to prioritize feature development, please
6161
- **Container offering in Amazon Marketplace for ScalarDB Analytics**
6262
- Users will be able to deploy ScalarDB Analytics by using the container offering, which enables users to use a pay-as-you-go subscription model.
6363
- **Red Hat OpenShift support**
64-
- Users will be able to use Red Hat–certified Helm Charts for ScalarDB Cluster in OpenShift environments.
64+
- Users will be able to deploy ScalarDB Cluster in Red Hat OpenShift.
6565

6666
#### AI/LLM support
6767

6868
- **Model Context Protocol (MCP) server**
6969
- Users will be able to use the MCP server of ScalarDB Core and ScalarDB Cluster to interact with them by using AI and large language model (LLM) applications. The MCP server will provide a way to communicate with ScalarDB by using natural language, enabling users to perform operations like querying and managing data in a more intuitive manner.
7070
- **LLM-friendly rule files for ScalarDB**
71-
- Users will be able to ask questions and tasks to LLMs by using the LLM-friendly rule files so that LLMs can work for them with better understanding of ScalarDB. The rule files will be designed to provide LLMs with the necessary context and instructions to effectively interact with ScalarDB, making it easier for users to leverage AI capabilities in their applications.
71+
- Users will be able to ask questions and tasks to LLMs by using the LLM-friendly rule files so that LLMs can work for them with a better understanding of ScalarDB. The rule files will be designed to provide LLMs with the necessary context and instructions to effectively interact with ScalarDB, making it easier for users to leverage AI capabilities in their applications.
7272

7373
### CY2025 Q4
7474

7575
#### New features
7676

7777
- **Native secondary index**
78-
- Users will be able to define flexible secondary indexes. The existing secondary index is limited because it is implemented based on the common capabilities of the supported databases' secondary indexes. Therefore, for example, you cannot define a multi-column index. The new secondary index will be created at the ScalarDB layer so that you can create more flexible indexes, like a multi-column index.
78+
- Users will be able to define flexible secondary indexes. The existing secondary index is limited because it is implemented based on the common capabilities of the supported databases' secondary indexes. Therefore, for example, users cannot define a multi-column index. The new secondary index will be created at the ScalarDB layer so that users can create more flexible indexes, like a multi-column index.
7979
- **Two-layered query engines**
8080
- Users will be able to use two-layered query engines to better federate analytical queries across domains. The first-layer query engine is responsible for federating analytical queries across various domains, while the second-layer query engine federates analytical queries within a specific domain across its corresponding databases.
8181

8282
#### Usability
8383

84-
- **Addition of decimal data types**
85-
- Users will be able to use decimal data types so that users can handle decimal numbers with high precision.
84+
- **Addition of DECIMAL data types**
85+
- Users will be able to use DECIMAL data types so that users can handle decimal numbers with high precision.
8686
- **Elimination of out-of-memory errors due to large scans**
8787
- Users will be able to issue large scans without experiencing out-of-memory errors.
8888

@@ -120,4 +120,4 @@ If you have a feature request or want to prioritize feature development, please
120120
- **Addition of SQL operations for sorting**
121121
- Users will be able to issue arbitrary sorting (ORDER BY) operations in ScalarDB SQL for multiple or non-JDBC databases. (Currently, ScalarDB can issue sorting operations using clustering keys or arbitrary sorting operations for single JDBC databases.)
122122
- **Addition of more data types**
123-
- Users will be able to use complex data types, such as JSON.
123+
- Users will be able to use complex data types, such as JSON.

0 commit comments

Comments
 (0)