Skip to content

Commit 225adc7

Browse files
AUTO: Sync ScalarDB docs in English to docs site repo (#1187)
Co-authored-by: josh-wong <[email protected]>
1 parent ed6dd2a commit 225adc7

File tree

1 file changed

+19
-2
lines changed

1 file changed

+19
-2
lines changed

docs/roadmap.mdx

Lines changed: 19 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -93,8 +93,10 @@ If you have a feature request or want to prioritize feature development, please
9393

9494
- **Native secondary index**
9595
- 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.
96-
- **Better catalog management**
97-
- Users will be able to manage a data catalog across diverse databases in a unified manner.
96+
- **Universal catalog**
97+
- Users will be able to manage metadata, including schemas and semantic information, for operational and analytical databases across separate business domains in a unified manner.
98+
- **Universal authentication and authorization**
99+
- Users will be able to be given access to ScalarDB Cluster and ScalarDB Analytics by using a unified authentication and authorization method.
98100

99101
#### Support for additional databases (object storage)
100102

@@ -116,3 +118,18 @@ If you have a feature request or want to prioritize feature development, please
116118
- Users will be able to use Red Hat–certified Helm Charts for ScalarDB Cluster in OpenShift environments.
117119
- **Container offering in Google Cloud Marketplace**
118120
- Users will be able to deploy ScalarDB Cluster by using the Google Cloud container offering, which enables users to use a pay-as-you-go subscription model.
121+
122+
### CY2026
123+
124+
- ** Audit Logging**
125+
- Users will be able to view and manage the access logs of ScalarDB Cluster and Analytics, mainly for auditing purposes.
126+
- **Stored procedures**
127+
- Users will be able to define stored procedures so that they can execute a set of operations with a complex logic inside ScalarDB Cluster.
128+
- **Triggers**
129+
- Users will be able to define triggers so that they can automatically execute a set of operations when a specific event occurs in ScalarDB Cluster.
130+
- **User-defined functions (UDFs)**
131+
- Users will be able to define functions so that they can use functions in SQLs to express complex logic in a simpler way.
132+
- **Addition of SQL operations for sorting**
133+
- Users will be able to issue sorting (ORDER BY) operations in ScalarDB SQL.
134+
- **Addition of more data types**
135+
- Users will be able to use complex data types, such as JSON.

0 commit comments

Comments
 (0)