Hi Rakkesh,
As Xingcan said, the trigger is required by the window to FIRE, you can use
time window (contains a inner trigger) or (ProcessFunction + State + Timer).
Thanks, vino.
2018-07-18 21:44 GMT+08:00 Titus Rakkesh :
> Thanks Xingcan. I specified as GlobalWindow since I am going to put all
Thanks Xingcan. I specified as GlobalWindow since I am going to put all the
elements coming with splittedActivationTuple with a 24 hour expiry and then
do operations on that when elements coming with stream "unionReloadsStream"
(bigger set).
On Wed, Jul 18, 2018 at 4:07 PM, Xingcan Cui wrote:
>
Hi Rakkesh,
The `GlobalWindow` is commonly used for custom window assignment and you should
specify a `trigger` for it [1].
If the built-in window (e.g., tumbling window or sliding window) join in
DataStream API fails to meet the requirements,
you could try the time-windowed join in Table/SQL AP
Thanks for the reply. I have called "env.execute()". But nothing getting
printed. I have a doubt whether "implemented function" is correct with my
"requirement". Please assist.
On Wed, Jul 18, 2018 at 2:57 PM, Xingcan Cui wrote:
> Hi Rakkesh,
>
> Did you call `execute()`on your `StreamExecutionE
Hi Rakkesh,
Did you call `execute()`on your `StreamExecutionEnvironment`?
Best,
Xingcan
> On Jul 18, 2018, at 5:12 PM, Titus Rakkesh wrote:
>
> Dear Friends,
> I have 2 streams of the below data types.
>
> DataStream> splittedActivationTuple;
>
> DataStream> unionReloadsStream;
>
Dear Friends,
I have 2 streams of the below data types.
DataStream> splittedActivationTuple;
DataStream> unionReloadsStream;
These streams are getting data from Kafka and getting data in different
frequencies. "unionReloadsStream" will receive more data than
"splittedActivationTuple".