[jira] [Closed] (GEODE-7486) IndexManager is not consistent

["Ernest Burghardt (Jira)" <ji...@apache.org>]

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

Ernest Burghardt closed GEODE-7486.
-----------------------------------
    Assignee: Ernest Burghardt  (was: Juan Ramos)

> IndexManager is not consistent
> ------------------------------
>
>                 Key: GEODE-7486
>                 URL: https://issues.apache.org/jira/browse/GEODE-7486
>             Project: Geode
>          Issue Type: Bug
>          Components: querying
>            Reporter: Juan Ramos
>            Assignee: Ernest Burghardt
>            Priority: Major
>              Labels: GeodeCommons
>             Fix For: 1.12.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> While working on GEODE-7351, I've found that the current {{IndexManager}} behaviour is not consistent:
> * If there's an exception thrown while adding an index mapping, we eat the exception, log an useless warning, and mark the index as invalid.
> * If there's an exception thrown while removing an index mapping, we re-throw the exception and leave the index as it is, even though it should be marked as invalid as well.
> The {{IndexManager}} should behave consistently and mark the index as {{invalid}} in both situations, clearly logging what went wrong while adding/removing the mapping.



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