Setting advanced connection properties
The tables below describe the settings in the Advanced tab.
| Setting | Description |
|---|---|
|
Select one of the following target storage formats: Text (the default), or Sequence. Information note
Creating and storing the tables in text format (the default) allows data to be appended to them. This in turn reduces the number of files created on CDP Private Cloud, improves query performance, and reduces the number of Hive jobs running. Information note
When using Text as the target storage format, new lines as part of the data values are not supported (due to an Apache Hadoop limitation). Best practice is to use Sequence as the target storage format. Information note
When Sequence format is selected, the data is loaded directly to the target and stored in an external table (in sequence format). Note also that data cannot be appended in Sequence format. |
|
|
Field delimiter |
The delimiter that will be used to separate fields in the target file. The default is |
|
Null value |
The value that will be used to indicate a null value in the target file. Example (where @ is the null value): mike,male,295678 sara,female,@ |
|
Escape character |
The escape character is used to escape the field delimiter character. When a field delimiter is escaped, it is interpreted as actual data, and not as a field delimiter. Example (where \ is the escape character and a comma is the field delimiter): sunroof\,power-steering |
|
Add metadata header |
When the target storage format is set to Text, you can optionally add a header row to the data files. The header row can contain the source column names and/or the intermediate (i.e. Replicate) data types. Example of a target file with a header row when both With column names and With data types are selected: Position:DECIMAL(38,0),Color:VARCHAR(10) 1,"BLUE" 2,"BROWN" 3,"RED" ... |
| Setting | Description |
|---|---|
| Apply/store changes when file size reaches | Specify the minimum size of the data required to apply/store the changes. |
| Apply/store changes when elapsed time reaches |
Specify the maximum time to wait before applying/storing the changes. |
- Changes will be applied when the Applied Changes replication option is enabled and/or stored when the Store Changes replication option is enabled.
- To facilitate rapid delivery of DDL messages, files are uploaded immediately, regardless of the specified File size reaches or Elapsed time reaches values.
Preventing ODBC connection timeouts
The default query timeout value is 600 seconds, which should be sufficient for most situations. However, when loading very large tables, you may need to increase the value to prevent timeouts. This can be done using the following internal parameter:
executeTimeout
See below for instructions on setting internal parameters.
Internal parameters
Internal parameters are parameters that are not exposed in the UI. You should only use them if instructed by Qlik Support.
To add internal Qlik Replicate parameters:
-
Click the Internal Parameters link.
The Internal Parameters dialog box opens.
- In the edit box, type the name of the parameter you need to add and then click it.
- The parameter is added to the table below the search box with its default value.
- Change the default value as required.
- To reset the parameter value to its default, click the "Restore default value" icon at the end of the row.
More options
These options are not exposed in the UI as they are only relevant to specific versions or environments. Consequently, do not set these options unless explicitly instructed to do so by Qlik Support or product documentation.
To set an option, simply copy the option into the Add feature name field and click Add. Then set the value or enable the option according to the instructions you received.
Settings summary
You can view a summary of your settings by clicking the Setting Summary link. This is useful if you need to send a summary of your settings to Qlik Support.