Query Builder doesn't give results specifically on the Chinese site | Community
Skip to main content
Level 2
January 16, 2020
Solved

Query Builder doesn't give results specifically on the Chinese site

  • January 16, 2020
  • 3 replies
  • 1798 views

Hi All, I kindly need a help if someone has any idea. I have recently worked on search implementation for a multi site setup. It is working fine on all languages ( arabic, french, japanese) except specifically on chinese. I have used Query builder API along with Lucene indexing. I debugged but the query won't give any result on any query with chinese characters. I have tested on http://localhost:4502/libs/cq/search/content/querydebug.html . 

 

If you have any idea to overcome this issue please let me know. It would be greatly appreciated.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by amogh-personal

AEM by default support most of the language search with query builder API. So make sure you are reading the search team in request parameter using UTF-8 format.

Thanks,
Amogh

3 replies

arunpatidar
Community Advisor
Community Advisor
January 16, 2020
Basavaraj_K
Level 2
January 19, 2020

Hello,

I had same issue with Chines(zh),Japines(ja),Korean(ki) languages, As you know these are differs from other languages representation.

For time being I have fixed this by targeting the languages and changing the querybuilder API parameters as below.

 

parms.put("property", "key");

parms.put("property.value","%"+value+"%");

parms.put("property.operation", "like");

 

You can try out this for time being if it fulfills your requirements.

kautuk_sahni
Community Manager
Community Manager
August 27, 2020
Thank you for sharing the solution. This would help in posterity.
Kautuk Sahni
amogh-personalAccepted solution
Level 2
January 26, 2020

AEM by default support most of the language search with query builder API. So make sure you are reading the search team in request parameter using UTF-8 format.

Thanks,
Amogh