Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUGFIX: Fixes NullPointerException in AnalyticJobGeneratorHadoop2 #294

Merged
merged 10 commits into from
Oct 20, 2017

Conversation

shkhrgpt
Copy link
Contributor

As discussed in issue, #273, using Long.getLong causes NullPointerException. Therefore, using Long.parseLong to convert a string to long.

@akshayrai @shankar37

Please take a look as soon as possible because it's a critical bug in the code base.
Thank you.

* Fix linkedin#162 with the right calculation for resourceswasted and  add missing workflow links (linkedin#207)

* Fix Exception thrown when JAVA_EXTRA_OPTIONS is not present (linkedin#210)
* Fix linkedin#162 with the right calculation for resourceswasted and  add missing workflow links (linkedin#207)

* Fix Exception thrown when JAVA_EXTRA_OPTIONS is not present (linkedin#210)

* Adds an option to fetch recently finished apps from RM (linkedin#212)

* Fixes issue caused by http in history server config property (linkedin#217)

* add config for timezone of job history server (linkedin#214)

* Include reference to the weekly meeting
Copy link
Contributor

@akshayrai akshayrai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @shkhrgpt

@akshayrai akshayrai merged commit 9a7049d into linkedin:master Oct 20, 2017
skakker pushed a commit to skakker/dr-elephant that referenced this pull request Dec 14, 2017
…nkedin#294)

BUGFIX: Uses Long.parseLong method to fix NullPointerException issue AnalyticJobGeneratorHadoop2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants