Using other special characters in fulltextsearch query builder is not return any results. | Community
Skip to main content
N
nickdanielle
August 16, 2022
Solved

Using other special characters in fulltextsearch query builder is not return any results.

  • August 16, 2022
  • 1 reply
  • 1021 views

Hello!

I have a content fragment which has a title property of:

jcr:content/data/master/@title = "Qi® Wireless 15W Receiver Reference Design"

Now I have here a query :

http://localhost:4502/bin/querybuilder.json?1_property=jcr:content/data/cq:model&1_property.0_value=/conf/mchp/settings/dam/cfm/models/reference-designs&1_property.p.or=true&2_group.0_path=/content/dam/mchp/content-fragments/reference-designs&2_group.p.or=true&3_property=jcr:content/data/master/processorFamily&4_property=jcr:content/data/master/functions&5_property=jcr:content/data/master/markets&group.0_fulltext=Qi®*&group.0_fulltext.relPath=jcr:content/data/master/@title&group.p.or=true&orderby=@jcr:content/jcr:lastModified&orderby.sort=desc&p.facets=true&p.limit=10&p.offset=0&type=dam:Asset

But somehow it's not returning any result when fulltextsearch is = "Qi®*"
But it returns a result when fulltextsearch is = "Qi®"

But I need to make it dynamic and needs to have '*' at the end of the string always (or is it required?).

Need some help.
Thanks!!!
 
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 Vijayalakshmi_S

@nickdanielle 

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. 

 

1 reply

Vijayalakshmi_S
Vijayalakshmi_SAccepted solution
Level 10
August 16, 2022

@nickdanielle 

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. 

 

    Terms & ConditionsAccessibility statement

    Loading footer...