Provides a file system connection with access to a KNIME Mountpoint, for example "LOCAL", or "My-KNIME-Hub". It can also provide a file system connection with access to the mountpoint which 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 mountpoint.
Note:In many cases it is not necessary to use this connector node. Nodes that require file system access (e.g. the File Reader node) already provide the same level of access, by choosing for example Read from > Mountpoint. The purpose of this connector node is to make file access with relative paths more flexible, by allowing to explicitly configure the working directory of the resulting file system connection. For example, this makes it easier to relocate (or change) the files that your workflow accesses, because you only need to change the working directory.
Path syntax: Paths for this connector are specified with a UNIX-like syntax such as /myfolder/myfile. An absolute path consists of:
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.
A zipped version of the software site can be downloaded here.
Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.Try NodePit Runner!
Do you have feedback, questions, comments about NodePit, want to support this platform, or want your own nodes or workflows listed here as well? Do you think, the search results could be improved or something is missing? Then please get in touch! Alternatively, you can send us an email to email@example.com, follow @NodePit on Twitter or botsin.space/@nodepit on Mastodon.
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.