Space Connector

Provides a file system connection with access to a KNIME Hub Space, for example the "Private" Space on "My-KNIME-Hub". It is also possible to always connect to the Space that contains the current workflow. The resulting output port allows downstream nodes to access files, e.g. to read or write, or to perform other file system operations (browse/list files, copy, move, ...) in the selected Space. Files outside the configured Space cannot be accessed.

Path syntax: Paths for this connector are specified with a UNIX-like syntax such as /myfolder/myfile. An absolute path consists of:

  1. A leading slash ("/").
  2. Followed by the path to the file ("myfolder/myfile" in the above example).

Options

Settings

Space selection
Specify the Space to access.
  • Current Space: If chosen, the file system connection will give access to the Space that contains the current workflow. Note that this option becomes unavailable, as soon as you add the KNIME Hub Credential input port. Moreover, should the current workflow not reside in a Hub Space, then this node provides fallback behavior by instead connecting to the mountpoint (e.g. LOCAL) of the current workflow.
  • Other Space: If chosen, the file system connection will give access to the selected Space.
Hub mountpoint
This option allows to specify a mountpoint (see KNIME Explorer) that connects to a KNIME Hub. Unconnected mountpoints are greyed out and can still be selected, but you need to go to the KNIME Explorer and connect the mountpoint before executing this node. Note that this option becomes unavailable, as soon as you add the the KNIME Hub Credential input port. Once this port is added, the node will always connect to the KNIME Hub specified by the port.
Space
Allows to specify the Space to connect to. The Space must be either within the currently selected Hub mountpoint, or within the KNIME Hub specified by the KNIME Hub Credential input port.
Working directory
Specify the working directory of the resulting file system connection, using the Path syntax explained above. The working directory must be specified as an absolute path. A working directory allows downstream nodes to access files/folders using relative paths, i.e. paths that do not have a leading slash. The default working directory is "/".

Input Ports

Icon…
A KNIME Hub Credential (provided by the KNIME Hub Authentication node).

Output Ports

Icon
File system connection to a KNIME Hub Space.

Popular Predecessors

Popular Successors

Views

This node has no views

Workflows

Links

Developers

You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.

Installation

To use this node in KNIME, install the extension KNIME Server Client from the below update site following our NodePit Product and Node Installation Guide:

v5.4

A zipped version of the software site can be downloaded here.

Plugin provider: KNIME AG, Zurich, Switzerland
Plugin version: 5.4.0.v202407231410
On NodePit since: 2024-12-06
Last update: 2024-12-21
KNIME versions: Since v4.7

Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.

Try NodePit Runner!