Professional Documents
Culture Documents
HP Vertica 7.1.x New Features
HP Vertica 7.1.x New Features
Legal Notices
Warranty
The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be
construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
The information contained herein is subject to change without notice.
Copyright Notice
Copyright 2006 - 2015 Hewlett-Packard Development Company, L.P.
Trademark Notices
Adobe is a trademark of Adobe Systems Incorporated.
Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.
UNIX is a registered trademark of The Open Group.
Page 2 of 61
Contents
Contents
10
10
10
10
11
11
12
12
12
Licensing Changes
13
Documentation Updates
13
14
14
15
15
16
Page 3 of 61
16
16
16
17
New Options
17
17
17
18
18
18
19
19
19
20
21
Security Model
21
22
23
24
25
SSL Changes
25
New Parameters Hold the Contents of Your SSL Certificate and Key Files
Setting the New SSL Parameters
25
26
27
27
28
SDK Enhancements
29
Page 4 of 61
29
29
29
30
31
32
Data Management
32
32
32
33
34
34
34
Management API
35
36
37
37
Access Policy
38
System Tables
39
39
New in V_CATALOGSchema
39
Management Console
40
41
41
41
42
42
Page 5 of 61
43
43
43
43
43
45
How ROLLUPWorks
45
ROLLUPGrouping Functions
45
46
46
Performance
47
47
47
48
48
48
48
49
Text Search
49
Scrutinize
49
50
Python 3 Support
50
50
HP Vertica Place
51
HP Vertica Pulse
51
Documentation Updates
Programmer's Guide Separated Into Individual Guides
53
53
Page 6 of 61
53
53
54
Retired Functionality
55
61
Page 7 of 61
Page 8 of 61
other users' sessions. Each user can have one dictionary of each type loaded at any given time. If a
user does not specify a dictionary of a given type, Pulse uses the default dictionary for that type.
GetAllDictionarySetLabels()
GetAllLoadedDictionaries()
UnloadLabeledDictionary()
UnloadLabeledDictionarySet()
UnloadLabeledMapping()
Page 9 of 61
Download the latest HP Vertica Connectivity Pack for Microsoft from my.vertica.com (logon
required).
ANALYZE_EXTERNAL_ROW_COUNT
DROP_EXTERNAL_ROW_COUNT
start_point_occurrence
key_separator
suppress_nonalphanumeric_key_chars
For a description of these parameters, see the Flex Tables Guide, FJSONPARSER. Using the new
parameters is presented in Loading JSONData.
Page 10 of 61
When loading delimited data, the fdelimitedparser (or mapdelimitedextractor function) now
includes a NULL for any row with an empty value, rather than an empty string (''). To continue using
empty strings when loading delimited data keys without a value, as in previous releases, specify
treat_empty_val_as_null=false.
See FDELIMITEDPARSER and MAPDELIMITEDEXTRACTOR in the Flex Tables Guide.
The new CUBE aggregation performs the aggregation for all permutations of CUBE
expressions.
The new GROUPING SETS aggregation allows you to specify exactly which groupings of
aggregations you need.
You can now use multiple ROLLUP, CUBE, or GROUPING SETSaggregations in a single
GROUPBYclause.
For a description of how these aggregations integrate with multi-level aggregations, see
Aggregating GROUP BY Results.
Kerberos integration for Hadoop. See Using Kerberos-Enabled Hadoop. This has been tested
with Hortonworks (HDP 2.2), Cloudera (CDH5.2 and 4.7) and MapR (4.0.1).
Direct reading of ORC files, a native Hadoop format, for improved efficiency. See Reading ORC
Files Directly.
Sharing of HCatalog configuration information. The hcatUtil script now copies HCatalog
configuration parameters from Hadoop so they do not need to be explicitly specified to
CREATEHCATALOGSCHEMA. See Configuring HP Vertica for HCatalog.
This release also adds improvements to the management of storage locations. Changes can now
be enforced immediately instead of waiting for the next automatic update, which simplifies the
process of retiring a storage location. Storage-location operations can also now be applied to all
Page 11 of 61
nodes with a single command. See Managing Storage Locations and the corresponding metafunctions in the SQL Reference Manual.
Connect to an Apache Ambari server through the Connect using an Ambari server to import
Vertica within a Hadoop environment button under the Provision section of Management
Console.
Monitor and update your Hadoop environment from the Management Console Existing
Infrastructure page.
For detailed instructions, see Using MC to Import and Monitor Vertica in a Hadoop Environment.
Page 12 of 61
Anything database-related beyond that scope depends on the mapped database user's privileges
granted on the database through GRANT statements.
The Associate role allows full privileges to monitor activity and messages on databases managed
by MC. Associate users may have other database privileges, depending on the database user
account to which they are mapped. These privileges can include modifying settings, installing
licenses, and viewing the database designer.
See About MC Users and About MC Privileges and Roles.
Licensing Changes
HP Vertica no longer counts each delimiter character as a 1-byte value against your license data
limit. Runnning a license audit after upgrading results in less total data than the previous version.
Documentation Updates
Documentation on partially sorted GROUPBY was erroneously included in the documentation and
has been removed. This functionality is currently not included in the product.
Page 13 of 61
All client authentication records are stored in the same location using a consistent format.
Any changes to client authentication when a node goes down are automatically recovered when
the node restarts.
Grant and revoke authentication methods for individual users or for user roles.
Assign a default authentication method. A user who has not been granted an authentication
method is authenticated with the default method.
Temporarily grant or revoke authentication methods for specific users and user roles or for all
users and user roles.
Page 14 of 61
\\
Page 15 of 61
Vertica backup or restore actions fail with an error message. If you do not save any passwords,
running vbr.py still creates the password file, but leaves the file empty.
Page 16 of 61
This option provides the same functionality currently available through the Administration Tools
interface.
New Options
The following options are new to the scrutinize diagnostics tool:
--diag-dump
Collects HP Vertica queries, system tables, and Data Collector tables. This
option replicates the behavior of the superseded collect_diag_dump tool.
--diagnostics
Collects log file data and runs commands against HP Vertica and its host
system. This option replicates the behavior of the superseded diagnostics
utility.
--log-limit limit
Limits how much data is collected from HP Vertica logs, where limit
specifies in gigabytes how much log data to collect, starting from the most
recent log entry.
--tmpdir=path
Specifies a temporary directory to use on all nodes. Use this option to ensure
that the temporary directory has enough free space so scrutinize can
complete execution.
Collects cluster hardware configuration from systems where the lshw utilty is installed.
Page 17 of 61
Page 18 of 61
When you create a live aggregate projection, you can no longer delete, update, or merge data in
the anchor table or the anchor projection. You can only add data to them.
Page 19 of 61
Top-K Projections
For optimal performance of Top-K queries, create a Top-Kprojection that aggregates the data in the
table for fast access. Querying the preaggregated data directly from the Top-K projection is usually
faster than querying the data from the anchor table and then calculating the top k rows.
When you create a Top-K projection, keep in mind:
l
After you create a Top-K projection for a table, you can no longer delete, update, or merge data in
the anchor table or anchor projection. You can only add data to them.
Top-K Projections
Page 20 of 61
Security Model
HP Vertica 7.1 introduces these security features:
l
SSL Changes
Page 21 of 61
Note: For details about GSS-API implementation, see RFC2744 and RFC4121.
Hash authentication is new; it replaces MD5 authentication. It allows you to store passwords
using the MD5 algorithm and the more secure SHA-512 algorithm. You configure the hash
authentication and then define user-level and system-level parameters to specify which
algorithm to use.
Use an SSL client certificate whose Common Name (CN) field contains the user name for the
target database.
Create an authentication method that uses an auth_type of tls with the authentication
method HOST TLS.
For information, see Configuring TLSAuthentication.
There are several new parameters for configuring LDAP. For details, see LDAPParameters.
Password. Password authentication sends passwords over the network in clear text. HP
Vertica recommends that you use hash authentication with the SHA512 algorithm.
Ident. The Ident protocol authenticates a database user with their system user name.
Page 22 of 61
Trust. When you grant trust authentication to a user, they can always log in without a password.
Reject. When you grant reject authentication to a user, they can never log in.
All client authentication records are stored in the same location using a consistent format.
Any changes to client authentication when a node goes down are automatically recovered when
the node restarts.
Grant and revoke authentication methods for individual users or for user roles.
Assign a default authentication method. A user who has not been granted an authentication
method is authenticated with the default method.
Temporarily grant or revoke authentication methods for specific users and user roles or for all
users and user roles.
Page 23 of 61
At the system level, set the SecurityAlgorithm configuration parameter. Valid values are:
n
'NONE'
'MD5'
'SHA512'
This setting applies to all users, unless the DBADMINhas set the user-level parameter to 'MD5'
or 'SHA512'. In that case, the user-level value overrides the system-level value.
l
At the user level, use ALTER USERto set the Security_Algorithm user parameter. Valid values
are the same as for the system-level parameter:
n
'NONE'
'MD5'
'SHA512'
If the value of the user-level parameter Security_Algorithm is 'NONE', HP Vertica uses the
algorithm specified in the system-level parameter, SecurityAlgorithm. If both parameters are
'NONE', HP Vertica uses the MD5 algorithm.
Important: Before you upgrade, read about the issues you might encounter in Upgrade
Considerations for Hash Authentication.
See Also
l
Page 24 of 61
You use the new ALTERAUTHENTICATIONstatement to set and change LDAPand Ident
parameters.The following examples set parameters using key/value pairs:
=> ALTER AUTHENTICATION ident1 SET system_users='root';
=> ALTER AUTHENTICATION Ldap1 SET host='ldap://172.16.65.177',
binddn_prefix='cn=', binddn_suffix=',dc=qa_domain,dc=com';
ALTERAUTHENTICATION
Configuring LDAPAuthentication
SSL Changes
HP Vertica 7.1.0 introduces these changes to SSL:
l
SSLPrivateKeySet this parameter to the contents of your servers private key (server.key)
file. Note that only the value of this parameter is visible to dbadmin users.
Page 25 of 61
file.
l
SSLCASet this parameter to the contents of SSL certificate authority (root.crt) file if using
mutual authentication.
These new parameters simplify distribution of your server certificate file (server.crt) and private
key (server.key) to server hosts in your cluster. BeforeHP Vertica7.1, the server certificate and
private key had to be copied to the HP Vertica catalog directory of each server host in your cluster.
Note: The SSLPrivateKey and SSLCertificate parameters are automatically set during the 7.1
upgrade, if EnableSSL=1 before the upgrade.
For a listing and description of these new configuration parameters and all other security
parameters, refer to the Administrator's Guide, Security Parameters.
Common Questions
The following table provides answers to common questions on setting the new parameters.
Page 26 of 61
Question
Response
key files so that the parameters are set for the upgrade.
parameters.
Page 27 of 61
For Windows ODBC, HP Vertica 7.1 also adds connection string properties within the ODBC Data
Source Administrator GUI, including SSL cert file and SSL key file fields under the Client Setting
tab.
Page 28 of 61
For more information about configuration parameters, see Configuration Parameters in the
Administrator's Guide.
SDK Enhancements
HPVertica 7.1.0 introduces these SDK Enhancement features:
l
Manually copy the library to every node in your cluster to a location where the UDx could find it.
For example, copy a Java library to each node in your cluster. Then you update each node's
CLASSPATH to include the library's directory.
In HP Vertica Version 7.1.x, you can specify one or more directories containing support library files
using the the new DEPENDSkeyword in the CREATELIBRARYstatement. HP Vertica handles
these support libraries the same way it treats the UDx library itself. It copies the libraries to each
Page 29 of 61
node in the cluster in a location where the UDx library can access them. For Java UDx libraries,
you can use this new feature as a way to set a Java classpath for each UDx library.
For more information, see Handling Java UDx Dependencies, Compiling Your C++ UDx, and
CREATE LIBRARY.
New functions to extract semi-structured data from the database directly into a Vmap, without
first having to write such data to disk and load it with COPY and the flex parsers
MAPDELIMITEDEXTRACTOR
MAPJSONEXTRACTOR
MAPREGEXEXTRACTOR
Each function processes a specific type of data, using identical arguments to the corresponding
flex table parser (FDELIMITEDPARSER, FJSONPARSER, and FREGEXPARSER). Use the
extractor functions to extract semi-structured data from database contents (such as an existing
table column or data returned from an expression), or entered directly as a string. The function
returns a single VMAProw that you can use in a flex or regular table column.
For more information, see the the Flex ExtractorFunctions Reference in the Flex Tables Guide.
Page 30 of 61
start_point
reject_on_empty_key
omit_empty_keys
reject_on_materialized_type_error
reject_on_empty_key
omit_empty_key
reject_on_materialized_type_error
BUILD_FLEXTABLE_VIEW
COMPUTE_FLEXTABLE_KEYS_AND_BUILD_VIEW
MATERIALIZE_FLEXTABLE_COLUMNS
Page 31 of 61
Data Management
HPVertica 7.1.0 introduces these Data Management features:
l
COPYStatement Changes
Apportioned load support. The COPYstatement already supported multi-threaded bulk loading
on a single node (parallel load). Now, load also occurs across multiple nodes to increase
performance.
LZO format support. COPYnow accepts LZO files, as it does other formats, such as BZIP and
GZIP files. For more information, see COPY in the SQL Reference Manual.
Page 32 of 61
DC_DESIGN_PROJECTION_CANDIDATES
DC_DESIGN_QUERY_PROJECTION_CANDIDATES
When you enable logging and start Database Designer, the Optimizer proposes a set of ideal
projections based on the options that you specify. The logs contain information about:
l
Whether or not the projections are actually created when the design is deployed.
Whether the projections are created with and without the ideal criteria that the Optimizer
identified.
If you do not deploy the design immediately, review the logs to determine if you want to change the
design and proposed projections. If Database Designer deployed the design, you can still manually
create some of the projections that Database Designer did not create in the deployed design.
By default, logging the Database Designer design data is disabled. To enable it, turn on the
configuration parameter DBDLogInternalDesignProcess:
=> ALTER DATABASE exampledb SET DBDLogInternalDesignProcess = '1';
Column definitions
Segmentation
Partitioning expression
Number of projections
Page 33 of 61
Swapping partitions is an atomic operation. The swapping operation moves the data to a new
partition and then swaps the newly partition with the partition in the target table while maintaining
the integrity of the data. If any task in the swap operation fails, the entire operation fails.
For more information, see:
l
Swapping Partitions
SWAP_PARTITIONS_BETWEEN_TABLES
Management API
Page 34 of 61
same fault group as the failed node. Otherwise, HP Vertica randomly selects an available active
standby node.
If you are an administrator, you can manually replace a failed node using the ALTER NODE
command. You can specify a particular standby node to replace a failed node, or you can allow HP
Vertica to choose a node. As with automatic node replacement, HP Vertica defaults to a standby
node from the same fault group as the failed node. If the fault group has no available standby nodes,
HP Vertica selects any available active standby node.
Management API
HP Vertica 7.1 introduces the Management API. The Management API is a REST API that can be
used to manage HP Vertica databases with scripts or applications that understand REST and
JSON.
The Management API provides a subset of the database administration tools found in the
Management Console. Features include the ability to:
l
View details about available database backups, start a new database backup, and restore
backups from specific archives
Add hosts to the database, remove hosts from the database, and replace hosts with standby
hosts
Page 35 of 61
database_valuevalue set at the database level. Shows default value if no value is set at the
database level.
Page 36 of 61
groupsdisplays the group(s) to which the parameter belongs (e.g. security parameter).
CASCADE TO Parameter
With the new CREATE RESOURCE POOl and ALTER RESOURCE POOL CASCADE TO parameter, you can
indicate a secondary resource pool to which queries can cascade. When a query reaches the initial
pool's RUNTIMECAP, the query cascades to your defined secondary pool where it executes.
PRIORITY HOLDOption
The new HOLD value option for the PRIORITY parameter sets a pool's priority to -999 so queries in
that pool queue until QUEUETIMEOUTis reached. You can set PRIORITY HOLD on a secondary pool if
you want a query that exceeds the initial pool's RUNTIMECAP to abort and stay on hold until a later
time.
For more information, see the RESOURCE_POOLS system table in the SQL Reference Manual
and Defining Secondary Resource Pools in the Administration Guide.
Page 37 of 61
SSLCLAYou set the SSL certificate authority by providing the contents of the certificate
authority root.crt file. For more information, see Security Parameters.
SSLCertificateYou set the SSL certificate by providing the contents of the server.crt file.
For more information, see Security Parameters.
SSLPrivateKeyYou set the server's private key by providing the contents of the server.key
file. Note that only the value of this parameter is visible to dbadmin users. For more information,
see Security Parameters.
SecurityAlgorithmUse this parameter to set the algorithm for the function that hash
authentication uses:MD5 or SHA512 .
Access Policy
With HPVertica you can now control access to data in a table at the column level. The new access
policy feature provides the capability to control user access at the table column level adding a
further level of security. Implementing this capability across your HP Vertica database can prevent
unauthorized users from retrieving sensitive information.
Implementing secure access to your HP Vertica table columns is achieved by creating user, roles,
and privileges. Once such required privileges exist, you choose which entities to associate with
table columns. Only user and roles granted relevant access can view and operate on data that the
column contains.
For more information see the following in the Administrator's Guide:
Page 38 of 61
See Also
SQLFor New Access Policy
System Tables
This section lists the new and modified system tables in this release. See the SQL Reference
Manual for details.
Modified in V_MONITORSchema
TheLOGIN_FAILUREStable has one new column:
l
CLIENT_AUTHENTICATION_NAME
CLIENT_AUTHENTICATION_NAME
CLIENT_AUTHENTICATION
JVM_MEMORY_KB
New in V_CATALOGSchema
The following system tables were added in this release:
Page 39 of 61
CLIENT_AUTH
CLIENT_AUTH_PARAMS
PASSWORD_AUDITOR
USER_CLIENT_AUTH
Modified in V_CATALOGSchema
The LICENSE_AUDITS system table has one new column:
l
LICENSE_NAME.
IS_EXPRESSION
IS_AGGREGATE
COLUMN_EXPRESSION
SEGMENT_EXPRESSION
HAS_EXPRESSIONS
IS_AGGREGATE
AGGREGATE_TYPE
HAS_AGGREGATE_PROJECTION
Management Console
This section lists the new functionality HP Vertica Analytics Platform introduced to Management
Console.
Page 40 of 61
Page 41 of 61
Average query queue time and execution time per pool across all nodes.
Total number of resource requests that were rejected on a specified pool across all nodes.
From the MC Configuration page, you can now change certain pool parameters.
The option to turn on column correlation detection for a design appears in the General tab, or in
the Options screen when using the Database Designer Wizard.
Page 42 of 61
When selecting queries to include in a design, the queries view in the Queries tab can be sorted
by most recent, most frequent, and longest running.
Icons now indicate the optimization status of design queries (optimized, partially optimized, or
unoptimized) in the Queries tab.
For more information about Database Designer in Management Console, see Using Management
Console to Create a Design in the Administrator's Guide.
Page 43 of 61
When to Rebalance
Rebalancing is useful (or necessary) after you:
l
Mark one or more nodes as ephemeral in preparation of removing them from the cluster
Add one or more nodes to the cluster so that HP Vertica can populate the empty nodes with data
Change the scaling factor of an elastic cluster, which determines the number of storage
containers used to store a projection across the database
Set the control node size or realign control nodes on a large cluster layout
Syntax
REBALANCE_TABLE('schema.table_name')
Parameters
[schema]
[Optional] Specifies the name of the schema that contains the table that you want to
rebalance. If you do not specify a schema-name, the statement checks for matching
tables in the first schema listed in the current search_path.
table_name
Privileges
Must be a superuser.
Example
The following command shows how to rebalance data on the specified table.
Page 44 of 61
How ROLLUPWorks
ROLLUP performs aggregate operations on multiple levels in a hierarchy, creating sub-totals. HP
Vertica7.1 then aggregates (or rolls up) these subtotals from the most detailed level to a grand total.
ROLLUP requires an ordered list of grouping expressions used as arguments.
To aggregate data, ROLLUP performs these operations:
l
Creates progressively higher-level subtotals by moving from right to left through the grouping
columns, starting with the lowest level.
Continues this process until all the grouping columns have been incorporated and aggregations
computed. It then reports a grand total.
Using ROLLUP equates to using a UNIONALL with a set of GROUPBYqueries. With ROLLUP,
you specify only the required groupings in the GROUPBYclause. This approach allows more
efficient analysis and improved database performance.
ROLLUPGrouping Functions
ROLLUP supports the following grouping functions:
l
GROUPING()
GROUPING_ID()
GROUP_ID()
Page 45 of 61
These grouping functions identify the group to which each row belongs and enable sorting subtotal
rows and filtering results .
See Also
l
GROUP BY Clause
GROUPING()
GROUP_ID ()
GROUPING_ID ()
ALTER ACCESS POLICY - specify actions that can be performed on an access policy.
Page 46 of 61
Performance
In this release, HP Vertica introduces numerous infrastructure improvements to increase
performance across the entire platform.
Page 47 of 61
The connector now determines if the file it is retrieving from HDFSis split across Hadoop nodes.
If it is split, then the connector connects to the Hadoop nodes storing each piece of the file and
retrieves and reassembles the pieces itself. Previously, the Hadoop nodes would reassemble
the file before sending it to the connector. Having the connector directly access the pieces and
reassemble the file removes the delay caused by having the file's contents transferred between
nodes in the Hadoop cluster before being sent to HP Vertica.
Page 48 of 61
When the connecter encounters an error while retrieving data from HDFS, it now automatically
retries the request. Previously, errors would often result in the query failing.
The connector now monitors the data transfer speed from the Hadoop cluster. If any connection
slows below a threshold (1 MB per second by default), the connector breaks it and tries to
retrieve the data from another node in the cluster. You can manually set the lowest allowable
data transfer rate. See Connector for HDFS Troubleshooting Tips for more information.
Text Search
HP Vertica 7.1 introduces functionality to allow you to perform a text search on a field within a table.
The text search feature allows you to quickly search the contents of a single CHAR, VARCHAR or
LONGVARCHAR field within a table to locate a specific keyword. This feature is best used on
columns that will be repeatedly queried regarding their contents. After the text index is created,
DML operations will be slightly slower on the source table. This is a result of syncing the text index
and source table. Regular queries on the source table will not be affected.
This functionality includes the addition of two new SQL statements, CREATE TEXT INDEX and
DROP TEXT INDEX.
For more information and a detailed example, see Text Search Overview.
Scrutinize
The Scrutinize command will now accept more options to provide users with a custom diagnostic
report to best suit their needs.
The new options are:
l
--version
--no-containers
--no-active-queries
--with-active-queries
Page 49 of 61
--begin
--end
Linux
Windows
Macintosh
Solaris
AIX
HP-UX
The Connecting to HP Vertica Guide contains details for configuring clients to connect to an IPv6
interface on an HP Vertica server.
Python 3 Support
HP Vertica 7.1 introduces support for Python 3 and newer versions of PyODBC. The specific
versions supported are detailed in the Supported Platforms guide. See Perl and Python
Requirements.
Page 50 of 61
HP Vertica Place
HP Vertica 7.1 includes HP Vertica Place, an analytics package that provides users with the ability
to manipulate geospatial data. With 7.1.x, HP Vertica Place is now generally available. Previously,
HP Vertica Place was only available as part of the HP Vertica Innovations program.
You can download HP Vertica Place from my.vertica.com/downloads.
HP Vertica Place Features:
l
HP Vertica Place will be available on all supported HP Vertica platforms after 7.1.
HP Vertica Pulse
HP Vertica 7.1 includes support for HP Vertica Pulse. HP Vertica Pulse is an add-on package that
provides a suite of functions that allow you to analyze and extract the sentiment from English
language text directly from your HP Vertica database.
HP Vertica Pulse features include:
l
Attribute based sentiment scoring - Pulse scores the sentiment of attributes in a sentence.
Attributes are generally nouns and are automatically discovered by Pulse. Pulse typically scores
sentiment from a range of -1 (negative sentiment) to +1 (positive sentiment). A sentiment of 0 is
considered neutral. Scoring individual attributes in a sentence instead of scoring the sentence as
a whole provides a more granular analysis for the text. For example, consider the sentence "The
quick brown fox jumped over the lazy dog." It would be difficult to score the sentiment on the
sentence as a whole, but if you score on the attributes of fox and dog, you could say the
sentiment on the fox was positive (the fox is quick), and the sentiment on the dog is negative
(the dog is lazy).
Page 51 of 61
Tuning to your domain - Pulse provides functionality to recognize attributes that are specific
to your domain. For example, you can add the name of your product or company to a 'white_list'
so that it is discovered by Pulse.
Tuning of how sentiment is scored - Pulse includes user-dictionaries of words that are used
to help score sentiment. You can alter these user-dictionaries to fine tune the way your text is
analyzed.
Filtering of attributes you are not interested in - Pulse supports a special 'stop words' userdictionary to indicate attributes that should not be analyzed. Alternately, you can choose to
score sentiment only on attributes defined in your white_list.
Synonym mappings - Pulse provides customizable mappings so that you can map synonyms
to a base word, and then normalize the analysis for the synonyms to the base word. For
example, you can map Hewlett Packard to HP.
HP Vertica Pulse requires that Java and the HP Vertica Java Support Package are installed on all
nodes in the HP Vertica cluster.
Note: The HP Vertica Pulse version must be the same as the version of the HP Vertica server.
For more information, see About the Package.
Page 52 of 61
Documentation Updates
HP Vertica 7.1.x introduces a number of changes to the standard documentation set.
Connecting to HP Vertica explains how to use the vsql client and the HP Verticaclient libraries.
Extending HP Vertica explains how to use SQLmacros and the SDK to add analytic features to
HP Vertica.
Page 53 of 61
The JavaClassPathForUDx configuration parameter. Instead of setting this parameter, you now
set a class path on each UDx library. Set this per-library class path using the new
DEPENDSkeyword of the CREATE LIBRARYand ALTER LIBRARYstatements.
See Also
For information about the meaning of obsolete and deprecated functionality, see Retired
Functionality.
Page 54 of 61
Retired Functionality
This section describes the two phases HP follows to retire HP Vertica functionality.
Deprecated. HP Vertica declares a feature deprecated in a major or minor release. Deprecated
features remain in the product and are functional. However, users accessing the feature receive
messages informing them that the feature will be removed in the following major or minor release.
Features are identified as deprecated in HP Vertica release notes and in feature documentation; all
documentation remains accessible. HP announces feature deprecation only in major and minor
releases.
Removed. HP removes a feature in the major or minor release immediately following the
deprecation announcement. Users can no longer access the functionality. The feature removal is
announced in HP Vertica release notes. All feature documentation is removed.
The following functionality has been deprecated, or removed in past and present versions:
Page 55 of 61
Functionality
Deprecated Removed
Component Version
Version
Server
BB_WITHIN
BEARING
CHORD_TO_ARC
DWITHIN
ECEF_CHORD
ECEF_x
ECEF_y
ECEF_z
ISLEFT
KM2MILES
LAT_WITHIN
LL_WITHIN
LLD_WITHIN
LON_WITHIN
MILES2KM
RADIUS_LON
RADIUS_M
RADIUS_N
RADIUS_R
RADIUS_Ra
RADIUS_Rc
7.1
7.2
Page 56 of 61
Functionality
l
RADIUS_Rv
RADIUS_SI
RAYCROSSING
WGS84_a
WGS84_b
WGS84_e2
WGS84_f
WGS84_if
WGS84_r1
Deprecated Removed
Component Version
Version
Server
7.1
Server
7.1
ADD_LOCATION()
Server
7.1
bwlimit
Server
7.1
Server
7.0
MERGE_PARTITIONS()
Server
7.0
Server,
7.0
clients
krb5 client authentication method
All clients
7.0
Pload Library
Server
7.0
USESINGLETARGET
Server
7.0
Server
6.1
7.1
Page 57 of 61
Functionality
Deprecated Removed
Component Version
Version
IMPLEMENT_TEMP_DESIGN()
Server,
6.1
clients
USER_TRANSFORMSuser table
Server
6.0
UPDATEprivileges on sequences
Server
6.0
Server
6.0
Server
6.0
SYS_DBA.QUERY_REPO table
Functions:
l
CLEAR_QUERY_REPOSITORY()
SAVE_QUERY_REPOSITORY()
Configuration parameters:
l
CleanQueryRepoInterval
QueryRepoMemoryLimit
QueryRepoRetentionTime
QueryRepositoryEnabled
SaveQueryRepoInterval
QueryRepoSchemaName
QueryRepoTableName
Server
6.1
Server
6.0
FUNCTION
Ganglia on Red Hat 4
Page 58 of 61
Functionality
Deprecated Removed
Component Version
Version
copy_vertica_database.sh
Server
restore.sh
Server
backup.sh
Server
Server,
clientsw
4.1 (Client)
5.1 (Server)
5.1
(Client)
MergeOutPolicySizeList
Server
4.1
5.0
EnableStrataBasedMrgOutPolicy
Server
4.1
5.0
ReportParamSuccess
All clients
4.1
5.0
BatchAutoComplete
All clients
4.1
5.0
use35CopyParameters
ODBC,
4.1
5.0
JDBC
clients
getNumAcceptedRows
getNumRejectedRows
ODBC,
5.0
JDBC
clients
Server,
5.0
parameter)
clients
EpochAdvancementMode
Server
4.1
5.0
VT_ tables
Server
4.1
5.0
RefreshHistoryDuration
Server
4.1
5.0
Notes
l
While the HPVertica Geospatial package has been deprecated, it has been replaced by
HPVertica Place. This analytics package is available on my.vertica.com/downloads.
LCOPY: Supported by the 5.1 server to maintain backwards compatibility with the 4.1 client
drivers.
Page 59 of 61
Query Repository: You can still monitor query workloads with the following system tables:
n
QUERY_PROFILES
SESSION_PROFILES
EXECUTION_ENGINE_PROFILES
In addition, HP Vertica Version 6.0 introduced new robust, stable workload-related system table:
l
QUERY_REQUESTS
QUERY_EVENTS
RESOURCE_ACQUISITIONS
Use the Kerberos gss method for client authentication, instead of krb5. See Configuring
Kerberos Authentication.
Page 60 of 61
Page 61 of 61