Dialect properties for DSV objects
This table shows the dialect properties that are supported for DSV objects:
| Dialect property | Type | Description |
|---|---|---|
separator |
string | Required. The delimiter character that separates the values in a row of data. The value of the separator is defined in this way for different delimited file types:
Other separator values are allowed, but they must be single-character separators. For example, double pipes ( |
skipLines |
integer | Optional. Indicates the number of header rows to skip over at the top of the file before reaching the actual data.
Note: For Compass (Data Lake Services) only, DSV data objects are required to have a single header line that contains column names. skipLines is always assumed to be 1.
|
headerLine |
integer | Optional. Indicates the line number that contains column headers for a data object. This value must be less than or equal to the value of skipLines.
Note: For Compass (Data Lake Services) only, DSV data objects are required to have a single header line that contains column names. headerLine is always assumed to be 1.
|
enclosingCharacter |
string | Optional. The character that identifies the start and end of a value. If two consecutive enclosing characters are found in a data object, they are interpreted as one. Therefore, escaping the enclosing character. |
The line separator is not specified in metadata.
These characters are regarded as the end of a line unless they are placed within enclosing characters:
- A carriage return
- A line feed
- The combination of carriage return and line feed
The last line may or may not have a line separator.
The encoding is not specified in metadata and is always assumed to be UTF-8.