You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksey Plekhanov (Jira)" <ji...@apache.org> on 2023/04/07 10:35:00 UTC
[jira] [Updated] (IGNITE-16452) IndexQuery can run on non-ready dynamically created index or rebuilding indexes
[ https://issues.apache.org/jira/browse/IGNITE-16452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Plekhanov updated IGNITE-16452:
---------------------------------------
Fix Version/s: (was: 2.15)
> IndexQuery can run on non-ready dynamically created index or rebuilding indexes
> -------------------------------------------------------------------------------
>
> Key: IGNITE-16452
> URL: https://issues.apache.org/jira/browse/IGNITE-16452
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.12
> Reporter: Maksim Timonin
> Assignee: Maksim Timonin
> Priority: Major
> Labels: IEP-49, IEP-71
> Time Spent: 10m
> Remaining Estimate: 0h
>
> IndexProcessor register dynamically created index earlier than fill it with data.
> Then IndexQuery can reach the index before it actually ready. So we need to restrict access for such indexes.
> The same behavior is for rebuilding indexes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)