lostluck commented on issue #23101: URL: https://github.com/apache/beam/issues/23101#issuecomment-1364759870
An improved error message is something that's clearer to someone who isn't intimately familiar with the SDK. To me forexample, it's pretty clear, but I also know what it's talking about. I'm also unlikely to make mistakes in pipeline construction that would lead to the error. Here's my suggestion: look at the current error message (see the original description) and figure out what's good about it, and what's bad about it. Then fix the bad parts about it, by adding more information, or reformating the information. A good error message is one that clearly indicates what's wrong, ideally in terms the user understands, or in terms of what the user specified, describes why that's wrong, and finally suggests a way to fix it. In this case, that would be the work around(s). -- 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]
