I'm encountering some issues regarding the FTS Alfresco search

[Kixer]

Hello, I'm encountering some issues regarding the FTS alfresco search, specifically when I try to query multiple properties at the same time. Here is the example -

When I try to query "ins:documentArchiveNumber:07-2/1 AND =ins:documentEstablishedManagementBoardLawsuitNumber:12 AND =ins:documentSecondaryAuthorityDecision: partlyUpheldAppeal" it does not return any results even though there is a document with all 3 properties and values. But when I query all the properties individually I get the correct results. When I try to combine the second and the third property I get correct results but for some reason when I combine the first property with the rest it returns no results. The second and the third property are newly added and are correctly indexed as per the Alfresco Node Browser. Can someone who has encountered an issue similar to this help me out?

PS: The same happens when I try to do this in the Alfresco Node Browser using the Query functionality.

[robinp]

Hi, 

Did you try to modify the first part of the query as it was a string?

like this:

ins:documentArchiveNumber:"07-2/1" AND =ins:documentEstablishedManagementBoardLawsuitNumber:12 AND =ins:documentSecondaryAuthorityDecision:"partlyUpheldAppeal"

[Kixer]

Hi, Thank you for your reply.

Yeah I did and it does not work. For some reason the properties that were there in the initial query that was used to filter documents all work without problems. The problems arise when I try to combine those old properties with the newly added/indexed ones. In this case the filter consists of about 23 properties out of which 8 are the newly added ones and the rest are the old ones. When I filter/query by the old ones it works but when I try to combine old ones with new ones it returns nothing even though it should return something.

For example here are the properties of one such document when I try to filter using the filter:

cm:owner:{}
ins:documentArchiveNumber: "07-2/1"
ins:documentCaseArchiveNumber: "07-2"
ins:documentDateReceived: "2024-05-02T00:00:00.000+0000"
ins:documentDecisionOfTheAdministrativeCourtAfterTheLawsuit: "procedureStopped"
ins:documentDecisionPerArticleMadeWithinDeadlineOfTheArticle52OfTheLawAndAdministrativeSports: "inDeadline"
ins:documentDegreeOfSecrecy: "01bdf351-b955-4928-b63b-82c338af2de1"
ins:documentEstablishedManagementBoardLawsuitDate: 
"2024-05-03T00:00:00.000+0000"
ins:documentEstablishedManagementBoardLawsuitNumber: 12
ins:documentEstablishedManagementBoardRequestedWritings: "aesfasdf"
ins:documentEstablishedManagementBoardSubmittedWritings: "gggggbbbbfv"
ins:documentMailType: "vlezna"
ins:documentNumber: 1
ins:documentOrganisationalUnit: "4bbd15a2-1fd9-4d68-9080-c0960fa0f684"
ins:documentReferenceNumber: "07-2/1"
ins:documentRequestForInitiationOfAMisdemeanorCommission: "kuku"
ins:documentSecondaryAuthorityDecision: "partlyUpheldAppeal"
ins:documentSendTo: [""]
ins:documentSenderName: "2f0a8d02-707c-47cd-ab15-925af190274c"
ins:documentStorn: false
ins:documentTitle: "SeriozenTestDokument34"

The difference in the database is that the strings are written without quotes and are searchable without quotes.

[robinp]

Maybe the problem is the escape char /

Do you find the right results if you're not searching with that specific property with that value?

Otherwise, do you have the right results if you use this:

ins:documentArchiveNumber: "07-2*"

If you already checked all the combinations maybe there was something wrong when solr built your new indexes. 

[Kixer · Accepted solution]

Wellp I purged the data and started anew and now it works  

The problem probably was that I was using indexed data from another project that is similar to this and the query failed combining the new props with the old ones.

Thanks for the replies again and have a great day!