Expand my Community achievements bar.

SOLVED

How to manage the Special characters in Full Text AEM Query search

Avatar

Level 1

We are trying to implement search using Full text AEM query. For the keywords without special characters, we are able to get the results, but the presence of any special character is breaking and there is no result.

 

kirankawadubobade_0-1697089260131.png

 

kirankawadubobade_2-1697089465814.png

 

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

@k_bobade Assuming you are using querybuilder.json, in above screen shot. Please check response marked as correct in below post:

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/provide-restricted-access-...

Quoting from the same thread:

Try the XPATH or JCR-SQL2 equivalent of the above query which has support for wildcard character in jcr:contains 

(You can arrive at the same using Explain Query: Tools -> Operations -> Diagnosis -> Query Performance -> Explain Query -> Key in your Query builder predicates -> You can see the XPATH and JCR-SQL2 equivalent and index used)

 

There is no explicit mention about wildcard support in fulltext Query Builder predicate. 

View solution in original post

2 Replies

Avatar

Correct answer by
Employee Advisor

@k_bobade Assuming you are using querybuilder.json, in above screen shot. Please check response marked as correct in below post:

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/provide-restricted-access-...

Quoting from the same thread:

Try the XPATH or JCR-SQL2 equivalent of the above query which has support for wildcard character in jcr:contains 

(You can arrive at the same using Explain Query: Tools -> Operations -> Diagnosis -> Query Performance -> Explain Query -> Key in your Query builder predicates -> You can see the XPATH and JCR-SQL2 equivalent and index used)

 

There is no explicit mention about wildcard support in fulltext Query Builder predicate. 

Avatar

Employee

Hello ,

In AEM special characters in search text are completely ignored and replaced by space.

For eg. hello@12 is searched as hello 12

will result in assets having either hello or 12 or both.