bzablocki opened a new issue, #26278:
URL: https://github.com/apache/beam/issues/26278
### What happened?
Format strings look like this, but are not exactly the same/consistent.
"Processing stuck in step {step name} for at least {duration} without
outputting or completing in state process at {stack trace}".
Goals (As much as possible)
- Ensure lulz logging is implemented in all flavors
- Consistent user step name format (might be the most difficult, I think
some places display "s4" style, and some display "User/Step/Name/Format"
- Use same format string
- Stack trace is displayed in all flavors.
### Issue Priority
Priority: 3 (minor)
### Issue Components
- [X] Component: Python SDK
- [ ] Component: Java SDK
- [ ] Component: Go SDK
- [ ] Component: Typescript SDK
- [ ] Component: IO connector
- [ ] Component: Beam examples
- [ ] Component: Beam playground
- [ ] Component: Beam katas
- [ ] Component: Website
- [ ] Component: Spark Runner
- [ ] Component: Flink Runner
- [ ] Component: Samza Runner
- [ ] Component: Twister2 Runner
- [ ] Component: Hazelcast Jet Runner
- [ ] Component: Google Cloud Dataflow Runner
--
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]
