[OAK-9910] Full-text queries fail in Boolean analyzed fields when executed over Elastic

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: indexing
• Assignee: Unassigned
• Reporter: Nuno Santos
• Created: 24/Aug/22 12:58
• Updated: 24/Aug/22 13:05

Description

Index definition:

"testIndex": {
 "jcr:primaryType": "nt:unstructured",
 "analyzed": true,
 "type": "Boolean",
 "name": "propa"
}

Data:

/test/a    [propa = true ]
/test/b    [propa = "true"]
/test/c    [propa = false] 

The following query executed with Elastic:

/jcr:root//*[jcr:contains(@propa, 'tru*')]

does not return the correct results of {{{}

{"/test/a", "/test/b"}

{}}}. The same query executes correctly with Lucene.

Using full-text search on a Boolean property is a feature that likely has not many real-world use-cases, but as Lucene supports it, Elastic should also support it.

Issue Links

• relates to: OAK-9875 Prefix query on a Long, analyzed field fails when executed over Elastic
• links to: Elasticsearch issue about missing ignore_malformed option on Boolean fields