[jira] [Updated] (IGNITE-26683) IndexQuery uses index before data population completes; should throw “index not found”

["Vsevolod Kovalev (Jira)" <ji...@apache.org>]

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

Vsevolod Kovalev updated IGNITE-26683:
--------------------------------------
    Description: During the initial build, IndexQuery treats an initialized-but-unpopulated index as available. Align with the SQL engine: return “index not found” until the index’s data population completes.  (was: Currently, only index rebuilding is marked with a flag. It would be useful to also mark the initial building phase, so that components like IndexQuery can avoid accessing an index before it is fully built.)
     Issue Type: Bug  (was: New Feature)
        Summary: IndexQuery uses index before data population completes; should throw “index not found”  (was: Add index building flag support for initial index build)

> IndexQuery uses index before data population completes; should throw “index not found”
> --------------------------------------------------------------------------------------
>
>                 Key: IGNITE-26683
>                 URL: https://issues.apache.org/jira/browse/IGNITE-26683
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Vsevolod Kovalev
>            Assignee: Vsevolod Kovalev
>            Priority: Major
>              Labels: IEP-49, IEP-71
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> During the initial build, IndexQuery treats an initialized-but-unpopulated index as available. Align with the SQL engine: return “index not found” until the index’s data population completes.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)