Support --verbose and/or --debug options so users don't have to tweak logging backend for basic output
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 205
Description
A good command line interface uses `--verbose` or `--debug` to control verbosity for users and contributors to get more info about what is going on in the program. Currently IIUC a user has to tweak JUL which is quite a poor experience and Java-centric rather than a good command line interface. We should add support for this alongside our other tools (like pipeline options parsing) for making it easy to build a pipeline `main()`.
Note that this is for the construction & submission side / core SDK. Each runner has its own needs as far as how to control the worker logging, though it is probably still better to have a general way.
Imported from Jira [BEAM-3475](https://issues.apache.org/jira/browse/BEAM-3475). Original Jira may contain additional context.
Reported by: kenn.
Contributor guide
Research direction
Start with the existing pipeline options parsing and the construction and submission side of the core SDK, keeping runner worker logging out of scope. Determine how a pipeline main() can accept --verbose or --debug without requiring JUL changes; done means those options provide basic output for users and contributors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- cli, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100