09-30-2022 04:19 AM
Hello,
We're currently facing a strange behavior in one of our search webscript.
The user can fill some filter, and we will return a list of document based on those filter.
For example:
SELECT * FROM fds:document AS D JOIN cmis:folder AS O ON D.cmis:objectId = O.cmis:objectId WHERE NOT (CONTAINS(D, 'PATH:\"/app:company_home/cm:Failure//*\"') OR CONTAINS(D, 'PATH:\"/app:company_home/cm:DropZone//*\"')) AND D.fds:docType='F1 CONTR' AND D.fds:docSource='mail'
Will return one result :
20211103075626EML502 (fds:document): workspace://SpacesStore/d47f4bc2-d7ed-4753-8cd1-77d6897a3c7b
The following query will also return the same result:
SELECT * FROM fds:document AS D JOIN cmis:folder AS O ON D.cmis:objectId = O.cmis:objectId WHERE NOT (CONTAINS(D, 'PATH:\"/app:company_home/cm:Failure//*\"') OR CONTAINS(D, 'PATH:\"/app:company_home/cm:DropZone//*\"')) AND D.fds:docType='F1 CONTR' AND AND D.fds:docSource='mail' AND O.cmis:name='202111*'
But if we broader the search on the name of the folder, such as " AND O.cmis:name='2021*' ", the query won't return any documents anymore.
The same behavior can be observed if we remove the first condition ( checking if the document is not on the path of cm:Failure and cmropZone ). Which is counterintuitive, you would expect to find more results using broader query parameters.
I've read that it may be due to the tokenization in one property, but the name is not defined in our model, so I've got no idea how to disable it on the folder name attribute.
10-02-2022 04:56 PM
Hi:
Are you sure that broader query is able to finish, and it is not giving some timeout due solr.http.socket.timeout param ?
Regards.
--C.
10-03-2022 06:00 AM
Hi,
I don't believe so, there are no errors indicating a timeout in either alfresco log files, or solr log files.
In order to be sure, I've added solr.http.socket.timeout=120000 to the alfresco-global.properties, and I still have the same issue.
Explore our Alfresco products with the links below. Use labels to filter content by product module.