s
>
>
>
>
>
>
>
> *From:* Alexis Sarda-Espinosa
> *Sent:* Friday, August 2, 2024 7:47 PM
> *To:* Schwalbe Matthias
> *Cc:* user
> *Subject:* Re: Using state processor for a custom windowed aggregate
> function
>
>
>
> Hi Matthias,
>
>
>
&
* you can aggregate it into the new state
* (cardinalities could change)
Thias
From: Alexis Sarda-Espinosa
Sent: Friday, August 2, 2024 7:47 PM
To: Schwalbe Matthias
Cc: user
Subject: Re: Using state processor for a custom windowed aggregate function
Hi Matthias,
Thank you for looking
n,
>
> TypeInformation keyType,
>
> TypeInformation accType,
>
> TypeInformation outputType)
>
> throws IOException {
>
>
>
>
>
> Cheers
>
>
>
> Thias
>
>
>
> PS: will you come to the FlinkForward conferen
ation outputType)
throws IOException {
Cheers
Thias
PS: will you come to the FlinkForward conference in October in Berlin (to
socialize)?
From: Alexis Sarda-Espinosa
Sent: Wednesday, July 31, 2024 3:46 PM
To: Schwalbe Matthias
Cc: user
Subject: Re: Using state processor for a custom wi
y different as for streaming
>> timers
>>
>>
>>
>> Hope that helps 😊
>>
>>
>>
>> Thias
>>
>>
>>
>>
>>
>>
>>
>> *From:* Alexis Sarda-Espinosa
>> *Sent:* Monday, Jul
> order
> - Triggers will only be fired after processing all events of a
> respective key are processed
> - Semantics are therefore slightly different as for streaming timers
>
>
>
> Hope that helps 😊
>
>
>
> Thias
>
>
>
>
>
>
: Monday, July 29, 2024 9:18 PM
To: user
Subject: Using state processor for a custom windowed aggregate function
Hello,
I am trying to create state for an aggregate function that is used with a
GlobalWindow. This basically looks like:
savepointWriter.withOperator(
OperatorIdentifier.forUid
Hello,
I am trying to create state for an aggregate function that is used with a
GlobalWindow. This basically looks like:
savepointWriter.withOperator(
OperatorIdentifier.forUid(UID),
OperatorTransformation.bootstrapWith(stateToMigrate)
.keyBy(...)
.window(GlobalWindows.cr
