You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: versioned_docs/version-3.9/roadmap.mdx
+34-18Lines changed: 34 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,47 +17,63 @@ If you have a feature request or want to prioritize feature development, please
17
17
18
18
:::
19
19
20
-
### CY2025 Q3
20
+
### CY2025 Q4
21
21
22
22
#### New capabilities
23
23
24
24
-**SQL interface for generic contracts for tables**
25
25
- Users will be able to use SQL-like queries to access generic contracts for tables so that they can simplify their application development.
26
26
27
-
#### Cloud support
28
-
29
-
-**Red Hat OpenShift support**
30
-
- Users will be able to use Red Hat–certified Helm Charts for ScalarDL in OpenShift environments.
31
-
-**Google Cloud Platform (GCP) support**
32
-
- Users will be able to deploy ScalarDL in Google Kubernetes Engine (GKE) in GCP.
33
-
34
-
### CY2025 Q4
27
+
### CY2026 Q1
35
28
36
29
#### New capabilities
37
30
38
31
-**Namespaces**
39
32
- Users will be able to use namespaces to group assets so that they can better manage their data.
40
33
41
34
#### Usability
42
-
-**Elimination of out-of-memory errors due to large scans**
43
-
- Users will be able to issue large scans without experiencing out-of-memory errors.
35
+
36
+
-**Java upgrade to version 21**
37
+
- Users will be able to run ScalarDL (except for the client SDK) on Java 21 so that they can use the latest features and improvements in Java.
44
38
-**Enable read operations during a paused duration.**
45
39
- Users will be able to issue read operations even during a paused duration so that users can still read data while taking backups.
46
40
47
41
#### Cloud support
48
42
49
-
-**Container offering in Google Cloud Marketplace**
50
-
- Users will be able to deploy ScalarDL by using the Google Cloud container offering, which enables users to use a pay-as-you-go subscription model.
51
-
-**Container offering in Azure Marketplace**
52
-
- Users will be able to deploy ScalarDL by using the Azure container offering, which enables users to use a pay-as-you-go subscription model.
43
+
-**Google Cloud Platform (GCP) support**
44
+
- Users will be able to deploy ScalarDL by using the GCP marketplace offering, which enables users to use a pay-as-you-go subscription model.
45
+
-**Azure support**
46
+
- Users will be able to deploy ScalarDL by using the Azure marketplace offering, which enables users to use a pay-as-you-go subscription model.
47
+
48
+
### CY2026 Q2
53
49
54
-
###CY2026
50
+
#### New capabilities
55
51
56
52
-**Lifecycle management for assets**
57
53
- Users will be able to better manage the lifecycle of assets, ensuring they are preserved securely for an extended period.
54
+
55
+
#### Improvements
56
+
57
+
-**Encryption**
58
+
- Users will be able to encrypt their data so that they can manage their data in a more secure way.
59
+
-**Elimination of out-of-memory errors due to large scans**
60
+
- Users will be able to issue large scans without experiencing out-of-memory errors.
61
+
62
+
#### Cloud support
63
+
64
+
-**Red Hat OpenShift support**
65
+
- Users will be able to use Red Hat–certified Helm Charts for ScalarDL in OpenShift environments.
66
+
-**AWS support**
67
+
- Users will be able to deploy ScalarDL by using the AWS marketplace offering, which enables users to use a pay-as-you-go subscription model.
68
+
69
+
### CY2026 Q3
70
+
71
+
#### Improvements
72
+
58
73
-**Performance optimizations**
59
74
- Users will be able to execute requests faster so that they can create ScalarDL applications in a more cost-effective way.
75
+
76
+
### CY2026 Q4 -
77
+
60
78
-**Lazy validation**
61
79
- Users will be able to validate the authenticity of their data lazily so that they can manage their data in a cost-effective way if their data doesn't need to be validated in real time.
62
-
-**Encryption**
63
-
- Users will be able to encrypt their data so that they can manage their data in a more secure way.
0 commit comments