[jira] [Resolved] (SPARK-16129) Eliminate direct use of commons-lang classes in favor of commons-lang3

["Sean Owen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SPARK-16129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Owen resolved SPARK-16129.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.1

Issue resolved by pull request 13843
[https://github.com/apache/spark/pull/13843]

> Eliminate direct use of commons-lang classes in favor of commons-lang3
> ----------------------------------------------------------------------
>
>                 Key: SPARK-16129
>                 URL: https://issues.apache.org/jira/browse/SPARK-16129
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core, SQL, Streaming
>    Affects Versions: 2.0.0
>            Reporter: Sean Owen
>            Assignee: Sean Owen
>            Priority: Minor
>             Fix For: 2.0.1
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org