linkedin / linkedin/dr-elephant
Events not stored in local HDFS are not supported
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.4k
- Forks
- 839
- PR merge metrics
- No merged PRs in 30d
Description
When constructing the URLs of the files to be consumed for the processing dr-elephant makes the assumption that the namenodes specified in the config file are the root for said URLs. In some cases these events may live in external storage such as S3 or WASB, both of which support the HDFS interface but are not necessarily accessible with a webhdfs:// prefix.
Contributor guide
No contributing guide indexed for this repository
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
Locate the code that constructs URLs for files consumed during processing, then trace how configured namenodes are used. Confirm how external HDFS-compatible storage such as S3 or WASB is represented, and consider the issue done when those event locations are supported without requiring a webhdfs:// prefix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- hadoop, java, spark
- Domain
- data-engineering, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100