You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexander Lapin (Jira)" <ji...@apache.org> on 2021/05/25 07:33:00 UTC
[jira] [Updated] (IGNITE-14667) Optimise WatchAggregator key
criterion inference
[ https://issues.apache.org/jira/browse/IGNITE-14667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Lapin updated IGNITE-14667:
-------------------------------------
Reviewer: Alexander Lapin
> Optimise WatchAggregator key criterion inference
> ------------------------------------------------
>
> Key: IGNITE-14667
> URL: https://issues.apache.org/jira/browse/IGNITE-14667
> Project: Ignite
> Issue Type: Task
> Reporter: Kirill Gusakov
> Assignee: Kirill Gusakov
> Priority: Major
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Now, MetaStorageManager is listening to the whole range of keys inferred from component watches key criteria. But in practice, it can be a rough strategy and if we have no prefix or range watches - we can infer the watch for collection of keys.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)