With this node you can locate and potentially import one or multiple files on any file system that can serve as input for another Generic KNIME Node. This is different from the KNIME "File Reader", in the sense that the file is not read into an internal KNIME Table, but stays on your file system. For non-local files (i.e., everything except for local and workflow-relative files) the files are first downloaded/copied into a temporary file store. This file store will be saved together with the node when closing/exporting the workflow. It will be deleted together with its contents (the downloaded files) when resetting the node. Therefore, if you need something more persitent or more control over when things are deleted, consider using a Transfer Files node and then import the transfered files from your local file system.
This node can access a variety of different file systems. More information about file handling in KNIME can be found in the official File Handling Guide.
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.
To use this node in KNIME, install the extension Generic Workflow Nodes for KNIME from the below update site following our NodePit Product and Node Installation Guide:
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 mail@nodepit.com.
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.