Container Input (Table)

This node receives a KNIME table from an external caller (i.e. the Call Workflow (Table Based) node) and makes it available at the output port. A configured parameter makes the Container Input (Table) visible from the external caller and enables the external caller to send a KNIME table to the Container Input (Table) node.

If a data table is connected to the optional input, the node will simply forward this table to the output port unless a table is supplied via the REST API, in which case the supplied table will be available at the output port.

If no input is given, a configured template table is output.

Options

Parameter name

A name for the input parameter(preferably unique). This name is exposed in the REST interface and in the Call Workflow (Table Based) node.

Description

A description for the input parameter. The description is shown in the API specification of the REST interface.

Template table

A template table can be used to define a table structure which allows the workflow to execute properly. The main purpose of the template table is to populate the "InputParameters" field of the generated OpenAPI specification, which is presented to end users for documentation purposes. When a node is executed without receiving any external input (over REST or from the Call Workflow (Table Based) node) and it has no table connected to its optional input port, the template is output. This allows downstream nodes to be configured when no external input is present and simplifies making adjustments to the workflow.

The template table also serves as a table spec when a simplified external input without table spec is received over the REST API. When receiving an input without table spec, the input will be parsed according to the spec defined by the template table, i.e. each input row must contain as many cells as columns in the template table and each cell must contain a type that is compatible to the column spec, throwing an error in case of any inconsistencies.

Set input table as template

By selecting this button, the input table, given one is provided, will be set as the new template table.

Use entire input table

When selected, the entire input table will be set as the template.

Use only first rows

When selected, only the first n rows are used as the template table. Can be especially useful when the input table serves as an example in the OpenAPI specification and you want to avoid over specifying the example with too many rows.

Omit table spec in API definition

When selected, only the data part of the template table is exposed to the OpenAPI definition, showing a well formed simplified example input. Select this if the workflow is expected to be consumed over REST and the caller of the workflow prefers the simplified input format.

Input Ports

An optional input that is directly forwarded to the output of the node, unless overwritten by supplying a table via the REST API.

Output Ports

The table contained in this container. A configured template table is output if no table has been injected from an external source.

Best Friends (Incoming)

• Table Creator (10 %) 
• Molecule Type Cast (10 %) Streamable
• Call Workflow (Table Based) (10 %) 
• Statistics (6 %) 
• Flow Variable IF Switch (3 %) 
• URL to File Path (3 %) Streamable
• File Reader (3 %) Streamable
• Table Reader (3 %) Streamable
• Concatenate (3 %) Streamable
• Concatenate (Optional in) (3 %) Streamable
• Column Filter (3 %) Streamable
• GroupBy (3 %) 
• Missing Value (3 %) 
• String Manipulation (Variable) (3 %) 
• Rule-based Row Filter (3 %) Streamable
• Data Generator (3 %) Streamable
• Call Local Workflow (Row Based) (3 %) 
• List Box Input (3 %) 
• Table View (3 %) 
• Container Output (Table) (3 %) 
• Table to JSON (3 %) 
• JSON to Table (3 %) 
• String to Date&Time (3 %) Streamable
• RDKit Count-Based Fingerprint (3 %) Streamable
• Show all 24 recommendations

Best Friends (Outgoing)

• Container Output (Table) (14 %) 
• Row Splitter (8 %) Streamable
• String Manipulation (8 %) Streamable
• Table Row to Variable (6 %) 
• Decision Tree Predictor (4 %) 
• Extract Column Header (4 %) 
• Create Table Structure (4 %) 
• Cross Joiner (4 %) Streamable
• Call Workflow (Table Based) (4 %) 
• Table Row To Variable Loop Start (2 %) 
• Variable to Table Row (2 %) 
• Java Edit Variable (2 %) 
• Java Snippet (2 %) Streamable
• Chunk Loop Start (2 %) 
• Concatenate (Optional in) (2 %) Streamable
• Column Appender (2 %) Streamable
• Column Filter (2 %) Streamable
• Constant Value Column Filter (2 %) 
• Row Filter (2 %) Streamable
• Reference Row Filter (2 %) 
• Joiner (2 %) 
• Column Splitter (2 %) Streamable
• Rule Engine (2 %) Streamable
• DB Update (2 %) Streamable
• Call Local Workflow (Row Based) (2 %) 
• Document Vector (2 %) 
• Table to JSON (2 %) 
• Columns to JSON (2 %) Streamable
• JSON to Table (2 %) 
• Hash Calculator (2 %) 
• HTTP Retriever (2 %) 
• Show all 31 recommendations

Workflows

• 01_​predictor_​flow
• 03_​Fetch_​ChEMBL_​Target_​Data
• Parse input
• dec_​tree
• h2o_​gbm
• h2o_​glm
• h2o_​naive
• h2o_​rndfor
• log_​regression
• mlp
• svm
• 01_​Deploying_​and_​Validating_​models_​as_​WebServices
• 01_​KNIME_​for_​Performance
• 02_​H2O_​for_​Performance
• 03_​Spark_​for_​Performance
• xgboost
• 02_​Stock-model
• KNIME Server- QikProp
• 02_​Stock-model
• Show all 19 workflows

Installation

To use this node in KNIME, install KNIME JSON-Processing from the following update site:

Developers

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.