Immuta Virtual Filesystem
Audience: Data Owners, Data Users, and System Administrators
Content Summary: This page provides general information about the Immuta Virtual Filesystem, the catalog refresh frequency, and the filesystem cache.
The Immuta Virtual Filesystem provides a mechanism for interacting with the exposed data sources in Immuta using any programming language. When you investigate the filesystem structure, you’ll notice that all the exposed Immuta data sources are actually represented as directories in the structure. If you dive into those directories, you may see further subdirectories or multiple files, depending on how the Data Owner exposed this data source. Those files are actually zero byte files until you read them; at that point, Immuta dynamically hydrates that file from the remote location (or potentially from the Immuta cache. This Immuta Virtual Filesystem can be mounted on any Linux, Mac, or virtual machine.
Catalog Refresh Frequency
The catalog refresh frequency is the maximum amount of time the filesystem will cache the catalog (directory structure) before syncing with Immuta. Lowering the catalog refresh frequency will cause policy changes to be reflected in the filesystem faster, but will also degrade performance when traversing the filesystem often.
As you view files in the virtual filesystem, to speed up consecutive reads, data will be stored in an encrypted cache locally on your machine. The size of the cache can be configured.
Installation and Usage
Platform specific installation and usage instructions can be found below: