Splits messages provided by the “mbody Reader” node into individual body parts. Email bodies are often of type “multi-part” (which can be hierarchically nested) -- this node will split a message down into its individual textual and/or binary parts.
For each message part, a new output row is appended -- this
means, that the number of output rows is greater (or at least
equal) the number of input rows. To allow associating and
grouping message parts which belong to the same message, this
node appends a column “Input ID” which resembles the Row ID of
the corresponding input row. Additionally, a “Hierarchy ID” is
appended; this allows to identify the position of a message part
within the multi-part structure. E.g. a Hierarchy ID
1.2.3 denotes a message part at the third position
within its parent, which in turn occurs at the second position
of the grandparent (root).
Message parts can contain either textual or binary data. The output table will contain two columns which either hold the text or binary content of the corresponding message part.
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 mbox Nodes from the below update site following our NodePit Product and Node Installation Guide:
A zipped version of the software site can be downloaded here.
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 chat on Gitter!
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.