You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "jay vyas (JIRA)" <ji...@apache.org> on 2016/05/26 15:20:12 UTC
[jira] [Updated] (SPARK-15563) Packages specification
[ https://issues.apache.org/jira/browse/SPARK-15563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jay vyas updated SPARK-15563:
-----------------------------
Description:
PROBLEM
Spark packages should be extensible as a mechanism for individual application developers to build productionable blueprints, and should be consumable/rebuildable/verifiable by robots. Otherwise, there is a danger that a "spark package" might just be a link to a github repo without any useful code in it.
SOLUTION
The spark-packages guidelines should enforce that either a `build.sbt`, `build.gradle`, `pom.xml`, or a `Makefile` present as part of the submission process.
I assume the spark-packages are a community maintained standard so the ASF Spark project is a good place to put this into the documentation.
was:
PROBLEM
Spark packages should be extensible as a mechanism for individual application developers to build productionable blueprints, and should be consumable/rebuildable/verifiable by robots.
SOLUTION
The spark-packages guidelines should enforce that either a `build.sbt`, `build.gradle`, `pom.xml`, or a `Makefile` present as part of the submission process.
I assume the spark-packages are a community maintained standard so the ASF Spark project is a good place to put this into the documentation.
> Packages specification
> ----------------------
>
> Key: SPARK-15563
> URL: https://issues.apache.org/jira/browse/SPARK-15563
> Project: Spark
> Issue Type: Improvement
> Components: Documentation
> Reporter: jay vyas
>
> PROBLEM
> Spark packages should be extensible as a mechanism for individual application developers to build productionable blueprints, and should be consumable/rebuildable/verifiable by robots. Otherwise, there is a danger that a "spark package" might just be a link to a github repo without any useful code in it.
> SOLUTION
> The spark-packages guidelines should enforce that either a `build.sbt`, `build.gradle`, `pom.xml`, or a `Makefile` present as part of the submission process.
> I assume the spark-packages are a community maintained standard so the ASF Spark project is a good place to put this into the documentation.
--
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