add logging to avro version detection
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 87
- Forks
- 73
- Avg merge
- 2h 50m
- Merged PRs (30d)
- 1
Description
its sadly common for users to have multiple avro versions on the classpath, sometimes shoved into innocent-looking jars.
we could add logging to our version detection code - https://github.com/linkedin/avro-util/blob/144d4a0f65ddd0bf545b14bdfeadb2189a81465d/helper/helper/src/main/java/com/linkedin/avroutil1/compatibility/AvroCompatibilityHelper.java#L710 - that would print which classes were examined, out of what jars (getProtectionDomain().toString() on each class) and what was the result.
this would help diagnosing issues
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in helper/src/main/java/com/linkedin/avroutil1/compatibility/AvroCompatibilityHelper.java around the linked version-detection code. Trace the classes it examines and add logging for each class, its protection domain, and the detected result; done means diagnostic output identifies the examined classes, their jars, and the selected version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100