Hi, KNIMEr,
A friend told me that this node will have an inconsistent name bug.
version: KNIME 5.4.3
column_name_extractor_bug.knwf (83.7 KB)
reproduce video:
Hi, KNIMEr,
A friend told me that this node will have an inconsistent name bug.
version: KNIME 5.4.3
column_name_extractor_bug.knwf (83.7 KB)
reproduce video:
Hi,
I’m using version 5.4.2, and the same issue occurred again. It’s quite strange. My guess is that it might be related to a faulty indexing algorithm. It seems to start assigning node indices from 0 — with the table creator as the first node — and continues incrementally from there. When we reset the node, it appears to start over again from 0. Just a thought .
An initial scan might be missing. Once one unchecks and checks the option to standardise names it might work.
@mlauber71 Yes, you are right, this way can work. Or when I use this node I don’t configure it(This is also the way I often use it.).
Usually, after this node It may be necessary to change some names. And this may be the place where it is easy to make mistakes.
This is a bug(maybe it’s brought by the modern UI.), but it should be easy to fix.