SQl2 query with contains does not find any nodes

[Magicr]

Hello,

I'm facing following strange situation and I have no idea about this behavior, using AEM6.4. Given is following situation:

In my project exists some nodes they have in property 'sling:resourceType' the value "c109_video". So I created two queries to find those nodes.

Query one: 

SELECT * FROM [nt:base] AS n WHERE ISDESCENDANTNODE(n, [/content/sites]) AND n.[sling:resourceType] like 'c109_video' ORDER BY n.[jcr:created] ASC

The result list contains more than zero hits. 

Query two: 

SELECT * FROM [nt:base] AS n WHERE ISDESCENDANTNODE(n, [/content/sites]) AND CONTAINS(n.[sling:resourceType], 'c109_video') ORDER BY n.[jcr:created] ASC

 The result list is empty.

Which reasons are responsible for this difference?

[aemmarc]

CONTAINS and LIKE do two different things.

[Magicr]

Ok und what is difference? What is the usecase of contains?

[aemmarc]

https://docs.adobe.com/docs/en/spec/jcr/1.0/6.6.5.1_jcr_like_Function.html

[aemmarc]

https://docs.adobe.com/docs/en/spec/jcr/1.0/6.6.5.2_jcr_contains_Function.html

[Magicr]

I do not understand the difference for my case. What I know, if you use contains it looks for exact matching. So you can define more than one pattern to find occurences. While with like is allowed to use wildcards (the % sign). My provided example has an exact match, or not? 

[Magicr]

If I look into jcr:title I will get a result with contains, other node properties do not work. Any ideas?

[Magicr]

Based on https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/search-inside-a-page-conte... is possible that contains looks only in nodes from type 'cq:Page' and not in other node types? That wold explain this strange situation.

[abhilakhpatre1]

Your first query looks fine and gives a expected results. If you want to search with like clause you can also introduce wildcard characters based upon your requirements to match the words (trailing or starting)

When it comes to CONTAINS , it will also work for non-delimetered words (simplewords) for it to be worked for delimited words like in your case _ underscore, you have to add double quotes to the text you are searching. I have rephrased your query with double quotes like below :

SELECT * FROM [nt:base] AS n WHERE ISDESCENDANTNODE(n, [/content/sites]) AND CONTAINS(n.[sling:resourceType], “'c109_video'”) ORDER BY n.[jcr:created] ASC

For more details you can also refere below links to understand the difference:

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/difference-between-contain...

https://stackoverflow.com/questions/48077571/why-does-contains-find-inequal-text-strings-in-jcr-sql2

Hope this might be helpful for you

[Magicr]

Thanks for trying to help. I tried your suggested query and the result list is still empty. 

Update: It seems only the property jcr:title returns a non empty resultlist. What  a hell?

[Jineet_Vora]

@Magicr,

Difference between Contains and Like:
1. Contains: Searches the given string anywhere in the data

2. Like: Works with regular expression and searches for an expression. e.g. %adobe%

[Magicr]

@Jineet_Vora I think you haven't understood my question right. And I haven't marked this as solution (whoever it was).

[Magicr · Accepted solution]

Some associates there works also with AEM faced the same situation. They have also no explainnations for this strange behavior. They think there are not documented changes in Service Pack 6, so thier recommendation is using like operator instead of contains

[sarikajain]

I am facing similar issue. I suspected that the only possible explanation for this behavior, is that contains performs a fulltext search and hence requires to be backed up by an index while like performs simple String comparison. I looked for some documentation to confirm on my doubt and I found the exact link I was looking for. If you are still looking for an answer, here it is:

https://developer.adobe.com/experience-manager/reference-materials/spec/jcr/1.0/6.6.3.3_Property_Con...

Spoiler

Support for the jcr:contains() (CONTAINS() in SQL) function is not required for any property types in particular. It is however required to work at the node level. In that case it applies to those properties of the node for which the implementation maintains an index. 

I have only one doubt left though. I hope someone is able to answer it for me. The contains function works for custom properties and jcr:title but not for other properties in jcr, sling and cq namespace and which oak:index node should I refer for check which index is being used by the contains function.