You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2016/06/22 08:05:57 UTC
[jira] [Created] (SPARK-16129) Eliminate direct use of commons-lang
classes in favor of commons-lang3
Sean Owen created SPARK-16129:
---------------------------------
Summary: 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
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