LucidDbSessionParameters

From Eigenpedia

Jump to: navigation, search

Overview

This page lists the parameters which can be set via the ALTER SESSION command. To retrieve current settings, use a system view query:

select * from sys_root.user_session_parameters;

Parameter List

Name Datatype Default Value Description
logDir VARCHAR(1024) SERVER_INSTALL_ROOT/log The logical root directory in which to store all error log files.
etlProcessId VARCHAR(1024) null An identifier for an ETL process instance. If not specified, it defaults to system-generated session ID. (ex: '14602').
etlActionId VARCHAR(1024) null An identifier for an action within an ETL process. This defaults to system-generated statement ID. (ex: 'LoadAccount').
errorMax BIGINT 0 The number of errors to allow before a statement fails. 0 means allow no errors. See LucidDbErrorHandling for more information.
errorLogMax BIGINT null The maximum number of errors to log for a statement. 0 means to log no errors; null means to log all errors.
label VARCHAR(1024) null An identifier indicating the name of the label that will be used by the current session. A setting of null indicates that the session will run with no label setting. See LucidDbWarehouseLabels for more information.
lastUpsertRowsInserted BIGINT null The number of rows inserted by the last MERGE statement executed by this session, or null if no MERGE statement has been executed. This parameters is set by the system as part of executing a MERGE, so it is usually queried rather than changed by users.
lastRowsRejected BIGINT null The number of rows rejected by the last INSERT, MERGE or DELETE statement executed by this session, or null if no such statement has been executed. This parameters is set by the system as part of executing a statement, so it is usually queried rather than changed by users.
squeezeJdbcNumeric BOOLEAN true Whether to replace unsupportable numerics, loaded through JDBC, with NULL. For example, an Oracle decimal value 9.99E100 is replaced with NULL when loaded into LucidDB as a DECIMAL(19,0). In contrast, an Oracle DECIMAL(5) that overflows when loaded into a LucidDB DECIMAL(3) will always be recorded as an error.
validateDdlOnPrepare BOOLEAN false Whether DDL statements should be validated at both prepare and execute (true), or only on execution (false, the default as of release 0.7.4).
reduceNonCorrelatedSubqueries BOOLEAN true Whether to reduce non-correlated subqueries to constants during query optimization. Introduced in release 0.7.4.