Hi,
currently, when building pipelines, we use a rather strict validation approach where pipeline elements are added one-after-the-other and a new connection can only be added if the ancestor element is fully configured. The drawback is that it is currently impossible to exchange intermediate pipeline elements (e.g., replace a stream while keeping the rest of the pipeline). My feeling is that this can be frustrating and time-consuming for users in case only minor changes are applied to the pipeline structure. What's your opinion on that? How should a perfect pipeline modeling process work from your point of view? Dominik
