Row Filter: Setting lost after re-execution

[tomljh]

My software environment: knime 5.3.1. Operating system: win10.

This problem occurs in the Row Filter node in the new version 5.3.1.

Test process description: I want to filter out the row with “Row number = 2” according to “Row number”. The filtering is executed correctly, but when the configuration interface is opened for the second time, the correct setting is not loaded.

That is, I set the parameter to “2”. When I open it for the second time, I hope it is still “2” instead of “1”.

RowFilterNode5_3_1.knwf (10.4 KB)

[HaveF]

Off the topic. Haha, this reminds me of a joke:

[mwiegand]

Hi @tomljh,

that issue likely is caused by the row index usually starting at zero.

2024-08-21 08:16:34,564 WARN Row Filter 5:7 Row number must be larger than zero: 0

There is also a possibly related post which you might be interested in:

Inconsistent Row Filter node behaviour with Row Number filter

During the creation of a workflow to assist with a question on the forum, I ran into strange and inconsistent behaviour on the Row Filter node with respect to row numbering. In searching I now see that this was mentioned back in 2017, but haven’t seen it actually documented or acknowledged as a bug, which I believe it is. Whilst additional comments in that 2017 post gave background regarding 0 or 1 based numbering schemes (which are now well documented as inconsistent across nodes) they did n…

As a workaround, while being in Modern UI, search for row filter //deprecated to get the currently much better old node.

Best
Mike

[tomljh]

Thank you for your reply. The difference between “Row Index” and “Row Number” as I understand it is that “Row Index” starts from 0 and “Row Number” starts from 1.

But my problem here is not this concept. Instead, I have set “Row Number = 2”. My purpose is to take the second row of the entire table (the second row counted from 1). The filtering is executed successfully and there is no problem. My problem is that I set the parameter to 2, and when I open the configuration interface for the second time, it shows 1.

For another example, I set “Row Number = 3” and the execution is successful. When I open the configuration interface for the second time, I hope it shows 3, but it still shows 1.

The problem is that in the new version 5.3.1, in the configuration interface of the new node, when the interface is opened for the second time, the previous settings are not loaded correctly.

[mwiegand]

Ah, now I understand. I recorded a screen recording that better visualized the bug.

That is concerning …

@DanielBog FYI

PS: @tomljh to better reflect the seriousness of the discovered bug I’d suggest, if still possible, to alter the title to something like “Row Filter: Setting lost after re-execution”

[tomljh]

Thank you very much for your enthusiasm. Your video clearly illustrates my problem.

I have modified the title. It is indeed not written clearly.

[DanielBog]

Hey,

thank you for reporting this problem and thanks @mwiegand for the nice video. This helps us a lot in understanding the issues and will speed up the development time. We could isolate and fix the problem (internal ticket UIEXT-2110). It will be released with the next version (5.3.2).

Thanks again for reporting and sorry for the inconvinience,
Daniel

[takbb]

@HaveF

Off the topic. Haha, this reminds me of a joke…

lol, @HaveF

Continuing “off the topic” with the “off-by-one” errors theme, the good news re the new Row filter/splitter/cropper nodes is that they have removed the inconsistency in KNIME, mentioned in the post that @mwiegand linked above, as demonstrated by this workflow (KNIME 5.3):

Row Number inconsistency.knwf (89.5 KB)

I just have to do is remember that I no longer need to factor this “feature” in, for future workflows when using the new nodes