The columns values are transformed to JSON objects for each row. When there are conflicting keys, the result is undefined, might vary between different versions of KNIME.
An example transformation:
From table:
Main | Num | text |
---|---|---|
main1 | 2 | Hello |
main2 | 1 | World |
with custom key/values:
const
and
val
,
Main
as data bound key,
Num
with manual
num
key and
text
as automatic:
{"main1":{"text": "Hello", "num": 2, "const":"val"}} |
{"main2":{"text": "World", "num": 1, "const":"val"}} |
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 KNIME JSON-Processing 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.