Microsoft OneLake Connector

Establishes a connection to the OneLake storage of a Microsoft Fabric workspace, enabling downstream nodes to access, read, and write files.

The node's output port exposes OneLake as a connected file system. This allows downstream nodes to perform common file operations, including reading, writing, browsing, listing, copying, and moving files and folders. For an overview of working with files and file systems in KNIME, see the KNIME File Handling Guide..

Path syntax
Paths use a UNIX-like format. For example: /Example.Lakehouse/Files/myfolder/file.csv. This absolute path includes:

1. Aa leading slash (/)
2. The name of a Fabric-managed item in the workspace (Example.Lakehouse)
3. A predefined folder within the item (Files)
4. A user-defined folder and file (myfolder/file.csv)

Limitations

• Fabric-managed paths are read-only. These include top-level items such as /MyLakehouse.lakehouse and their system folders like /MyLakehouse.lakehouse/Files and /MyLakehouse.lakehouse/Tables.
  The Tables folder contains Delta Lake files for Fabric-managed tables and must not be modified directly.
  Within the Files folder, users can freely create, modify, move, or delete their own subfolders and files.
• Workspace folders are not represented in the file system. Their contents appear at the root level with unique names. This behavior is due to current limitations of the OneLake API, which is in preview and subject to change.