If the script finds projection buddies with different SELECT and ORDER BY clauses, it generates a deploy script. The script identifies and lists any unsupported projections. Vertica has provided a pre-upgrade script that examines your current database and sends to standard output its analysis and recommendations. You must then revert to the previous installation. If the upgrade encounters these projections, it is liable to fail. If a table's only superprojection is one of these projection types, the projection is regarded as unsafe.Before upgrading to 9.2 or higher, you are strongly urged to check your database for unsupported projections. With version 9.2, Vertica has removed support for pre-join and range segmentation projections. Identify and Remove Unsupported Projections If you were unaware of this limitation and currently have more than 1 TB of ROS data in your database, before upgrading to Vertica 10.1 or higher please make the necessary adjustments to stay below the 1 TB limit, or contact our sales team to explore other licensing options. Starting with Vertica 10.1, if you are using Vertica for SQL on Hadoop, you cannot load more than 1 TB of ROS data into your Vertica database. Includes 1 TB of Vertica ROS formatted data on HDFS. Vertica for SQL on Hadoop is for deployment on Hadoop nodes. Vertica for SQL on Hadoop is licensed per node, on an unlimited number of central processing units or CPUs and an unlimited number of users.
0 Comments
Leave a Reply. |