[jira] [Resolved] (OAK-4060) Allow use of pre extrcated text cache for incremental indexing

["Chetan Mehrotra (JIRA)" <ji...@apache.org>]

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

Chetan Mehrotra resolved OAK-4060.
----------------------------------
    Resolution: Fixed

Exposed an OSGi config setting {{alwaysUsePreExtractedCache}} (default false). If set to true then {{PreExtractedTextProvider}} would be consulted in normal indexing mode also

* trunk - 1732278
* 1.2 - 1732283

> Allow use of pre extrcated text cache for incremental indexing
> --------------------------------------------------------------
>
>                 Key: OAK-4060
>                 URL: https://issues.apache.org/jira/browse/OAK-4060
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: lucene
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>            Priority: Minor
>             Fix For: 1.2.12, 1.3.17
>
>
> Pre Extraction support was implemented with an assumption that such big indexing would happen as part of reindex so it was used in reindex phase only. Reason to avoid using it in incremental indexing (non reindex case) were
> # Incremental index would does not have text for newly added files. So checking with pre extracted cache would not be useful
> # PreExtraction logic keeps in memory state (blobs_empty.txt,blobs_error.txt) which would then unnecessary hog memory.
> However in some cases people make use of new incremental migration feature in upgrade. Which would lead to one big incremental indexing step once next migration is done and that would then not able to make use of pre extraction support.
> So as a fix we should provide a policy option to ignore the reindex clause per admin setting



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)