Hello List,

I created a lucene property index as follow:

{
    "async": "async",
    "compatVersion": 2,
    "evaluatePathRestrictions": true,
    "indexRules": {
        "dam:Asset": {
            "includePropertyTypes": [
                "String"
            ],
            "jcr:primaryType": "nt:unstructured",
            "properties": {
                "brand1": {
                    "jcr:primaryType": "nt:unstructured",
                    "name": "jcr:content/metadata/option/1/brand",
                    "propertyIndex": true
                },
                "brand2": {
                    "jcr:primaryType": "nt:unstructured",
                    "name": "jcr:content/metadata/option/2/brand",
                    "propertyIndex": true
                },
                "jcr:primaryType": "nt:unstructured"
            }
        },
        "jcr:primaryType": "nt:unstructured"
    },
    "jcr:primaryType": "oak:QueryIndexDefinition",
    "reindex": false,
    "reindexCount": 1,
    "type": "lucene"
}

If I test the XPATH query /jcr:root/content/dam//element(*,
dam:Asset)[(jcr:content/metadata/option/_x0032_/@brand='E’)]
I get the debug message "cost for lucene-property is 193.0”. So it works as
expected.

But if I add a OR-Statemenet to the XPATH query like
/jcr:root/content/dam//element(*,
dam:Asset)[(jcr:content/metadata/option/_x0031_/@brand='E') or
(jcr:content/metadata/option/_x0032_/@brand='E’)]

I get "cost for lucene-property is Infinity”

Question: Does the Lucene property index support or conditions? I tried
even with a oak property index without success.

Thanks for your help!

Best regards
Burkhard

Reply via email to