[SPARK-16129] Eliminate direct use of commons-lang classes in favor of commons-lang3

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.0.0
• Component/s: DStreams, Spark Core, SQL
• Target Version/s: 2.0.0
• Assignee: Sean R. Owen
• Reporter: Sean R. Owen
• Created: 22/Jun/16 08:05
• Updated: 14/Feb/24 10:54
• Resolved: 24/Jun/16 09:36

Description

There are several instances where we are still using org.apache.commons.lang classes instead of org.apache.commons.lang3. Only the latter is a direct dependency.

That's easy enough to fix. I think it might be important for 2.0.0 even at this late hour, because in addition, Commons Lang's NotImplementedException is being used where I believe the JDK's standard UnsupportedOperationException is appropriate. Since these exceptions may conceivably propagate and be handled by user code they sorta become part of an API.

Issue Links

• is related to: SPARK-47039 Add a checkstyle rule to ban `commons-lang` in Java code
• links to: [Github] Pull Request #13843 (srowen)