apache / apache/beam

[Bug]: Make the lulz logging messages consistent across all flavors of Dataflow

Open
#26,278 4 comments 0 reactions 1 assignee Claimed by @bzablocki View on GitHub
bug go java P3
Dominant language
Java
Stars
8.7k
Forks
4.7k
Avg merge
1d 20h
Merged PRs (30d)
196

Description

### 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

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.