You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2017/10/08 17:31:00 UTC
[jira] [Resolved] (SPARK-17726) Allow RDD.pipe to take script
contents
[ https://issues.apache.org/jira/browse/SPARK-17726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon resolved SPARK-17726.
----------------------------------
Resolution: Won't Fix
I think there are many workarounds for this, e.g, having a base script in worker nodes taking an parameter, another script in strings. I am resolving this for now as it looks the use case can't be explained properly anyway here.
> Allow RDD.pipe to take script contents
> --------------------------------------
>
> Key: SPARK-17726
> URL: https://issues.apache.org/jira/browse/SPARK-17726
> Project: Spark
> Issue Type: New Feature
> Reporter: Ratan Rai Sur
> Priority: Minor
> Labels: features
>
> I have a need to run arbitrary shell scripts which get passed to me as strings. I was wondering if there could be a flag that indicates that the string needs to be written to a temp file and then executed.
> I took a look at PipedRDD.scala and would be willing to take a crack at making changes, but I wanted to get some feed back on why this can't or shouldn't happen.
> Thanks!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org