You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2021/06/13 22:41:02 UTC

[jira] [Updated] (FLINK-8435) Adding BloomFilter/HyperLogLog state as Managed once

     [ https://issues.apache.org/jira/browse/FLINK-8435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flink Jira Bot updated FLINK-8435:
----------------------------------
    Labels: auto-unassigned stale-major  (was: auto-unassigned)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 30 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> Adding BloomFilter/HyperLogLog state as Managed once
> ----------------------------------------------------
>
>                 Key: FLINK-8435
>                 URL: https://issues.apache.org/jira/browse/FLINK-8435
>             Project: Flink
>          Issue Type: New Feature
>          Components: Runtime / Task
>            Reporter: Moein Hosseini
>            Priority: Major
>              Labels: auto-unassigned, stale-major
>
> Many times doing something approximately is enough for users (Such as counting). I think we should implement bloom filter and HyperLogLog as state for keyed state. By this users are able to filter or process many things approximately.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)