The Index Writer node saves an in-memory Index Object to a specified local directory
or file. This allows preserving indexes generated by indexing nodes (e.g.
Single-Field Indexer) for future use in matching, filtering, or search tasks without
rebuilding them. This node generates a flow variable containing the absolute path to
the stored index file.
The stored index can later be reloaded by the Index Reader Node, enabling efficient
reuse of previously built indexes in matching, filtering, or search workflows without
reindexing the data.
The node serializes both the indexed data and metadata (such as algorithm parameters,
number of entries, and index type) into a compact binary format optimized for
exorbyte’s fuzzy matching engine.
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 exorbyte matchmaker toolbox 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.