Re: Changed the behavior of "DataSet.print()"

2015-06-04 Thread Robert Metzger
ueske < > >> >> > > fhue...@gmail.com > >> >> > > > > > >> >> > > > >> >>>> wrote: > >> >> > > > >> >>>>> > >> >> > > > >> >>>>

Re: Changed the behavior of "DataSet.print()"

2015-06-03 Thread Stephan Ewen
t; wrote: >> >> > > > > >> >> > > > >> I agree that avoiding name which starts with “print” is >> better. >> >> > > > >> >> >> > > > >> Regards, >> >> > > > >>

Re: Changed the behavior of "DataSet.print()"

2015-06-03 Thread Stephan Ewen
> > On May 28, 2015, at 11:35 PM, Maximilian Michels < > >> m...@apache.org> > >> > > > wrote: > >> > > > >> > > >> > > > >> > +1 for printOnTaskManager() > >> > > > >> > > >

Re: Changed the behavior of "DataSet.print()"

2015-06-02 Thread Aljoscha Krettek
>> > >> > > > >> > +1 for printOnTaskManager() >> > > > >> > >> > > > >> > On Thu, May 28, 2015 at 2:53 PM, Kruse, Sebastian < >> > > > >> sebastian.kr...@hpi.de> >> > > >

Re: Changed the behavior of "DataSet.print()"

2015-06-02 Thread Maximilian Michels
kManager() > > > > >> > > > > > >> > On Thu, May 28, 2015 at 2:53 PM, Kruse, Sebastian < > > > > >> sebastian.kr...@hpi.de> > > > > >> > wrote: > > > > >> > > > > > >> >> T

Re: Changed the behavior of "DataSet.print()"

2015-06-02 Thread Kostas Tzoumas
at 2:53 PM, Kruse, Sebastian < > > > >> sebastian.kr...@hpi.de> > > > >> > wrote: > > > >> > > > > >> >> Thanks, for your quick responses! > > > >> >> > > > >> >> I also think

Re: Changed the behavior of "DataSet.print()"

2015-06-02 Thread Till Rohrmann
2:53 PM, Kruse, Sebastian < > > >> sebastian.kr...@hpi.de> > > >> > wrote: > > >> > > > >> >> Thanks, for your quick responses! > > >> >> > > >> >> I also think that renaming the old print method should

Re: Changed the behavior of "DataSet.print()"

2015-06-02 Thread Fabian Hueske
gt;>>>>> I would vote for adding another method to the DataSet called > >> >>>>>> "printLocal()" > >> >>>>>>> that has the old behavior. > >> >>>>>>> > >> >>>>>>> On Thu, May 28, 2015

Re: Changed the behavior of "DataSet.print()"

2015-06-02 Thread Aljoscha Krettek
trick. As >> a >> >> contribution to your brainstorming for a name, I propose >> logOnTaskManager() >> >> ;) >> >> >> >> Cheers, >> >> Sebastian >> >> >> >> -Original Message- >> >> From: Fabi

Re: Changed the behavior of "DataSet.print()"

2015-06-02 Thread Robert Metzger
k that renaming the old print method should do the trick. As > a > >> contribution to your brainstorming for a name, I propose > logOnTaskManager() > >> ;) > >> > >> Cheers, > >> Sebastian > >> > >> -----Original Messag

Re: Changed the behavior of "DataSet.print()"

2015-05-28 Thread Chiwan Park
gt; From: Fabian Hueske [mailto:fhue...@gmail.com] >> Sent: Donnerstag, 28. Mai 2015 14:34 >> To: dev@flink.apache.org >> Subject: Re: Changed the behavior of "DataSet.print()" >> >> As I said, the common print prefix might indicate eager execution. >

Re: Changed the behavior of "DataSet.print()"

2015-05-28 Thread Maximilian Michels
; ;) > > Cheers, > Sebastian > > -Original Message- > From: Fabian Hueske [mailto:fhue...@gmail.com] > Sent: Donnerstag, 28. Mai 2015 14:34 > To: dev@flink.apache.org > Subject: Re: Changed the behavior of "DataSet.print()" > > As I said, the common pr

RE: Changed the behavior of "DataSet.print()"

2015-05-28 Thread Kruse, Sebastian
: Donnerstag, 28. Mai 2015 14:34 To: dev@flink.apache.org Subject: Re: Changed the behavior of "DataSet.print()" As I said, the common print prefix might indicate eager execution. I know that writeToTaskManagerStdOut() is quite bulky, but we should make the difference in the behavior very clear,

Re: Changed the behavior of "DataSet.print()"

2015-05-28 Thread Fabian Hueske
as > > > > soon > > > > > as > > > > > > print() is invoked. If you regard print() as a debugging means, > > this > > > > is a > > > > > > severe restriction. > > > > > > I see use cases f

Re: Changed the behavior of "DataSet.print()"

2015-05-28 Thread Stephan Ewen
se cases for both print() implementations, but I would at > > least > > > > > provide some kind of backwards compatibility, be at a parameter or > a > > > > > legacyPrint() method or anything else. As I assume print() to be > very > > > > >

Re: Changed the behavior of "DataSet.print()"

2015-05-28 Thread Fabian Hueske
e restriction. > > > > I see use cases for both print() implementations, but I would at > least > > > > provide some kind of backwards compatibility, be at a parameter or a > > > > legacyPrint() method or anything else. As I assume print() to be very > >

Re: Changed the behavior of "DataSet.print()"

2015-05-28 Thread Robert Metzger
gt; > might otherwise not be directly portable to newer Flink versions. What > do > > > you think? > > > > > > Cheers, > > > Sebastian > > > > > > -Original Message- > > > From: Robert Metzger [mailto:rmetz...@apache.org] > &

Re: Changed the behavior of "DataSet.print()"

2015-05-28 Thread Fabian Hueske
y > > frequently used, a lot of existing programs would benefit from this and > > might otherwise not be directly portable to newer Flink versions. What do > > you think? > > > > Cheers, > > Sebastian > > > > -----Original Message- > > From:

Re: Changed the behavior of "DataSet.print()"

2015-05-28 Thread Robert Metzger
; > Cheers, > Sebastian > > -Original Message- > From: Robert Metzger [mailto:rmetz...@apache.org] > Sent: Dienstag, 26. Mai 2015 11:12 > To: dev@flink.apache.org > Subject: Re: Changed the behavior of "DataSet.print()" > > I've filed a JIRA to u

RE: Changed the behavior of "DataSet.print()"

2015-05-28 Thread Kruse, Sebastian
Message- From: Robert Metzger [mailto:rmetz...@apache.org] Sent: Dienstag, 26. Mai 2015 11:12 To: dev@flink.apache.org Subject: Re: Changed the behavior of "DataSet.print()" I've filed a JIRA to update the documentation: https://issues.apache.org/jira/browse/FLINK-2092 On Fri, May

Re: Changed the behavior of "DataSet.print()"

2015-05-26 Thread Robert Metzger
I've filed a JIRA to update the documentation: https://issues.apache.org/jira/browse/FLINK-2092 On Fri, May 22, 2015 at 11:08 AM, Stephan Ewen wrote: > Hi all! > > Me merged a patch yesterday that changed the API behavior of the > "DataSet.print()" function. > > "print()" now prints to stdout on