Lucene queries for personas returning unexpected results

[swicken-dotcms]

Describe the bug
Lucene queries for personas returning unexpected results

Reproduced on: 22.03.2, 22.08

Related ticket: https://dotcms.zendesk.com/agent/tickets/108233

To Reproduce
From a demo starter

1. Create a new content type called Test CT with a title field and a tag field called testTags that is indexed
2. Add a contentlet with the persona tag ecoenthusiast
3. Try a lucene query

Example 1

+contentType:TestCt
+TestCt.testTags("ecoenthusiast")

Example 2

+contentType:TestCt
+TestCt.testTags("ecoenthusiast:persona")

The first time I tried to recreate this only example 2 returned results. The second time, neither are returning results.

Expected behavior
The query should not require :persona appended, this was not required in previous versions. You should only need the name of the persona.

Beyond that, the results seem generally inconsistent. It might have something to do with how we are dealing with : in the query.

[wezell]

Tags are stored at the root level, e.g. +tags:ecoenthusiast

[dsilvam]

Hey team! Please add your planning poker estimate with Zenhub @freddyucv @victoralfaro-dotcms

[dsilvam]

This is working correctly as commented by @wezell

[freddyucv]

This is working correctly as commented by @wezell

[bryanboza]

Tested on release-23.01 and here the results

After do this Lucene Query here the results:

We are returning just the first example

[dsilvam]

After discussing with @erickgonzalez , the issue is that filtering by +tags:EcoEnthusiast vs +tags:"ecoenthusiast:persona" gives different results.

[dsilvam]

PR: #23848

[josemejias07]

Failed QA - Tested on 23.03_22c57977_SNAPSHOT // Docker // macOS 13.0 // FF v110.0

The below upgrade task should be perform automatically

curl --location --request POST 'http:///api/v1/upgradetask'
--header 'Authorization: Basic YWRtaW5AZG90Y21zLmNvbTphZG1pbg=='
--header 'Content-Type: application/json'
--data-raw '{ "upgradeTaskClass":"com.dotmarketing.startup.runonce.Task230119MigrateContentToProperPersonaTagAndRemoveDupTags"
}
'

[dsilvam]

Passed Internal QA again:
This is working as expected. Query cache needs to be deactivated.

[josemejias07]

Approved QA - Tested on 23.03_cb5a2388_SNAPSHOT // Docker // macOS 13.0 // FF v111.0

[bryanboza]

In order to close this card we need to generate a new starter sire to remove the persona tags.

[wezell]

Not worth holding this card open for this or creating a new starter. Let us make the changes in the starter and they will get picked up when we really need to create a new version.

[bryanboza]

Waiting for a new starter in order to close.

[bryanboza]

Fixed, creation of the new starter is pending