igor-dv commented on PR #40404: URL: https://github.com/apache/beam/pull/40404#issuecomment-6045244880
The proto field is just an id, I agree it is not a message type. I am working on a custom runner based on Beam. The Job API only gives the failure as text, and matching that text is brittle (the same words show up in user errors). I put a small class tag in `message_id` on the ERROR message so the submitter can tell the class of failure without parsing the message text. Upstream `WaitForCompletion` already prints that id, then drops it. I want it on the error so I don't have to fork `WaitForCompletion` or parse the log line. Runners that leave it empty or use a counter are fine. `MessageID` is then empty or that value, and callers that don't care ignore it. -- 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]
