[infinispan-issues] [JBoss JIRA] (ISPN-6220) Speedup index rebuilds but using ADD rather than UPDATE statements when safe

[Tristan Tarrant (Jira)]

     [ https://issues.jboss.org/browse/ISPN-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tristan Tarrant updated ISPN-6220:
----------------------------------
    Fix Version/s: 10.0.0.Final
                       (was: 9.4.8.Final)


> Speedup index rebuilds but using ADD rather than UPDATE statements when safe
> ----------------------------------------------------------------------------
>
>                 Key: ISPN-6220
>                 URL: https://issues.jboss.org/browse/ISPN-6220
>             Project: Infinispan
>          Issue Type: Enhancement
>          Components: Embedded Querying
>            Reporter: Sanne Grinovero
>            Priority: Major
>             Fix For: 10.0.0.Final
>
>
> The {{DistributedExecutorMassIndexer}} relies on update commands to index the new entries, but when we just run a full purge of the index it should be safe to use Add commands instead if we know that there aren't concurrent updates.
> The lack of concurrent updates might be tricky but I think we can find such a condition when using Affinity as the index is being fully controlled by the current indexing engine, similarly to the checks to see if it's safe to use an NRT workspace.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)