> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.1/connectors/connector-repositories/file-connectors/nfs-network-file-system.md).

# NFS (Network File System)

This article outlines the integration with the NFS (Network File System) connector, enabling streamlined metadata management through features such as crawling, data preview, and manual lineage building.

The connector establishes connectivity to the NFS file system of the host machine where the application is deployed, providing access to files stored on the instance's local storage. It uses a dedicated service account with the required file system permissions to access metadata from files and folders.

<figure><img src="https://1121831267-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFZv5WsZmBfXjiJfMU2zR%2Fuploads%2Fw5YL8qNWbLFHS8tA30KP%2Fimage.png?alt=media&amp;token=6f7d0bf1-bb1e-4833-9847-9f2d82d684f0" alt=""><figcaption></figcaption></figure>

## Overview

### **Connector** Details

| Connector Category                                                      | File Connectors      |
| ----------------------------------------------------------------------- | -------------------- |
| OvalEdge Release Supported                                              | Release4.0 and later |
| <p>Connectivity</p><p>\[How the connection is established with NFS]</p> | NFS JDK              |

#### Connector Features

| Feature                                      | Availability |
| -------------------------------------------- | :----------: |
| Crawling                                     |       ✅      |
| Delta Crawling                               |       ❌      |
| Profiling\*                                  |       ❌      |
| Sample Profiling                             |       ✅      |
| Data Preview                                 |       ✅      |
| Auto Lineage                                 |       ❌      |
| Manual Lineage                               |       ✅      |
| Secure Authentication via Credential Manager |       ✅      |
| Data Quality\*\*                             |       ✅      |
| DAM (Data Access Management)                 |       ❌      |
| Bridge                                       |       ✅      |

{% hint style="info" %}
\*Full profiling is supported through DuckDB. To enable this capability, configure the system setting (**enable.duckdb**) to **True**. When enabled, the File Data tab displays only the first 100 rows from the source file.
{% endhint %}

{% hint style="info" %}
\*\*Data Quality supports rule execution on supported file formats, including compressed CSV files (.csv.gz).
{% endhint %}

### Metadata Mapping

The following objects are crawled from NFS and mapped to the corresponding UI assets.

<table><thead><tr><th width="131.75">NFS Object</th><th width="161.75">NFS Attribute</th><th width="180.25">OvalEdge Attribute</th><th width="183.5">OvalEdge Category</th><th width="171.75">OvalEdge Type</th></tr></thead><tbody><tr><td>Bucket</td><td>Bucket</td><td>Bucket</td><td>Bucket</td><td>Bucket</td></tr><tr><td>Folder</td><td>Folder</td><td>Folder</td><td>Folder</td><td>Folder</td></tr><tr><td>File</td><td>File</td><td>File</td><td>File</td><td>File</td></tr><tr><td>XLSX</td><td>File</td><td>File</td><td>File</td><td>File</td></tr><tr><td>XLS</td><td>File</td><td>File</td><td>File</td><td>File</td></tr><tr><td>CSV</td><td>File</td><td>File</td><td>File</td><td>File</td></tr><tr><td>TXT</td><td>File</td><td>File</td><td>File</td><td>File</td></tr><tr><td>PARQUET</td><td>File</td><td>File</td><td>File</td><td>File</td></tr><tr><td>ORC</td><td>File</td><td>File</td><td>File</td><td>File</td></tr><tr><td>JSON</td><td>File</td><td>File</td><td>File</td><td>File</td></tr><tr><td>YAML</td><td>File</td><td>File</td><td>File</td><td>File</td></tr><tr><td>PIP</td><td>File</td><td>File</td><td>File</td><td>File</td></tr><tr><td>AVRO</td><td>File</td><td>File</td><td>File</td><td>File</td></tr><tr><td>GIF</td><td>File</td><td>File</td><td>File</td><td>File</td></tr><tr><td>SQL</td><td>File</td><td>File</td><td>File</td><td>File</td></tr><tr><td>XML</td><td>File</td><td>File</td><td>File</td><td>File</td></tr><tr><td>IMAGE</td><td>File</td><td>File</td><td>File</td><td>File</td></tr></tbody></table>

## Set up a Connection

### Prerequisites

The following are the prerequisites to establish a connection.

Ensure that the CSV files follow the required formatting standards for proper data processing and visibility. Refer to [CSV Format Requirements](https://docs.ovaledge.com/connectors/additional-requirements/csv-format-requirements-for-file-connectors)**.**

#### **Service Account User Permissions**

{% hint style="warning" %}
It is recommended to use a dedicated service account to establish the connection to the data source, configured with the following minimum set of permissions.
{% endhint %}

{% hint style="info" %}
**👨‍💻Who can provide these permissions?** These permissions are typically granted by the NFS administrator, as users may not have the required access to assign them independently.
{% endhint %}

<table><thead><tr><th width="233">Operations</th><th width="150">Objects</th><th>Access Permission</th></tr></thead><tbody><tr><td>Connector Validation</td><td>-</td><td>Read</td></tr><tr><td>Crawling &#x26; Profiling</td><td>Folder</td><td>Read and Execute (rx)</td></tr><tr><td>Crawling &#x26; Profiling</td><td>Files</td><td>Read</td></tr></tbody></table>

### Connection Configuration Steps

{% hint style="warning" %}
Users are required to have the Connector Creator role in order to configure a new connection.
{% endhint %}

1. Log into **OvalEdge**, go to **Administration > Connectors**, click **+ (New Connector)**, search for **NFS**, and complete the required parameters.

{% hint style="info" %}
Fields marked with an asterisk (\*) are mandatory for establishing a connection.
{% endhint %}

<table><thead><tr><th width="220.25">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Connector Type</td><td>By default, "<strong>NFS</strong>" is displayed as the selected connector type.</td></tr><tr><td>Credential Manager*</td><td><p>Select the desired credentials manager from the drop-down list. Relevant parameters will be displayed based on the selected option.</p><p>Supported Credential Managers:</p><ul><li>OE Credential Manager</li><li>AWS Secrets Manager</li><li>HashiCorp</li><li>Azure Key Vault</li></ul><p>For more details, click <a href="https://docs.ovaledge.com/connectors/additional-requirements/credential-manager-configuration">here</a>.</p></td></tr><tr><td>License Add Ons</td><td>Select the checkbox for <strong>Data Quality</strong> Add-On to identify data quality issues using data quality rules and anomaly detection.<br>For more details, click <a href="https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/license-types-and-add-ons">here</a>.</td></tr><tr><td>Connector Environment*</td><td>Select the environment (Example: PROD, STG) configured for the connector. This field is mandatory for creating the NFS connection.<br>For more details, click <a href="https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/prerequisites#connector-environment">here</a>.</td></tr><tr><td>Connector Name*</td><td><p>Enter a unique name for the NFS connection              </p><p>(Example: "NFSdb").</p></td></tr><tr><td>Connector Description</td><td>Enter a brief description of the connector.</td></tr><tr><td>Path*</td><td>Provide the path of the location where files or folders are located (Example: E:\NFSPath).</td></tr><tr><td>User ID*</td><td>Enter the operating system or NFS username used to access the configured file path.</td></tr></tbody></table>

**Default Governance Roles**

<table data-header-hidden><thead><tr><th width="220.25"></th><th></th></tr></thead><tbody><tr><td>Default Governance Roles*</td><td>Select the appropriate users or teams for each governance role from the drop-down list. All users configured in the security settings are available for selection.</td></tr></tbody></table>

**Admin Roles**

<table data-header-hidden><thead><tr><th width="220.25"></th><th></th></tr></thead><tbody><tr><td>Admin Roles*</td><td><p>Select one or more users from the dropdown list for Integration Admin and Security &#x26; Governance Admin. All users configured</p><p>in the security settings are available for selection.</p></td></tr></tbody></table>

**No of Archive Objects**

<table data-header-hidden><thead><tr><th width="220.25"></th><th></th></tr></thead><tbody><tr><td>No Of Archive Objects*</td><td><p>This shows the number of recent metadata changes to a dataset at the source. By default, it is off. To enable it, toggle the Archive button and specify the number of objects to archive.</p><p>Example: Setting it to 4 retrieves the last four changes, displayed in the 'Version' column of the 'Metadata Changes' module.</p></td></tr></tbody></table>

**Bridge**

<table data-header-hidden><thead><tr><th width="220.25"></th><th></th></tr></thead><tbody><tr><td>Select Bridge*</td><td><p>If applicable, select the bridge from the drop-down list.</p><p>The drop-down list displays all active bridges that have been configured. These bridges facilitate communication between data sources and the system without requiring changes to firewall rules.<br><strong>Note</strong>: Select a Bridge only if the configured NFS path is accessed through a Bridge.</p></td></tr></tbody></table>

2. After entering all connection details, the following actions can be performed:
   1. Click **Validate** to verify the connection.
   2. Click **Save** to store the connection for future use.
   3. Click **Save & Configure** to apply additional settings before saving.
3. The saved connection will appear on the **Connectors home page**.

## Manage Connector Operations

### Crawl

{% hint style="warning" %}
To perform crawl operations, users must be assigned the Integration Admin role.
{% endhint %}

1. Navigate to the **Connectors** page and click **Crawl/Profile.**
2. This action initiates the metadata collection process from the data source and loads the retrieved metadata into the **File Manager > File Explorer.**
3. In the **File Manager**, click the connector name, select the specific **folder(s) or file(s)**, then click **Catalog /** **Catalog and Profile** from the **Nine Dots** menu. For more details, click [here](https://docs.ovaledge.com/file-manager/file-explorer).

{% hint style="info" %}
Profiling is supported only at the individual file level through the File Nine Dots menu in File Manager. File columns are fetched into the system only after the profiling process has been successfully completed.
{% endhint %}

4. The File Manager displays additional metadata such as file or folder size and last modified date. Folder-level summaries, including file counts, file types, and sample files, are also available where applicable.
5. The selected files or folders will be added to the **Data Catalog > Files/File Columns** tab.

### Other Operations

The **Connectors page** provides a centralized view of all configured connectors, along with their health status.

**Managing connectors includes:**

* **Connectors Health**: Displays the current status of each connector using a **green** icon for active connections and a **red** icon for inactive connections, helping to monitor the connectivity with data sources.
* **Viewing**: Click the **Eye icon** next to the connector name to view connector details.

**Nine Dots Menu Options:**

To view, edit, validate, configure, or delete connectors, click on the **Nine Dots** menu.

* **Edit Connector**: Update and revalidate the data source.
* **Validate Connector:** Check the connection's integrity.
* **Settings**: Modify connector settings.
  * **Crawler**: Configure data extraction.
  * **Access Instructions**: Add notes on how data can be accessed.
  * **Business Glossary Settings**: Manage term associations at the connector level.
  * **Lineage**: Select the parsing method (Regular or AI-Augmented) for generating lineage, and set a confidence threshold to control when AI-generated lineage is accepted or held for review. For more details, click [here](https://docs.ovaledge.com/release8.1/connectors/introduction-to-connectors/setup-and-connectivity/connector-settings#lineage-applicable-for-supported-connectors).
* **Delete Connector**: Remove a connector with confirmation.

For more details, click [here](https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/connector-settings).

## Limitations

<table><thead><tr><th width="80.6666259765625">S.No</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>File and folder uploads are not supported for NFS connectors through Bridge.</td></tr><tr><td>2</td><td>For File-based connectors, the folder count in the File Manager and Data Catalog Files module may not match if folders of files are added or deleted in the source system after crawling. Run the connection crawl again to refresh and display the latest changes.</td></tr></tbody></table>

## Troubleshooting

If incorrect parameters are entered, error messages may appear. Ensure all inputs are accurate to resolve these issues. If issues persist, contact the assigned **support** team.

{% tabs %}
{% tab title="Connectivity" %}

<table data-search="true"><thead><tr><th width="82.5703125" align="right">S. No</th><th width="219.5703125">Error Message</th><th width="410.37109375">Error Description &#x26; Resolution</th></tr></thead><tbody><tr><td align="right">1</td><td><strong>Error while validating connection: permission denied while accessing the configured path</strong></td><td><p>The application account does not have the required permissions to access or operate on the configured NFS path.</p><p><strong>Resolution:</strong></p><ul><li>Confirm <strong>Read</strong> permission on the configured path.</li><li>Confirm <strong>Execute</strong> permission on the folder to allow traversal through nested folders during crawling and profiling.</li><li>For operations that create, modify, upload, or delete files, ensure <strong>Write</strong> permission is available on the parent directory.</li><li>Review file ownership and NFS export permissions if access is still denied.</li><li>Retry validation after confirming the required permission.</li></ul></td></tr><tr><td align="right">2</td><td><strong>Error while validating connection: configured path not found or not accessibleInvalid pathFolder validation failed</strong></td><td><p>The configured path is invalid, inaccessible, does not exist, or does not point to a valid directory.</p><p><strong>Resolution:</strong></p><ul><li>Verify that the configured path exists and points to the intended directory.</li><li>Ensure the path uses the correct format and does not contain typing errors or invalid path separators.</li><li>Ensure the NFS share is mounted and accessible from the system where the application or Bridge is running.</li><li>When using a Bridge, verify the path exists on the <strong>Bridge machine</strong>, not the application host.</li><li>Ensure the configured path matches the mounted NFS location.</li><li>If the path is retrieved through a credential manager, confirm that the correct key name is configured.</li></ul></td></tr><tr><td align="right">3</td><td><strong>Unable to connect to NFS server</strong></td><td><p>The NFS server cannot be reached because of network connectivity issues, unavailable services, firewall restrictions, or incorrect NFS export configuration.</p><p><strong>Resolution:</strong></p><ul><li>Verify network connectivity to the NFS server.</li><li>Ensure the NFS service and exports are correctly configured.</li><li>Confirm firewall rules allow the required NFS traffic.</li><li>Verify that the NFS share is mounted and accessible.</li></ul></td></tr><tr><td align="right">4</td><td><strong>Operation timed out or performance is slow</strong></td><td><p>NFS operations take longer than expected because of large directory structures, network latency, or high NFS server load.</p><p><strong>Resolution:</strong></p><ul><li>Verify network connectivity between the application or Bridge and the NFS server.</li><li>Allow additional time for operations involving large files or directories.</li><li>Check NFS server performance and resource utilization.</li><li>Retry the operation after resolving any network or server performance issues.</li></ul></td></tr><tr><td align="right">5</td><td><strong>File operation failed</strong></td><td><p>A file operation such as upload, download, deletion, or directory creation failed because of insufficient permissions, an invalid destination, file locks, or storage limitations.</p><p><strong>Resolution:</strong></p><ul><li>Verify the destination path and required permissions.</li><li>Ensure sufficient disk space is available.</li><li>Check whether the file is locked or being used by another process.</li><li>Retry the operation after resolving the underlying issue.</li></ul></td></tr><tr><td align="right">6</td><td><strong>File system or I/O error</strong></td><td><p>File operations failed because of storage issues, NFS mount problems, or temporary input/output failures.</p><p><strong>Resolution:</strong></p><ul><li>Verify that the NFS mount is healthy and accessible.</li><li>Check available disk space and NFS server status.</li><li>Retry the operation after resolving the infrastructure issue.</li></ul></td></tr></tbody></table>
{% endtab %}

{% tab title="Crawling & Profiling" %}

<table data-search="true"><thead><tr><th width="82.91796875" align="right">S. No</th><th width="220.2265625">Error Message</th><th>Error Description &#x26; Resolution</th></tr></thead><tbody><tr><td align="right">1</td><td><strong>Crawl completed with errors: file type not supported for cataloging</strong></td><td><p>The file extension is not included in the configured list of file types for cataloging.</p><p><strong>Resolution:</strong></p><ul><li>Open the connector settings and review the configured file types.</li><li>Add the required file extension to the list, separated by a comma.</li><li>Run the crawl again after adding the extension.</li></ul></td></tr><tr><td align="right">2</td><td><strong>Profile completed with errors: unable to parse file, structure not recognized</strong></td><td><p>The file structure is inconsistent and cannot be parsed correctly for profiling. This commonly occurs with comma-separated files containing extra or missing delimiters.</p><p><strong>Resolution:</strong></p><ul><li>Confirm that every row contains a consistent number of fields.</li><li>Correct any extra or missing delimiters in the file.</li><li>Verify that the file uses a supported structure and encoding.</li><li>Refer to the documented structure guidelines for the file type before profiling again.</li></ul></td></tr><tr><td align="right">3</td><td><strong>Profile completed with no columns retrieved</strong></td><td><p>The selected file type is supported for cataloging but is not currently supported for profiling.</p><p><strong>Resolution:</strong></p><ul><li>Confirm that the file type is supported for profiling, such as a spreadsheet or comma-separated file.</li><li>For unsupported file types, use cataloging only because column-level details are unavailable.</li><li>Contact the standard support channel if profiling is required for an unsupported file type.</li></ul></td></tr><tr><td align="right">4</td><td><strong>Data parsing failed</strong></td><td><p>Metadata cannot be extracted because the source file uses an unsupported format, inconsistent structure, or incompatible encoding.</p><p><strong>Resolution:</strong></p><ul><li>Verify that the file format and structure are supported.</li><li>Ensure CSV headers, delimiters, and encoding are valid.</li><li>Verify that Excel files are not corrupted or password-protected.</li><li>Correct the file and retry the profiling operation.</li></ul></td></tr></tbody></table>
{% endtab %}
{% endtabs %}

## FAQs

{% tabs %}
{% tab title="Connectivity" %}

<table data-search="true"><thead><tr><th width="82.94921875" align="right">S. No</th><th width="220.30078125">Question</th><th width="410.90234375">Answer</th></tr></thead><tbody><tr><td align="right">1</td><td><strong>Why is no username or password requested while setting up this connector?</strong></td><td><p>This connector uses the account under which the application is running.</p><ul><li>No separate username or password is required.</li><li>The application account must have the required access to the connected folder.</li><li>System-level folder permissions are used during connection, crawling, and profiling.</li></ul></td></tr><tr><td align="right">2</td><td><strong>What permissions are required for NFS file operations?</strong></td><td><p>The required permissions depend on the operation being performed.</p><ul><li><strong>Read permission:</strong> Required to access and read file content.</li><li><strong>Execute permission:</strong> Required on directories to traverse the folder structure during crawling and profiling.</li><li><strong>Write permission:</strong> Required on the parent directory when creating, uploading, or modifying files.</li><li><strong>Delete operations:</strong> Require the appropriate write-level access to the source directory.</li><li>Execute permission alone does not allow file content to be modified.</li></ul></td></tr><tr><td align="right">3</td><td><strong>How should a sensitive or confidential folder path be handled during setup?</strong></td><td><p>A credential manager can be used to hide the actual folder path.</p><ul><li>Store the actual folder path as the credential manager value.</li><li>Assign a key name to the stored path.</li><li>Enter the key name in the connector setup instead of the actual path.</li><li>The application retrieves the actual path during validation.</li></ul></td></tr><tr><td align="right">4</td><td><strong>What is the recommended NFS path format?</strong></td><td><p>Configure an <strong>absolute directory path</strong> that points to a mounted NFS location.</p><ul><li>Relative paths are not supported.</li><li>A path pointing directly to a file is not supported.</li><li>Ensure the configured path corresponds to an accessible mounted NFS directory.</li></ul></td></tr><tr><td align="right">5</td><td><strong>Are symbolic links supported?</strong></td><td>No. Symbolic links and other special file types are skipped during processing to avoid invalid or unsupported file references.</td></tr><tr><td align="right">6</td><td><strong>Does this connector support delta crawling?</strong></td><td><p>No. Delta crawling is not currently supported.</p><ul><li>Crawling does not automatically identify files changed since the previous crawl.</li><li>Each crawl uses the files and folders explicitly selected at that time.</li></ul></td></tr></tbody></table>
{% endtab %}

{% tab title="Cataloging" %}

<table data-search="true"><thead><tr><th width="83.83984375" align="right">S. No</th><th width="220.41015625">Question</th><th width="414.453125">Answer</th></tr></thead><tbody><tr><td align="right">1</td><td><strong>Why are only the files and folders in the first level shown after a crawl?</strong></td><td><p>This is expected behavior for a standard crawl.</p><ul><li>The main connector settings catalog only the first level of files and folders.</li><li>Files and folders inside subfolders are not automatically included.</li><li>Use the folder-level options from the file manager to select deeper levels for cataloging.</li></ul></td></tr><tr><td align="right">2</td><td><strong>Can a file or folder deep inside the structure be cataloged without first cataloging its parent folders?</strong></td><td><p>Yes.</p><ul><li>A specific file or folder can be cataloged directly.</li><li>Parent folders do not need to be cataloged first.</li><li>The selected item appears in the catalog with its correct location.</li></ul></td></tr><tr><td align="right">3</td><td><strong>What is the difference between the various cataloging options available for a folder?</strong></td><td><p>The cataloging options control which content is included and how deep the operation goes:</p><ul><li><strong>Selected item only:</strong> Catalogs only the selected folder.</li><li><strong>Selected item + files:</strong> Includes files up to the selected depth without cataloging subfolders separately.</li><li><strong>Selected item + subfolders:</strong> Includes subfolder structure up to the selected depth without individual files.</li><li><strong>Selected item + subfolders and files:</strong> Includes both subfolders and files up to the selected depth.</li><li>Similar options are available for <strong>cataloging and profiling together</strong>.</li></ul></td></tr><tr><td align="right">4</td><td><strong>Which file types can be added or removed from what gets cataloged?</strong></td><td><p>The connector configuration controls the file extensions included during cataloging.</p><ul><li>Supported extensions such as spreadsheet, comma-separated, text, columnar, and structured data formats are included by default.</li><li>Add a new extension by placing a comma after the existing entries and entering the extension.</li><li>Files with the added extension are recognized during future crawls.</li></ul></td></tr><tr><td align="right">5</td><td><strong>What happens when a file or folder is uncataloged?</strong></td><td><p>Uncataloging affects only the selected item.</p><ul><li>Uncataloging a folder does not automatically remove nested items.</li><li>Uncataloging a file does not affect its parent folder.</li><li>Each item is handled independently.</li><li>A bulk option to remove an entire folder and all nested content is not currently available.</li></ul></td></tr><tr><td align="right">6</td><td><strong>What do the Download and Delete options available for a cataloged file do?</strong></td><td><p><strong>Download:</strong> Retrieves the complete file content for local saving and does not depend on profiling status.</p><p><strong>Delete:</strong> Removes the file from the original source location, not only from the catalog.</p><ul><li>Delete uses the required source-level access to remove the original file.</li><li>Use caution when deleting files from shared folder locations.</li></ul></td></tr></tbody></table>
{% endtab %}

{% tab title="Profiling" %}

<table><thead><tr><th width="83.40234375" align="right">S. No</th><th width="220.22265625">Question</th><th>Answer</th></tr></thead><tbody><tr><td align="right">1</td><td><strong>What does full profiling mean for this connector, and is it truly unrestricted?</strong></td><td><p>Profiling is controlled by a configurable row limit.</p><ul><li>The configured row limit determines how many rows are read during profiling and sample-data viewing.</li><li>Large files are not processed in their entirety when the row limit is lower than the total number of rows.</li><li>The row limit can be adjusted through system settings.</li><li>No upper limit is currently imposed on the configured row count.</li></ul></td></tr><tr><td align="right">2</td><td><strong>Is there a maximum file size that can be profiled?</strong></td><td><p>No fixed maximum file size is enforced directly.</p><ul><li>Profiling is controlled by the configured number of rows rather than file size.</li><li>Large files, including files several gigabytes in size, can be profiled.</li><li>Only the configured number of rows is examined.</li></ul></td></tr><tr><td align="right">3</td><td><strong>Can columns be manually added to a file that does not show any columns by default?</strong></td><td><p>No.</p><ul><li>Column information becomes available only after the file is profiled.</li><li>Columns are derived directly from the file content.</li><li>Manually created or virtual columns are not supported at the file level.</li></ul></td></tr><tr><td align="right">4</td><td><strong>How are files without column headers handled during profiling?</strong></td><td><p>A connector setting is available for files without headers.</p><ul><li>Enable the option indicating that the file does not contain headers.</li><li>For CSV files without column headers, generic column names such as A, B, and C are used.</li><li>Profiling can then proceed without requiring header names in the first row.</li></ul></td></tr><tr><td align="right">5</td><td><strong>Does a data quality rule run only on the sample of rows used for profiling, or on the complete file?</strong></td><td><p>Data quality rules are intended to run against the complete file content.</p><ul><li>Profiling and sample-data viewing use the configured row limit.</li><li>Data quality rules are not limited to the profiling sample.</li><li>Additional limitations may apply to very large files and are still under review.</li></ul></td></tr><tr><td align="right">6</td><td><strong>Which file types support profiling and metadata extraction?</strong></td><td><p>Profiling and metadata extraction are supported for file types such as <strong>CSV and Microsoft Excel (.xls and .xlsx)</strong>.</p><ul><li>Cataloging supports a broader range of file types than profiling.</li><li>Documents, images, and other supported formats can be cataloged without necessarily providing column-level profiling information.</li><li>Corrupted, password-protected, or unsupported file formats cannot be processed for metadata extraction.</li></ul></td></tr><tr><td align="right">7</td><td><strong>Which character encoding is used for CSV files?</strong></td><td><p>CSV files are processed using <strong>ISO-8859-1</strong> encoding.</p><ul><li>Files using other encodings may require conversion for correct character interpretation.</li><li>Ensure the CSV file uses a compatible encoding before profiling.</li></ul></td></tr></tbody></table>
{% endtab %}

{% tab title="Lineage" %}

<table data-search="true"><thead><tr><th width="83.26171875" align="right">S. No</th><th width="220.3984375">Question</th><th>Answer</th></tr></thead><tbody><tr><td align="right">1</td><td><strong>Since a folder itself has no columns, how can lineage be built at the folder level?</strong></td><td><p><strong>When a folder is profiled, the system can use the column information from the profiled folder for folder-level lineage, assuming the files in the folder have the same content and structure.</strong></p><ul><li>A folder does not have its own columns.</li><li>Profiling the folder provides the column information required for folder-level lineage.</li><li>This approach assumes that the files within the folder have the same content and structure.</li></ul></td></tr><tr><td align="right">2</td><td><strong>Which file does the system pick when assigning columns to a folder for lineage?</strong></td><td><p><strong>When folder-level column lineage is required, the folder can be profiled assuming that the files within the folder have the same content and structure. The resulting column information supports lineage at the folder level.</strong></p><ul><li>Folder profiling is used when column-level lineage is required for a folder.</li><li>The files within the folder are assumed to have the same content and structure.</li><li>The profiled folder provides the column information required for folder-level lineage.</li></ul></td></tr></tbody></table>
{% endtab %}
{% endtabs %}

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.ovaledge.com/release8.1/connectors/connector-repositories/file-connectors/nfs-network-file-system.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.