> ## Documentation Index
> Fetch the complete documentation index at: https://docs.activeviam.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Parser overrides

> How to use `ParserOverridesDescription` to override the DLC's default CSV column parser type per store field, instead of relying on implicit column-to-field name matching.

Overrides are keyed by store field name and specify the parser type to use for that field.

Parser Overrides currently only work with CSV files.
This is a global configuration which will affect which CsvColumnParser's are added to the channel.

The DLC will implicitly try to match input columns to datastore table fields with the same name.
The data type of the table field is implicitly used for the parser type.

For more granular control of the parsers for a CSV topic, the `CsvColumnParser` column calculator can be explicitly added to the channel as a [Custom Field](/configuration/custom-field).

### Java configuration

`ParserOverridesDescription` Spring Beans are picked up as configurations for the DLC.

#### Example

```java theme={"languages":{"custom":["/engine/python-sdk/0.9/languages/pycon.tmLanguage.json"]}}
@Bean
ParserOverridesDescription columnParsingOverrides() {
    return ParserOverridesDescription.builder()
            .parserOverride(StoreFieldNames.MATURITY, STRING)
            .parserOverride(StoreFieldNames.SCENARIO_IDS, INT_ARRAY)
            .parserOverride(StoreFieldNames.PROFIT_AND_LOSS, DOUBLE_ARRAY)
            .parserOverride(StoreFieldNames.PV, DOUBLE_ARRAY)
            .parserOverride(StoreFieldNames.SENSITIVITY, DOUBLE_ARRAY)
            .build();
}
```