🎉 🎉 RAPIDMINER 9.10 IS OUT!!! 🎉🎉
Download the latest version helping analytics teams accelerate time-to-value for streaming and IIOT use cases.
Changed behaviour of "Enable Operator" in RM 7.6
I have noticed that the behaviour of "Enable Operator" has changed in RapidMiner 7.6. Up until RM 7.5 when a connected (input and output) operator was disabled, the connection stayed intact between the previous and the next operator. This was quite helpful, in cases where an operator should be deleted without making a new connection, especially in cases with an irregular operator order, in which adding the connection back in changes the process order.
RM 7.6, however, not only disable the desired operator, but also deletes the entire connection to and from it. This happens only in processes that also have been built in RM 7.6. It behaves as previously when a process was originally built in an earlier version of RM.
Is this behaviour something that others can replicate and confirm? If so, is this a bug or a feature?