process.
>
> Any suggestions would be greatly appreciated
>
> Thanks Andy
>
> From: Jey Kottalam
> Reply-To:
> Date: Friday, September 19, 2014 at 12:35 PM
> To: Andrew Davidson
> Cc: "user@spark.apache.org"
> Subject: Re: RDD pipe example. Is this a bug or a
d open a
socket and write to the down stream process.
Any suggestions would be greatly appreciated
Thanks Andy
From: Jey Kottalam
Reply-To:
Date: Friday, September 19, 2014 at 12:35 PM
To: Andrew Davidson
Cc: "user@spark.apache.org"
Subject: Re: RDD pipe example. Is this a
Hi Andy,
That's a feature -- you'll have to print out the return value from
collect() if you want the contents to show up on stdout.
Probably something like this:
for(Iterator iter = rdd.pipe(pwd +
"/src/main/bin/RDDPipe.sh").collect().iterator(); iter.hasNext();)
System.out.println(iter.next
What is in 'rdd' here, to double check? Do you mean the spark shell when
you say console? At the end you're grepping output from some redirected
output but where is that from?
On Sep 19, 2014 7:21 PM, "Andy Davidson"
wrote:
> Hi
>
> I am wrote a little java job to try and figure out how RDD pipe
Hi
I am wrote a little java job to try and figure out how RDD pipe works.
Bellow is my test shell script. If in the script I turn on debugging I get
output. In my console. If debugging is turned off in the shell script, I do
not see anything in my console. Is this a bug or feature?
I am running t
