<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Vertica Documentation – New and changed in Vertica 12.0.1</title>
    <link>/en/new-features/12.0.1/</link>
    <description>Recent content in New and changed in Vertica 12.0.1 on Vertica Documentation</description>
    <generator>Hugo -- gohugo.io</generator>
    
	  <atom:link href="/en/new-features/12.0.1/index.xml" rel="self" type="application/rss+xml" />
    
    
      
        
      
    
    
    <item>
      <title>New-Features: admintools</title>
      <link>/en/new-features/12.0.1/admin/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/new-features/12.0.1/admin/</guid>
      <description>
        
        
        &lt;h2 id=&#34;stop_db-and-stop_subcluster-graceful-shutdown&#34;&gt;stop_db and stop_subcluster graceful shutdown&lt;/h2&gt;
&lt;p&gt;When you run the &lt;a href=&#34;../../../en/admin/using-admin-tools/admin-tools-reference/writing-admin-tools-scripts/&#34;&gt;admintools commands&lt;/a&gt; &lt;code&gt;stop_db&lt;/code&gt; and &lt;code&gt;stop_subcluster&lt;/code&gt; on an Eon Mode database, the default behavior is now to gracefully shut down the specified subclusters. Both commands provide override options that force immediate shutdown of the target subclusters.&lt;/p&gt;
&lt;p&gt;For examples, see &lt;a href=&#34;../../../en/admin/operating-db/stopping-db/&#34;&gt;Stopping the database&lt;/a&gt; and &lt;a href=&#34;../../../en/eon/managing-subclusters/starting-and-stopping-subclusters/#Stopping&#34;&gt;Stopping a Subcluster&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;fast-startup&#34;&gt;Fast startup&lt;/h2&gt;
&lt;p&gt;The admintools command 
&lt;code&gt;&lt;a href=&#34;../../../en/admin/operating-db/starting-db/&#34;&gt;start_db&lt;/a&gt;&lt;/code&gt; has a new &lt;code&gt;--fast&lt;/code&gt; option for starting Eon Mode databases. When invoked on an unencrypted database, Vertica uses startup information from &lt;code&gt;cluster_config.json&lt;/code&gt; to expedite the startup process.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>New-Features: Client drivers</title>
      <link>/en/new-features/12.0.1/client-drivers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/new-features/12.0.1/client-drivers/</guid>
      <description>
        
        
        &lt;h2 id=&#34;oauthjsonconfig-precedence&#34;&gt;OAuthJsonConfig precedence&lt;/h2&gt;
