Skip to content

Conversation

@MaxGekk
Copy link
Member

@MaxGekk MaxGekk commented Jan 30, 2020

What changes were proposed in this pull request?

Why are the changes needed?

This fixes the following warnings:

  1. RDD.scala:240: constructor Integer in class Integer is deprecated: see corresponding Javadoc for more information.
  2. MutableProjectionSuite.scala:63: constructor Integer in class Integer is deprecated: see corresponding Javadoc for more information.
  3. UDFSuite.scala:446: constructor Integer in class Integer is deprecated: see corresponding Javadoc for more information.
  4. UDFSuite.scala:451: constructor Double in class Double is deprecated: see corresponding Javadoc for more information.
  5. HiveUserDefinedTypeSuite.scala:71: constructor Double in class Double is deprecated: see corresponding Javadoc for more information.

Does this PR introduce any user-facing change?

No

How was this patch tested?

  • By RDDSuite, MutableProjectionSuite, UDFSuite and HiveUserDefinedTypeSuite

@SparkQA
Copy link

SparkQA commented Jan 30, 2020

Test build #117555 has finished for PR 27399 at commit 47c8d5d.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

* that only happens on the driver).
*/
private val stateLock = new Integer(0)
private val stateLock = new Serializable {}
Copy link
Member

Choose a reason for hiding this comment

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

Yeah anything Serializable is fine. Integer.valueOf(0) isn't ideal because it's going to be a shared object. Anything would work - String("") for example. This seems OK to just slightly odd looking. It could also be a proper Lock, used as a lock, but whatever.

Copy link
Member Author

Choose a reason for hiding this comment

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

@srowen Do you want me to modify this?

Copy link
Member

Choose a reason for hiding this comment

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

Seems OK to me as a minimal change that shouldn't matter for behavior.

@srowen
Copy link
Member

srowen commented Jan 31, 2020

Merged to master

@srowen srowen closed this in 2d4b5ea Jan 31, 2020
@MaxGekk MaxGekk deleted the eliminate-warning-part4 branch June 5, 2020 19:43
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.

3 participants