Skip to main content
Dell PowerScale is an enterprise scale-out storage system that hosts the industry-leading OneFS filesystem, which can be hosted on-premises or deployed in the cloud. This document loader utilizes unique capabilities from PowerScale that can determine which files have been modified since an application’s last run and only returns modified files for processing. This will eliminate the need to re-process (chunk and embed) files that have not been changed, improving the overall data ingestion workflow. This loader requires PowerScale’s MetadataIQ feature enabled. Additional information can be found on our GitHub Repo: https://github.com/dell/powerscale-rag-connector

Overview

Integration details

Loader features

Setup

This document loader requires the use of a Dell PowerScale system with MetadataIQ enabled. Additional information can be found on our GitHub page: https://github.com/dell/powerscale-rag-connector.

Installation

The document loader lives in an external pip package and can be installed using standard tooling.

Initialization

Now we can instantiate the document loader:

Generic document loader

Our generic document loader can be used to incrementally load all files from PowerScale in the following manner:

UnstructuredLoader

Optionally, the PowerScaleUnstructuredLoader can be used to locate the changed files and automatically process the files producing elements of the source file. This is done using LangChain’s UnstructuredLoader class.
The fields:
  • es_host_url is the endpoint to MetadataIQ Elasticsearch database
  • es_index_name is the name of the index where PowerScale writes its file system metadata
  • es_api_key is the encoded version of your Elasticsearch API key
  • folder_path is the path on PowerScale to be queried for changes

Load

Internally, all code is asynchronous with PowerScale and MetadataIQ and the load and lazy load methods will return a Python generator. We recommend using the lazy load function.

Returned object

Both document loaders will keep track of what files were previously returned to your application. When called again, the document loader will only return new or modified files since your previous run. The connector uses the file’s birth time (btime) to distinguish between ENTRY_ADDED and ENTRY_MODIFIED:
  • ENTRY_ADDED — the file was created after the last checkpoint
  • ENTRY_MODIFIED — the file existed before the last checkpoint and has been modified
  • The metadata fields in the returned Document will return the path on PowerScale that contains the modified file. You will use this path to read the data via NFS (or S3) and process the data in your application (e.g.: create chunks and embedding).
  • The source field is the path on PowerScale and not necessarily on your local system (depending on your mount strategy); OneFS expresses the entire storage system as a single tree rooted at /ifs.
  • The snapshot field is the PowerScale snapshot ID associated with the file.
  • The lin field is the PowerScale logical inode number — a unique, stable identifier for each file on the filesystem.
  • The change_types property will inform you on what change occurred since the last one.
Your RAG application can use the information from change_types to add or update entries in your chunk and vector store. When using PowerScaleUnstructuredLoader, the page_content field will be filled with data from the Unstructured Loader.

Lazy load

Internally, all code is asynchronous with PowerScale and MetadataIQ and the load and lazy load methods will return a Python generator. We recommend using the lazy load function.
The same Document is returned as the load function with all the same properties mentioned above.

Additional examples

Additional examples and code can be found on our public GitHub webpage: https://github.com/dell/powerscale-rag-connector/tree/main/examples that provide full working examples.

API reference

For detailed documentation of all PowerScale Document Loader features and configurations, head to the GitHub page: https://github.com/dell/powerscale-rag-connector/.