Container Output: Several Data Type unsupported

Feedback & Ideas
1

Hi,

I happen to encounter an issue when calling a remote workflow where the Container Output is not supporting unknown data types. Since it is sometimes not possible to guarantee data type consistency and the Container Output not really processing but merely passing data through, why not enabling it to be more generous about unknown data types?

ERROR Container Output (Table) 6:1050     Execute failed: The column type: "?" is not supported
ERROR Call Workflow (Table Based) 3:1323     Execute failed: Failure, workflow was not executed, current state is IDLE.
Container Output (Table) 6:1050: Execute failed: The column type: "?" is not supported

image
image1686Ă—1243 348 KB

UPDATE: It seems the data type “set” and who knows what else, is not supported either. This is … unsettling.

ERROR Call Workflow (Table Based) 3:1323 Execute failed: Unsupported data type: "Set"

Best
Mike

2

Hi Mike,
For full data type and port support, I recommend Workflow Services. The container output node produces JSON and not all data types can be converted to that (I agree though, that for a set type it could be possible).
Kind regards,
Alexander

3

Hi @AlexanderFillbrunn,

I am using these already as it’s about the Container Output node:

Best
Mike

4

Hi Mike,
For it to be a workflow service, you would need to use the Workflow Service Input and Workflow Service Output nodes in connection with the Call Workflow Service node.
Kind regards,
Alexander

1 Like
5

Hi @AlexanderFillbrunn,

maybe I am not quite getting the point you want to make but I am using the equivalent node Call Workflow (Table Based).

image

Best
Mike

6

Hi Mike,
The nodes are not equivalent. The Call Workflow (Table Based) in combination with the container in- and outputs uses JSON as transport protocol for your data, while the Workflow Service nodes use a proprietary binary format that can handle all KNIME types.
Kind regards,
Alexander

2 Likes