GitHub user bamaer added a comment to the discussion: HOP-import kettle
Yes @nadment, that was also the reason behind my initial questions. Removing the hidden steps from the import is easy, but there will be dangling hops from/to those steps that can't be removed without significant work in the importer. Sure, we can just leave those hops and assume they will be removed the first time such a workflow/pipeline is opened and saved in Hop Gui, but it's safe to assume @EricTonissen won't manually open/save all of the ~8.000 files he needs to migrate, and there could be other side effects. Of course we can create a feature request and look into this, but this is a discussion after all, and see if we can identify what that requested change would look like. The last thing we want to do is import bad decisions and code quality issues from PDI/Kettle into Apache Hop. GitHub link: https://github.com/apache/hop/discussions/6166#discussioncomment-15227908 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
