# Properties file Input
## 
Read data (key, value) from properties files
### Description
The Property Input transform reads key/values pairs from a Java properties files.
{% hint style="info" %}
Tip: More information on this file format is available on [Wikipedia](https://en.wikipedia.org/wiki/.properties).
{% endhint %}
| Hop Engine | ✓ |
| ---------- | ------------ |
| Spark | ? |
| Flink | ? |
| Dataflow | ? |
### Options
#### Files Tab
| Option | Description |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
| Transform name | Name of the transform. This name has to be unique in a single pipeline. |
| Filename is defined in a field? | The file name to read is available in a field in the input stream. |
| Get filename from field | Specify the field to read the file name from. |
| File or directory | Specifies the location and/or name of the input text file. |
| Add | Click to add the file/directory/wildcard combination to the list of selected files (grid) below. |
| | Browse |
| Click to select the file to load from a file browser. | Regular expression |
| Specifies the regular expression you want to use to select the files in the directory specified in the previous option. | Exclude Regular |
| Specifies a regular expression to exclude files from the specified directory. | Selected Files |
| Contains a list of selected files (or wildcard selections) and a property specifying if that file is required or not. If a file is required and it is not found, an error is generated, otherwise, the file name is skipped. | Delete |
| Click to remove the selected file or wildcard selection from the list. | Edit |
| Click to modify the selected file or wildcard. | Show filenames(s)… |
#### Content Tab
| Option | Description |
| ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| File Type | The file’s type. This should be "Properties file". |
| Encoding | The character encoding used for the file. |
| Section | If necessary, specify the section of the file to read. |
| Limit | Specify the maximum number of rows read from the file, or specify 0 for no limit. |
| Substitute variable for value | If the file was provided in a variable, resolve that variable to get the file name. |
| Include filename in output? | Allows you to specify a field name to include the file name in the output of this transform. |
| Rownum in output | Allows you to specify a field name to include the row number (Integer) in the output of this transform. |
| Reset rownum per file? | Enable to reset the generated row number to 1 at the start of every individual file. Otherwise, the rownum counts all rows in all files. |
| Include section name in output? | Allows you specify a field name to include the section namemin the output of this transform. |
| Add filename to result? | Adds the names of the files read to the result of this pipeline. A unique list is kept in memory that can be used in the next workflow action in a workflow, for example in another pipeline. |
#### Fields Tab
| Option | Description |
| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Name | The name of the output field |
| Column | The attribute to read |
| Type | The data type for the field. This might require conversion if the source file does not use the same type. The following options all apply to the result after conversion. |
| Format | The format or conversion mask to use in the data type conversion |
| Length | The maximum number of characters for the output data type, or -1 for no limit. |
| Precision | The number of decimal places used for displaying floating-point numbers. |
| Currency | The currency symbol to display for monetary value. |
| Decimal | The decimal point symbol to use for numbers. Typically "." (10.5) or "," (10,5). |
| Group | The thousands separator symbol to use for numbers. Typically "," (5,200,820) or "." (5.200.820). |
| Trim type | The trimming method used to remove blank spaces from string values. This can be left (removes leading spaces), right (removes trailing spaces), both, or none. |
| Repeat | Repeat the column value of the previous row if the column value is empty (null) |
#### Additional output fields Tab
| Option | Description |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| Short filename field | The field used to contain the filename, without the path. |
| Extension field | The field used to contain the file extension. |
| Path field | The field used to contain the file’s path. |
| Size field | The field used to contain the file size. |
| Is hidden field | The field used to contain whether the file is hidden. |
| Last modification field | The field used to contain the date the file was last modified. |
| Uri field | The field used to contain the full source URL for the file. This could be an http\:// or file:// URL depending on the file’s source. |
| Root uri field | The field used to contain the root of the source URL for the file, including the protocol and top-level address. |
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.primeur.com/data-shaper-1.21/knowing-the-data-shaper-designer/pipelines/transforms/propertyinput.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.