Cell Splitter in loop behaves strange . . .

Hi,

When I use the Cell Splitter node in a loop something strange happens.

In practice, some cells are empty. My delimiter is “;” so there are situations like “1;;” for example. I then expect 3 new columns but only 2 are created so the loop gives an error.

If I manually set the Cell Splitter noda to 3 columns then it works fine.

See the attached flow.

Does anyone know why or what I am doing wrong?

THNX

SL_Cell-Splitter_Loop_20230516.knwf (54.0 KB)

Hi @sanderlenselink

Does checking “allow changing table specifications” in the first wf solves your problem?


gr. Hans

1 Like

Hi @HansS

thnx for your very quick respons . . yep, that seems to be the solution

I will dive further in all the parameters of that configuration screen. I didn’t know it.

regards,

1 Like

another little question . . . the Chunk Loop Start requires the type “string” Therefore I use the String Manipulation (Multi column) node to convert to the type string.
However, this node / process makes the flow verry, very slow. How can you fasten that?

Thats not the case for the above mentioned flow because its very small. On my real live actual dataset it takes 15-30min

THNX

https://forum.knime.com/uploads/short-url/kHCnVE3osWjTbBoJQTPghFyiiJw.knwf

Hi @sanderlenselink ,

Why don’t you transform the string after the loop? this will runs at once and can bring some speedy for you. When you are inside the loop, just make the split as you need, less process inside the loop will let more memory to make others stuffs.

Tks,

Denis

@denisfi

you’re fully right . . . however, it was my understanding that to run the loop the type string was required. So, that’s why included the conversion to type string within the loop.

But when I set “Allow changing table specifications” (see above cq @HansS his tip) the type string isn’t needed anymore. And this brings down the processing time by 60%

You all thnx for helping . . . it works :ok_hand:

THNX

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.