[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-deprioritized-major auto-deprioritized-minor auto-unassigned (was: auto-deprioritized-major auto-unassigned stale-minor) Priority: Not a Priority (was: Minor) This issue was labeled "stale-minor" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Minor, please raise the priority and ask a committer to assign you the issue or revive the public discussion. > 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: Not a Priority > Labels: auto-deprioritized-major, auto-deprioritized-minor, > auto-unassigned > > 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.20.1#820001)
[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-deprioritized-major auto-unassigned stale-minor (was: auto-deprioritized-major 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 Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, 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: Minor > Labels: auto-deprioritized-major, auto-unassigned, stale-minor > > 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.20.1#820001)
[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-deprioritized-major auto-unassigned (was: auto-unassigned stale-major) Priority: Minor (was: Major) This issue was labeled "stale-major" 7 ago and has not received any updates so it is being deprioritized. If this ticket is actually Major, please raise the priority and ask a committer to assign you the issue or revive the public discussion. > 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: Minor > Labels: auto-deprioritized-major, auto-unassigned > > 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)
[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)
[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 (was: stale-assigned) > 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 >Assignee: Aegeaner >Priority: Major > Labels: auto-unassigned > > 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)
[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: stale-assigned (was: ) > 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 >Assignee: Aegeaner >Priority: Major > Labels: stale-assigned > > 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)
[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 ] Robert Metzger updated FLINK-8435: -- Component/s: API / DataStream > 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: API / DataStream >Reporter: Moein Hosseini >Assignee: Aegeaner >Priority: 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 (v7.6.3#76005)
[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 ] Robert Metzger updated FLINK-8435: -- Component/s: (was: API / DataStream) Runtime / Operators > 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 / Operators >Reporter: Moein Hosseini >Assignee: Aegeaner >Priority: 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 (v7.6.3#76005)
[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 ] Chesnay Schepler updated FLINK-8435: Environment: (was: 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.) > 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 >Reporter: Moein Hosseini >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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 ] Chesnay Schepler updated FLINK-8435: Description: 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. > 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 >Reporter: Moein Hosseini >Priority: 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 (v7.6.3#76005)
