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 2015/06/09 09:13:00 UTC
[jira] [Commented] (SPARK-8173) A class which holds all the
constants should be present
[ https://issues.apache.org/jira/browse/SPARK-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14578454#comment-14578454 ]
Sean Owen commented on SPARK-8173:
----------------------------------
While I think you might be able to suggest some targeted cases in which some constants should be refactored into one place, I don't think it's true that most are worth moving, and not to one monolithic class. I'm going to close this unless you have more targeted suggestions.
> A class which holds all the constants should be present
> -------------------------------------------------------
>
> Key: SPARK-8173
> URL: https://issues.apache.org/jira/browse/SPARK-8173
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Environment: software
> Reporter: sahitya pavurala
> Priority: Minor
>
> A class which holds all the constants should be present, instead of hardcoding every where(Similar to MRConstants.java in MapReduce)
> All the parameter names when used should be referenced from that class
--
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