You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Nuno Santos (Jira)" <ji...@apache.org> on 2022/08/24 13:01:00 UTC
[jira] [Commented] (OAK-9910) Full-text queries fail in Boolean analyzed fields when executed over Elastic
[ https://issues.apache.org/jira/browse/OAK-9910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584235#comment-17584235 ]
Nuno Santos commented on OAK-9910:
----------------------------------
OAK-9875 fixes full-text search for analyzed properties with types other than Boolean, but due to a limitation of Elasticsearch, it does not fix it for Booleans.
> Full-text queries fail in Boolean analyzed fields when executed over Elastic
> ----------------------------------------------------------------------------
>
> Key: OAK-9910
> URL: https://issues.apache.org/jira/browse/OAK-9910
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: indexing
> Reporter: Nuno Santos
> Priority: Minor
>
> Index definition:
> {noformat}
> "testIndex": {
> "jcr:primaryType": "nt:unstructured",
> "analyzed": true,
> "type": "Boolean",
> "name": "propa"
> }
> {noformat}
> Data:
> {noformat}
> /test/a [propa = true ]
> /test/b [propa = "true"]
> /test/c [propa = false] {noformat}
> The following query executed with Elastic:
> {noformat}
> /jcr:root//*[jcr:contains(@propa, 'tru*')]
> {noformat}
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)