Hi Aljoscha,
Thanks for your response.
With all this preliminary information collected, I’ll start a formal process.
Thank everybody for your attention.
Best,
Xingcan
> On Jul 8, 2019, at 10:17 AM, Aljoscha Krettek wrote:
>
> I think this would benefit from a FLIP, that neatly sums up the op
I think this would benefit from a FLIP, that neatly sums up the options, and
which then gives us also a point where we can vote and ratify a decision.
As a gut feeling, I most like Option 3). Initially I would have preferred
option 1) (because of a sense of API purity), but by now I think it’s g
Hi all,
Thanks for your participation.
In this thread, we got one +1 for option 1 and option 3, respectively. In the
original thread[1], we got two +1 for option 1, one +1 for option 2, and five
+1 and one -1 for option 3.
To summarize,
Option 1 (port side output to flatMap and deprecate spli
Personally I prefer 3) to keep split/select and correct the behavior. I
feel side output is kind of overkill for such a primitive function, and I
prefer simple APIs like split/select.
Hao Sun
On Thu, Jul 4, 2019 at 11:20 AM Xingcan Cui wrote:
> Hi folks,
>
> Two weeks ago, I started a thread [
Hi folks,
Two weeks ago, I started a thread [1] discussing whether we should discard
the split/select methods (which have been marked as deprecation since v1.7)
in DataStream API.
The fact is, these methods will cause "unexpected" results when using
consecutively (e.g., ds.split(a).select(b).spli
