Hi,

Are the UUIDs randomly generated when calling .uuid or are they assigned and 
then .uuid will return the same UUID when calling multiple times? The latter 
would be problematic because we would not correctly assign state.

Best,
Aljoscha
> On 19. Sep 2017, at 11:41, Fabian Hueske <fhue...@gmail.com> wrote:
> 
> If this would be the case, that would be a bug in Flink.
> As I said before, your implementation looked good to me.
> All state of window and trigger should be wiped if the trigger returns 
> FIRE_AND_PURGE (or PURGE) and it's clean() method is correctly implemented. 
> 
> I'll CC Aljoscha again for his opinion. 
> We might need to file a JIRA for the issue.
> 
> Thanks, 
> Fabian
> 
> 2017-09-19 11:32 GMT+02:00 gerardg <ger...@talaia.io 
> <mailto:ger...@talaia.io>>:
> Thanks Fabian, I'll take a look to these improvements.
> 
> I was wondering if the increasing state size could be due to that the UUID
> used in the keyBy are randomly generated. Maybe even if I correctly delete
> all the state related to a given key there is still some metadata related to
> the key wandering around.
> 
> Gerard
> 
> 
> 
> --
> Sent from: 
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/ 
> <http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/>
> 

Reply via email to