AEM 6.1 query results difference using TAGs | Community
Skip to main content
gabriellegarda
Level 2
June 8, 2017
Solved

AEM 6.1 query results difference using TAGs

  • June 8, 2017
  • 3 replies
  • 3026 views

I'm using the aem tags over some products nodes(cq:tags).

In my local instance when I run my query asking for this tags over author and publish mode I got the same number of results, however in the qa environment we have result count number that are different between this instances with the same content. our old products are effectively tagged and in the list of this query but any new product is not getting in this count. It is just like new nodes with this tag are not indexed.

I'm using http://localhost:4503/tagging http://localhost:4502/tagginghttp://10.20.0.6:4503/tagging to see the count.

I can see that "everyone" user has read rights over this tag

The tags  and content have been published

I have also tested deactivating my tags and activating again and the same with the content

Old nodes with this tag are listed and work with the tag list and my query

My query is this one

select [a].[jcr:path] as [jcr:path], [a].[jcr:score] as [jcr:score] from [cq:Taggable] as [a] where ([a].[cq:tags] in('mysite:products/tr', '/etc/tags/mysite/products/tr')) and (isdescendantnode([a], [/content/mysite/products/es-ar/]))

I use also indexing on cq:tags property that I have also reindexed.

It seems tag system is freezed in my qa instance it doesn't identify any new node with my tag.

Is there any osgi service that I should check that maybe is stopped?

Why the old nodes using the same tag in the same folder works?

Why is this only happening in publish instance?

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 kautuk_sahni

Reference document:- Best Practices for Queries and Indexing

                                Rebuild Indexes in AEM with Oak Index | Adobe

~kautuk

3 replies

VeenaVikraman
Community Advisor
Community Advisor
June 9, 2017

I assume this could be  because of your indexing. Could you try to replicate the indexing done in your qa publish to your local and check what issue you might be facing ?

gabriellegarda
Level 2
June 9, 2017

Hello Veena, thanks for your reply, Yes I've also published this indexing, we installed this site on our uat instance and it is working, so it seems only a qa instance problem. maybe this instance needs to be reinstalled.

kautuk_sahni
Community Manager
kautuk_sahniCommunity ManagerAccepted solution
Community Manager
June 12, 2017

Reference document:- Best Practices for Queries and Indexing

                                Rebuild Indexes in AEM with Oak Index | Adobe

~kautuk

Kautuk Sahni