[
https://issues.apache.org/jira/browse/GEODE-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16183717#comment-16183717
]
ASF subversion and git services commented on GEODE-3520:
--------------------------------------------------------
Commit acbd66ce97b53506e927cc5ba881d7b2ba9b1b53 in geode's branch
refs/heads/develop from [~nnag]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=acbd66c ]
GEODE-3520: isValid API made public
* In case an index update corrupts the index, the index will be marked
invalid
* Queries will not use that index while executing queries.
* The API isValid had been made public so that users can find out if
the index ia valid or not
* A new field has been added to the list index gfsh command which shows
the isValid flag.
* If while loading the data index during its creation and it causes an
exception, the index creation will fail.
> IndexMaintenanceExceptions should not affect a put
> --------------------------------------------------
>
> Key: GEODE-3520
> URL: https://issues.apache.org/jira/browse/GEODE-3520
> Project: Geode
> Issue Type: Bug
> Components: querying
> Reporter: Jason Huynh
> Assignee: Jason Huynh
>
> If during index maintenance i.e. index update during a put operation , if
> there is an exception, the index is marked invalid, however the put will be
> successful as it is present in the data regions.
> This will require us to provide a user a way to determine which indexes are
> valid/invalid (maybe a new column in GFSH to describe index). The query
> engine would need to avoid using indexes marked as invalid.
> Also provide a Java API isValid on the indexes to know if they are valid.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
