To search you must prefix it with =. See more in the Search section in the Content Services documentation.
- The Equals operator =
java.lang.UnsupportedOperationException:
Exact Term search is not supported unless you configure the field
<{http://www.alfresco.org/model/content/1.0}title> for cross locale search
must not be used in the user search boxes
within the user interface i.e Share, ACS and Digital Workspace, because it will
produce 0 results and the following error will show in the SOLR Logs:
-
Facet labels may be shown incorrectly in the user interface because they include the localization prefix in addition to the original value. For instance {en}value instead of value.
-
Queries used in Alfresco Search REST API only accept the equals operator = for content model properties when the tokenization is set to false. Note: must not be used in the user search boxes If the tokenization is set to false then the = operator will perform an exact field search, rather than an exact term search. The other tokenization options true and both will raise an exception when being used with the equals operator. Changing the tokenization option for a property requires re-indexing all those values in SOLR, this means you must design your custom content model carefully before deploying it to a production environment. For example:
<propertyname="cm:sample">
<type>d:text</type>
<index enabled="true">
<tokenised>false</tokenised>
</index>
</property>
The following features are working as expected in Search Services 2.0 and above deployments with Cross Locale configuration enabled:
- Equals operator can be used from the user interface search boxes and the results are as expected
- Facet labels are returned without the localization prefix, so they are shown consistently in the user interface
- Queries used in Alfresco Search REST API accept the equals operator = for properties with every tokenisation option: false, true and both.