[
https://issues.apache.org/jira/browse/SLING-11844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17730079#comment-17730079
]
Robert Munteanu commented on SLING-11844:
-----------------------------------------
[~abhigarg] - I filed this when I noticed extracted index definitions that look
like this
{code}
{
"/oak:index/some-index-1": { }.
"/oak:index/some-index-2": {
"fullTextEnabled":true,
"type":"lucene"
(etc)
}
{code}
I think the tooling should not emit empty nodes. I don't have a source
content-package yet, but maybe you can try and reproduce based on the existing
tests? I think just adding an empty folder inside the {{_oak_index}} folder
will work.
> Index definitions must not be extracted from empty nodes
> --------------------------------------------------------
>
> Key: SLING-11844
> URL: https://issues.apache.org/jira/browse/SLING-11844
> Project: Sling
> Issue Type: Bug
> Components: Content-Package to Feature Model Converter
> Reporter: Robert Munteanu
> Priority: Major
> Fix For: Content-Package to Feature Model Converter 1.3.4
>
>
> Under certain conditions, extracted index definitions will contain empty
> nodes. These are useless and should be skipped. They can also confuse tooling
> processing the index definitions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
