while working with the Column Expression Node I struggle a lot, maybe because of the lack of documentation, to dynamically define the column type (i.e. string, int etc.). I overwrite via a flow variable expressions > element 0 > outputType > cell-class but to no avail.
All to no avail. I then tried to locate the actual code of the node in GitHub or Bitbucket, to possibly derive the required values, but to no avail either. I hope anyone has an idea.
Awesome Thanks a lot @ArjenEX. Do you happen to know a place where I can find all data types? Iteratively going through each individual type ist tiring to say the least.
PS: Trying to find that information in the GitHub Repo doing a grep -rin core.data.def . … WIP
There we go. But, based on the Test Data Generator – KNIME Hub node there are substantially more data types present than presumably declared Sure I made a mistake … do you spot it?
Boolean value
Date and Time
Duration
List (Collection of: Boolean value)
List (Collection of: Date and Time)
List (Collection of: Number (double))
List (Collection of: Number (integer))
List (Collection of: Number (long))
List (Collection of: String)
List (Collection of: String)
List (Collection of: URI)
Local Date
Local Date Time
Local Time
Number (double)
Number (double)
Number (integer)
Number (long)
Period
Set (Collection of: Boolean value)
Set (Collection of: Date and Time)
Set (Collection of: Number (double))
Set (Collection of: Number (integer))
Set (Collection of: Number (long))
Set (Collection of: String)
Set (Collection of: String)
Set (Collection of: URI)
String
String
String
URI
Zoned Date Time
Data Types extracted via grep from Knime GitHub Repository
PS: I updated the workflow to manually extract all data types from the Column Expression node per your guidance. Interestingly, though, all retrieved values are of type org.knime.core.data.def.StringCell.
Previously it worked. am I stupid or is this a bug?
Thanks for pointing that out. My mistake falls into the same category as missing semicolons or quotes xD
Btw, I managed to identify presumably all data type definitions by poking around the repo and recognizing that a more fuzzy search for “.data.” seems to do the job. I will fine tune my workflow and update that later on.