Hi Lu,
@vino yang I think what he means is that the "max"
semantics between window and non-window are different. It changes
non-aggregated fields unpredictably.
That's really an interesting question.
I take a look at the relevant implementation. From the perspective of
codes, "max" always keeps
Hi weizheng,
IMHO, I do not know where is not clear to you? Is the result not correct?
Can you share the correct result based on your understanding?
The "keyBy" specifies group field and min/max do the aggregation in the
other field based on the position you specified.
Best,
Vino
Lu Weizheng 于
