Hi @dimi@ipazin , the request in the other thread is not exactly the same - hence why I did not propose it.
The request in the other thread finds the top parent only, while what @dimi is looking for is more of the path, meaning finding all parent → grand parent → grand grand parent → … → top ancestor. Unless the path was meant to find the top ancestor only (just like in the other thread)?
Yes, we ended up only extracting the top parents in Knime. We were able to build a path (using cell replacer concatenate) - but our solution was not very “elegant”. Therefore, we opted to rather use service analysis.
indeed @bruno29a request is not same but two interesting things were mentioned in it and that’s the reason of sharing. One is KNIME Network Mining extension which might be able to do this. (I haven’t used it so can’t say it can for sure but worth exploring before going scripting @dimi.) Second one is my comment in one of replies: “…(no Rule Engines outside loop and one Rule Engine was inside loop to give entire path which led to parent)…” which shows you how to get full path. Having said that here is workflow example how to get full path. Looks decent to me @dimi. Top parent hierarchy search_ipazin.knwf (48.0 KB)
At the end one Rule Engine is outside and seems it’s needed there but maybe it’s just too late for me
(And third interesting thing mentioned is how to build better stopping criteria )
Thanks a lot for posting this solution based on the KNIME relational network nodes. This is definitely the best way to deal with this kind of -relational graph- problems.
I would like (need) to run it on the 4.4.1 KNIME version (for the time being) but obviously it is already implemented on the 4.5.0 version lol . Thus, KNIME complains about the -Recursive Loop- nodes for which I have the extension in version 4.4.1 but apparently not compatible with the newest one 4.5.0.
Since the 4.5.0 KNIME version is really just released, would you mind please to just post here a snapshot or explain what was your -Recursive Loop End- configuration ?
Note: The main purpose of the workflow was for retrieving the Path. But since it already compiled the data, I’m able to retrieve the Top Parent also. But I believe that, for the Top Parent, the solution in the other thread is more optimized - or perhaps the solution by @tobias.koetter could be, but I’m not able to test it as I have the same “problem” as @aworker (Knime 4.4.x vs 4.5.x)