nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

CMIS contains query issue

udayakumar_p

Why does, when using contains in CMIS query works as like predicate. For example, consider the following query,

Select * from common:basedoctype where CONTAINS('PATH:"//app:company_home/st:sites/cm:digitalcontent/cm:documentLibrary//*"') AND common:keywords ='external_link'.

This query returns all content with keywords 'external_link' and also those contents with keywords 'external_link_text' as well. when i remove the contains clause it return only the contents with keywords external_link.

Why does when using contains it works as if i specified external_link*.

Find more posts tagged with

Alfresco Content Services

Comments

cesarista

Hi:

Probably it is due that your custom property (common:keywords) is being tokenized when indexing. This is done in the indexation part of the cited property in your content model definition. Maybe with a tokenized=false, and a reindexation of this property is enough. But test it first in a dev env to be sure, cause this may be complicated in a production env with many documents with this property (as it may involve a non incremental change of your content model, reindexation, etc).

Regards.

--C.

udayakumar_p

Hi,

Thanks for the reply. I will try it out.

Can you explain what tokenized means?

Also does setting tokenised to false makes the search case sensitive?

cesarista

Hi:

Tokenized means that the value for the SOLR index is splitted in parts (usually by blank spaces or undercores), and indexed separately (usually both, the full term and their part). You have some part of the value in common, so the CMIS query may give both results. The thing is that when using CONTAINS predicate, SOLR does search, and when CONTAINS is not part of the query this query may be solve by the database (depending on your search setup).
No, AFAIK, CMIS searches are case sensitive.

Some links:

Content Model - Defining and Deploying | Alfresco Documentation (look for tokenized)

Transactional metadata queries supported by database | Alfresco Documentation

Regards.

--C.

andy1

If a query goes to the database, case sensitivity is defined by the database collation. With SOLR, full text search matches are case insensitive and identifier matches are case sensitive.

Andy