&lt;p&gt;The connection parameters oauthjsonconfig (&lt;a href=&#34;../../../en/connecting-to/client-libraries/client-drivers/install-config/odbc/creating-an-odbc-data-source-name-dsn/odbc-dsn-connection-properties/&#34;&gt;ODBC&lt;/a&gt;) and OAuthJsonConfig (&lt;a href=&#34;../../../en/connecting-to/client-libraries/accessing/java/creating-and-configuring-connection/jdbc-connection-properties/&#34;&gt;JDBC&lt;/a&gt;) now take precedence over the deprecated OAuth parameters:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;OAuthAccessToken/oauthaccesstoken&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;OAuthRefreshToken/oauthrefreshtoken&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;OAuthClientId/oauthclientid&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;OAuthClientSecret/oauthclientsecret&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;OAuthTokenUrl/oauthtokenurl&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;OAuthDiscoveryUrl/oauthdiscoveryurl&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;OAuthScope/oauthscope&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>New-Features: Complex types</title>
      <link>/en/new-features/12.0.1/complex-types/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/new-features/12.0.1/complex-types/</guid>
      <description>
        
        
        &lt;h2 id=&#34;add-new-fields-to-complex-type-columns&#34;&gt;Add new fields to complex type columns&lt;/h2&gt;
&lt;p&gt;Previously, Vertica did not allow you to change the fields of complex type columns in native tables. Now, you can add new fields to an existing complex type column using &lt;a href=&#34;../../../en/sql-reference/statements/alter-statements/alter-table/&#34;&gt;ALTER TABLE&lt;/a&gt;. See &lt;a href=&#34;../../../en/admin/working-with-native-tables/managing-table-columns/adding-new-field-to-complex-type-column/&#34;&gt;Adding a new field to a complex type column&lt;/a&gt; for details.&lt;/p&gt;
&lt;h2 id=&#34;field-aliases-in-row-literals&#34;&gt;Field aliases in ROW literals&lt;/h2&gt;
&lt;p&gt;In &lt;a href=&#34;../../../en/sql-reference/data-types/complex-types/row/&#34;&gt;ROW&lt;/a&gt; literals, you can now name individual fields using AS. The following two statements are equivalent:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;=&amp;gt; SELECT ROW(&amp;#39;Amy&amp;#39; AS name, 2 AS id, false AS current) AS student;

=&amp;gt; SELECT ROW(&amp;#39;Amy&amp;#39;, 2, false) AS student(name, id, current);
&lt;/code&gt;&lt;/pre&gt;
      </description>
    </item>
    
    <item>
      <title>New-Features: Containers and Kubernetes</title>
      <link>/en/new-features/12.0.1/containers-and-k8s/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/new-features/12.0.1/containers-and-k8s/</guid>
      <description>
        
        
        &lt;h2 id=&#34;elevate-security-context-privileges-for-core-files&#34;&gt;Elevate security context privileges for core files&lt;/h2&gt;
&lt;p&gt;The &lt;code&gt;securityContext&lt;/code&gt; custom resource definition parameter can elevate Vertica server container privileges so that you can perform privileged actions, such as create core files that contain information about the Vertica server process.&lt;/p&gt;
&lt;p&gt;For details, see &lt;a href=&#34;../../../en/containerized/custom-resource-definition-parameters/&#34;&gt;Custom resource definition parameters&lt;/a&gt; and &lt;a href=&#34;../../../en/containerized/troubleshooting-your-k8s-cluster/&#34;&gt;Troubleshooting your Kubernetes cluster&lt;/a&gt;. For additional details about security context, see the &lt;a href=&#34;https://github.com/kubernetes-client/go/blob/master/kubernetes/docs/V1SecurityContext.md&#34;&gt;Kubernetes documentation&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;resize-persistent-volumes-automatically-on-managed-kubernetes-services&#34;&gt;Resize persistent volumes automatically on managed Kubernetes services&lt;/h2&gt;
&lt;p&gt;When you use a storageClass that allows volume expansion and you allocate depot storage with a percentage of the total disk space, the operator automatically adjusts the size of the PV and the depot when you update &lt;code&gt;spec.local.requestSize&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;For details, see &lt;a href=&#34;../../../en/containerized/custom-resource-definition-parameters/&#34;&gt;Custom resource definition parameters&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;override-helm-chart-object-naming-convention&#34;&gt;Override helm chart object naming convention&lt;/h2&gt;
&lt;p&gt;The &lt;code&gt;nameOverride&lt;/code&gt; Helm chart parameter sets the naming prefix for all objects that the Helm chart creates.&lt;/p&gt;
&lt;p&gt;For details, see &lt;a href=&#34;../../../en/containerized/db-operator/helm-chart-parameters/&#34;&gt;Helm chart parameters&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;java-8-support-in-the-vertica-server-image&#34;&gt;Java 8 support in the Vertica server image&lt;/h2&gt;
&lt;p&gt;The Vertica server image includes the Java 8 OpenJDK so that you can develop Java UDx and use the Java runtime in your Vertica environment.&lt;/p&gt;
&lt;p&gt;For details about Java UDx development, see &lt;a href=&#34;../../../en/extending/developing-udxs/developing-with-sdk/java-sdk/&#34;&gt;Java SDK&lt;/a&gt;. For a detailed list of Vertica images, see &lt;a href=&#34;../../../en/containerized/&#34;&gt;Containerized Vertica&lt;/a&gt;.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>New-Features: Machine learning</title>
      <link>/en/new-features/12.0.1/ml/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/new-features/12.0.1/ml/</guid>
      <description>
        
        
        &lt;h2 id=&#34;isolation-forest&#34;&gt;Isolation forest&lt;/h2&gt;
&lt;p&gt;The &lt;a href=&#34;../../../en/sql-reference/functions/ml-functions/transformation-functions/apply-iforest/&#34;&gt;APPLY_IFOREST&lt;/a&gt; function now supports a &lt;code&gt;contamination&lt;/code&gt; parameter that specifies the approximate ratio of data points in the training data that are labeled as outliers. The function uses this &lt;code&gt;contamination&lt;/code&gt; value to calculate an anomaly score threshold, a minimum limit that determines whether an input data point is marked as an outlier. You can set &lt;code&gt;contamination&lt;/code&gt; instead of setting a threshold explicitly with the &lt;code&gt;threshold&lt;/code&gt; parameter.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>New-Features: Management Console</title>
      <link>/en/new-features/12.0.1/mc/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/new-features/12.0.1/mc/</guid>
      <description>
        
        
        &lt;h2 id=&#34;eon-mode-root-volume-encryption-on-aws&#34;&gt;Eon Mode root volume encryption on AWS&lt;/h2&gt;
&lt;p&gt;On Eon Mode on Amazon Web Services (AWS), the root volume is encrypted by default when you perform any of the following operations with Management Console:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Provision a database&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Revive a database&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Scale up a database&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Add a new subcluster&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For details, see &lt;a href=&#34;../../../en/mc/cloud-platforms/aws-mc/&#34;&gt;Amazon Web Services in MC&lt;/a&gt; and &lt;a href=&#34;../../../en/mc/db-management/subclusters-mc/&#34;&gt;Subclusters in MC&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;support-gp3-volume-type-on-aws&#34;&gt;Support gp3 volume type on AWS&lt;/h2&gt;
&lt;p&gt;Vertica supports the gp3 volume type as the default volume type for root and EBS volumes on Amazon Web Services (AWS). The gp3 volume type is more cost-efficient and has better performance for input/output operations per second (IOPS) than the gp2 volume type. For details, see the &lt;a href=&#34;https://aws.amazon.com/ebs/general-purpose/&#34;&gt;Amazon gp3 product overview documentation&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Vertica uses gp3 volumes as the default volume type for the following operations in both Enterprise Mode and Eon Mode:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Create a database&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Revive a database&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Add a subcluster&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Scale up a subcluster&lt;/p&gt;

&lt;div class=&#34;alert admonition note&#34; role=&#34;alert&#34;&gt;
&lt;h4 class=&#34;admonition-head&#34;&gt;Note&lt;/h4&gt;

If the existing subcluster uses gp2 volumes, the scale-up operation adds gp2 volumes to the existing subcluster.

&lt;/div&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Additionally, the Vertica &lt;a href=&#34;../../../en/setup/set-up-on-cloud/on-aws/deploy-using-cloudformation-templates/&#34;&gt;CloudFormation Template (CFT)&lt;/a&gt; uses the gp3 volume as the default volume type.&lt;/p&gt;
&lt;p&gt;For details about Vertica on AWS, see the following:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;a href=&#34;../../../en/setup/set-up-on-cloud/on-aws/&#34;&gt;Vertica on Amazon Web Services&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a href=&#34;../../../en/mc/cloud-platforms/aws-mc/&#34;&gt;Amazon Web Services in MC&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a href=&#34;../../../en/mc/db-management/subclusters-mc/&#34;&gt;Subclusters in MC&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;aws-cluster-creation-i4i-instance-type-support&#34;&gt;AWS cluster creation i4i instance type support&lt;/h2&gt;
&lt;p&gt;Management Console now supports three AWS i4i instance types for database cluster creation. For configuration details, see &lt;a href=&#34;../../../en/mc/cloud-platforms/aws-mc/enterprise-volume-config-defaults-aws/&#34;&gt;Enterprise Mode volume configuration defaults for AWS&lt;/a&gt; and &lt;a href=&#34;../../../en/mc/cloud-platforms/aws-mc/eon-volume-config-defaults-aws/&#34;&gt;Eon Mode volume configuration defaults for AWS&lt;/a&gt;.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>New-Features: Performance improvements</title>
      <link>/en/new-features/12.0.1/performance-improvements/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/new-features/12.0.1/performance-improvements/</guid>
      <description>
        
        
        &lt;h2 id=&#34;refresh_columns&#34;&gt;REFRESH_COLUMNS&lt;/h2&gt;
&lt;p&gt;Refreshing a &lt;a href=&#34;../../../en/admin/working-with-native-tables/managing-table-columns/defining-column-values/#SET_USING&#34;&gt;SET USING&lt;/a&gt; column where SET USING is set to a constant value such as null has been optimized. Compared to previous releases, calling &lt;a href=&#34;../../../en/sql-reference/functions/management-functions/projection-functions/refresh-columns/&#34;&gt;REFRESH_COLUMNS&lt;/a&gt; in REBUILD mode now performs significantly faster when it repopulates a SET USING column with constant values.&lt;/p&gt;
&lt;p&gt;One exception applies: this optimization does not apply to SET USING subqueries such as SELECT null.&lt;/p&gt;
&lt;h2 id=&#34;backuprestore&#34;&gt;Backup/restore&lt;/h2&gt;
&lt;p&gt;Better manifest processing and garbage collection have significantly improved performance of vbr backup and restore operations.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>New-Features: S3 object store</title>
      <link>/en/new-features/12.0.1/s3-object-store/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/new-features/12.0.1/s3-object-store/</guid>
      <description>
        
        
        &lt;h2 id=&#34;server-side-encryption-sse&#34;&gt;Server-side encryption (SSE)&lt;/h2&gt;
&lt;p&gt;Vertica now supports all three types of S3 server-side encryption: SSE-S3, SSE-KMS, and SSE-C. See &lt;a href=&#34;../../../en/sql-reference/file-systems-and-object-stores/s3-object-store/&#34;&gt;S3 object store&lt;/a&gt;.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>New-Features: Security and authentication</title>
      <link>/en/new-features/12.0.1/security-and-authentication/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/new-features/12.0.1/security-and-authentication/</guid>
      <description>
        
        
        &lt;h2 id=&#34;custom-tls-configurations&#34;&gt;Custom TLS configurations&lt;/h2&gt;
&lt;p&gt;You can now &lt;a href=&#34;../../../en/sql-reference/statements/create-statements/create-tls-config/&#34;&gt;create custom TLS Configurations&lt;/a&gt; and assign them to the following database parameters to secure different connection types:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;ServerTLSConfig&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;HttpsTLSConfig&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;LDAPLinkTLSConfig&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;LDAPAuthTLSConfig&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;InternodeTLSConfig&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For details, see &lt;a href=&#34;../../../en/sql-reference/config-parameters/security-parameters/&#34;&gt;Security parameters&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;internodetlsconfig-tlsmode&#34;&gt;InternodeTLSConfig TLSMODE&lt;/h2&gt;
&lt;p&gt;You can now set the TLSMODE for internode encryption with &lt;a href=&#34;../../../en/sql-reference/statements/alter-statements/alter-tls-config/&#34;&gt;ALTER TLS CONFIGURATION&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;For details on data channel TLS, see &lt;a href=&#34;../../../en/security-and-authentication/internode-tls/data-channel-tls/&#34;&gt;Data channel TLS&lt;/a&gt;.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>New-Features: SQL functions and statements</title>
      <link>/en/new-features/12.0.1/sql-functions-and-statements/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/new-features/12.0.1/sql-functions-and-statements/</guid>
      <description>
        
        
        &lt;h2 id=&#34;create-and-drop-tls-configurations&#34;&gt;CREATE and DROP TLS configurations&lt;/h2&gt;
&lt;p&gt;You can now &lt;a href=&#34;../../../en/sql-reference/statements/create-statements/create-tls-config/&#34;&gt;create&lt;/a&gt; and &lt;a href=&#34;../../../en/sql-reference/statements/drop-statements/drop-tls-config/&#34;&gt;drop&lt;/a&gt; TLS Configurations.&lt;/p&gt;
&lt;h2 id=&#34;refresh_columns-updates&#34;&gt;REFRESH_COLUMNS updates&lt;/h2&gt;
&lt;p&gt;The &lt;a href=&#34;../../../en/sql-reference/functions/management-functions/projection-functions/refresh-columns/&#34;&gt;REFRESH_COLUMNS&lt;/a&gt; function now supports a Boolean flag that specifies whether to split ROS containers if the range of partition keys to refresh spans multiple containers or part of a single container. By default, this flag is set to true: split ROS containers as needed.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>New-Features: Users and privileges</title>
      <link>/en/new-features/12.0.1/users-and-privileges/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/new-features/12.0.1/users-and-privileges/</guid>
      <description>
        
        
        &lt;h2 id=&#34;expanded-cryptographic-privileges&#34;&gt;Expanded cryptographic privileges&lt;/h2&gt;
&lt;p&gt;Keys, certificates, and TLS Configurations now support granting and revoking privileges.&lt;/p&gt;
&lt;p&gt;Superusers have limited privileges on cryptographic objects that they do not own. For details, see &lt;a href=&#34;../../../en/admin/db-users-and-privileges/db-privileges/db-object-privileges/#crypto&#34;&gt;Database Object Privileges&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id=&#34;cryptographic-keys-and-certificates&#34;&gt;Cryptographic keys and certificates&lt;/h3&gt;
&lt;p&gt;You can now &lt;a href=&#34;../../../en/sql-reference/statements/grant-statements/grant-key/&#34;&gt;grant&lt;/a&gt;/&lt;a href=&#34;../../../en/sql-reference/statements/revoke-statements/revoke-key/&#34;&gt;revoke&lt;/a&gt; USAGE, DROP, and ALTER privileges on cryptographic keys.&lt;/p&gt;
&lt;p&gt;You cannot explicitly grant privileges on certificates; rather, privileges on certificates comes from ownership or privileges on the underlying cryptographic key. For details, see &lt;a href=&#34;../../../en/sql-reference/statements/grant-statements/grant-key/&#34;&gt;GRANT (key)&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id=&#34;tls-configurations&#34;&gt;TLS configurations&lt;/h3&gt;
&lt;p&gt;You can now &lt;a href=&#34;../../../en/sql-reference/statements/grant-statements/grant-tls-config/&#34;&gt;grant&lt;/a&gt;/&lt;a href=&#34;../../../en/sql-reference/statements/revoke-statements/revoke-tls-config/&#34;&gt;revoke&lt;/a&gt; DROP and USAGE privileges on TLS Configurations.&lt;/p&gt;

      </description>
    </item>
    
  </channel>
</rss>
