Consider publishing fatjar with relocated dependencies for notebooks environment
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 1.1k
- Forks
- 83
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 30
Description
It seems quite common when someone uses a project dependency, to have different versions of our dependencies on the classpath. Project dependencies are loaded before dataframe, so dataframe end up calling those versions and getting exceptions. BOMInputStream happened twice, and another case was CustomDoubleParser.
If we publish a fatjar with relocated dependencies, dataframe will always call them and get no exceptions
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 by reviewing the repository's build configuration and how the notebook environment assembles project dependencies. Compare the reported BOMInputStream and CustomDoubleParser conflicts with the proposed fatjar and dependency relocation approach; done means a publishable artifact whose relocated dependencies avoid classpath version conflicts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100