[
https://issues.apache.org/jira/browse/SLING-13405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henry Kuijpers updated SLING-13405:
-----------------------------------
Description:
Add support for Lucene indexes in Sling Mock Oak, as an opt-in feature.
Lucene index support for JCR_OAK is enabled automatically when a compatible
org.apache.jackrabbit:oak-lucene (same or newer version than the shaded Oak) is
in the test class path. No context plugin or code changes are needed. Without
it, or when Oak Lucene classes come from another artifact (e.g. the AEM API
JARs), behavior is unchanged. A warning is logged if a Lucene index definition
is found while Lucene support is not enabled. The warning contains clear
information on what to do to enable it.
Async indexes (async, fulltext-async, hybrid async+nrt/sync) are updated
synchronously within each commit, so index definitions from real instances can
be used unchanged and content is searchable right after saving. Lucene index
definitions in oak:index nodes at non-root paths are supported as well.
was:
Add support for Lucene indexes in Sling Mock Oak, as an opt-in feature.
By default, it's not active. If you run unit tests with a Lucene index present,
without oak-lucene dependency active, you'll get a warning saying that Lucene
is not available.
Opting in means adding the oak-lucene dependency.
> Sling Mock Oak: Support Lucene indexes
> --------------------------------------
>
> Key: SLING-13405
> URL: https://issues.apache.org/jira/browse/SLING-13405
> Project: Sling
> Issue Type: Improvement
> Components: Testing
> Affects Versions: Testing Sling Mock Oak 4.1.0-1.86.0
> Reporter: Henry Kuijpers
> Priority: Minor
> Fix For: Testing Sling Mock Oak 4.1.2-1.86.0
>
>
> Add support for Lucene indexes in Sling Mock Oak, as an opt-in feature.
> Lucene index support for JCR_OAK is enabled automatically when a compatible
> org.apache.jackrabbit:oak-lucene (same or newer version than the shaded Oak)
> is in the test class path. No context plugin or code changes are needed.
> Without it, or when Oak Lucene classes come from another artifact (e.g. the
> AEM API JARs), behavior is unchanged. A warning is logged if a Lucene index
> definition is found while Lucene support is not enabled. The warning contains
> clear information on what to do to enable it.
> Async indexes (async, fulltext-async, hybrid async+nrt/sync) are updated
> synchronously within each commit, so index definitions from real instances
> can be used unchanged and content is searchable right after saving. Lucene
> index definitions in oak:index nodes at non-root paths are supported as well.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)