mata-p commented on issue #4901: URL: https://github.com/apache/hop/issues/4901#issuecomment-2657192541
The "Filter" transfor does allow only one destination to be set, it doesn't require both. This was the description from the previous bug: > In the "Java Filter", it states that both destinations (matching and non-matching) are optional. > > However, if you only set one, you'll see this error: > > Java filter.0 - ERROR: Both matching and non-matching destination transforms need to be specifi The merged PR didn't really change that, it still requires either none or both to be set. I get that if both are unset you can skip evaluating the condition expression alltogether, since everything goes to the void anyway. But why is it needed to add a Dummy transform if I'm not interrested in the rejected rows (or only in those)? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
