Hi @pierrel, I totally get where you’re coming from with this, and it would be great to have a splitter with the ability to dynamically add output ports rather than chaining row splitters.
A similar discussion has been had a while ago resulting in a component that attempts to in someway fill the “gap in the market”.
See this post:
Unfortunately components don’t have the ability to allow dynamically adding output ports at design time, so I created a component with 10 row-filter output ports (0 to 9), where you specify the regex pattern to match each, plus an additional 11th port for chaining to the next copy of the component where you have more than 10 patterns, so it can further filter “uncaught rows”.
It also has a a view that tells you how many rows are caught by each filter pattern. In the demo screenshot below, you can see that my config has caught a number of different cities, but I can easily see on the view output that there is an uncaught row, so I can go look at the 11th output (port 10) and quickly see what I’ve missed
In this case, looking at the uncaught rows I can quickly see that my data contained a typo.
