These enhancements were added for all platforms unless specified in the title for a specific platform.
Triggers Supported on Object File System Tables
VantageCloud Lake now supports triggers on tables in the Object File System.
Scaling Primary Cluster Up and Down
When you initially provision an environment, you specify the instance size of the primary cluster.
After provisioning your enviroment, you can scale the original instance size up or down by up to two instance sizes.
Scale up for short-term increases in workload and data-intensive tasks to maintain optimal performance or speed up processing.
Scale down during periods of reduced demand to avoid paying for unused resources.
To scale your primary cluster up or down, you must submit a request. See Scaling Primary Cluster Up and Down.
Block Storage Expansion for Primary Cluster
When you initially provision an environment, you specify the amount of block storage you want for the primary cluster.
After provisioning your environment, you can add block storage to the primary cluster in increments of 1 TB.
Block Storage expansion for the primary cluster cannot be reduced (rolled back) after being incremented.
To add block storage to the primary cluster, you must submit a request. See Block Storage.
Consumption Alert Email Notifications
Set alerts to notify you and others that consumption is approaching a threshold. More than one alert can be set for each organization. See Viewing and Configuring Consumption Alerts.
Single Table Join Indexes on Object File System Tables
Starting with this release, Single Table Join Indexes (STJIs) are supported on Object File System tables on the primary index. See Querying Object File System Data.
External Object Storage Platform Support
- Cloudera
- Cloudian HyperStore
- IBM Cloud Object Store (IBM COS)
- RedHat Ceph
- Scality Ring
- VAST Data
- Vcinity VAccess
Default DBQL Logging Value
For DBQL logging, detail logging is the default on VantageCloud Lake. For users or accounts running tactical workloads, the recommendation is to enable DBQL Summary/Threshold logging, so the logging volume is nominal. The summary log can be accessed using td_metric_svc.dbqlsummaryV. See Tracking Query Behavior with Database Query Logging: Operational DBAs.
Recommendations for Using Analytic Functions
Use ASCII client collation when executing analytic functions. If your data has UNICODE characters, set the UTF8 client character set and Collation set to ASCII for the user session. See Recommendations for Using Analytic Functions.