Hi,
while working on an example workflow I encountered several issues when trying to filter by row index / number which required me, as the long value is required for filtering by row index / number, to explore other approaches.
I then realized the Reference Rowe Filter node RowID but not Row Number / Index which however the regular row filter does.
I’d like to suggest to keep all filtering options in a set of similar nodes fully aligned (if plausible).
Best
Mike
Because Reference Row Filter is a quick way of joining and then filtering a table, I think constraining the node on RowID is okay, for it forces you to work with explicitly identified rows. That said, it does not hurt to have more options 
I don’t get it 
Anyways, for consistency reasons and because a numeric filter is / can be more precise than a string based one, having row number based filtering is based on my experience superior.
Until you run out of numbers maybe. I created long IDs with the help of the rank node.
That reminds me of several topics we exchanged about. In regard to the star alliance group, wouldn‘t it be a nice idea to collect limitations in one post?