Unable to get PredicateEvaluator instance | Community
Skip to main content
gkambara
gkambara
Level 2
October 18, 2016
Solved

Unable to get PredicateEvaluator instance

  • October 18, 2016
  • 3 replies
  • 1834 views

Hello,

I'm getting the following errors in author instance:

error.log:10.10.2016 05:03:38.868 ERROR [10.43.32.118 [1476090145519] POST /content/phonegap/my-app/main/jcr:content/pge-app/app-config.newupdate.json HTTP/1.1] com.day.cq.search.impl.builder.QueryBuilderImpl Unable to get PredicateEvaluator instance: limit
error.log:10.10.2016 05:03:38.869 ERROR [10.43.32.118 [1476090145519] POST /content/phonegap/my-app/main/jcr:content/pge-app/app-config.newupdate.json HTTP/1.1] com.day.cq.search.impl.builder.QueryBuilderImpl Unable to get PredicateEvaluator instance: offset

But the stacktrace is not logged (or doesn't exist). Does anyone know what this error means?

It is related to ContentSync, when I stage changes.

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 gkambara

We solved the problem.

We were putting the params "offset" and "limit" in the map, to create the query.

map.put(PredicateGroup.PARAM_OFFSET, "0"); map.put(PredicateGroup.PARAM_LIMIT, PARAM_VALUE_UNLIMITED);

After removing these lines, the error is not logged anymore.

 

Thanks.

3 replies

smacdonald2008
smacdonald2008
Level 10
October 18, 2016

Please provide more details - are you using custom code? What API are you using if you are. If possible - post the code. 

kautuk_sahni
Community Manager
kautuk_sahniCommunity Manager
Community Manager
October 19, 2016

Can you please share with us, your Querybuilder  query?? what value you are using in p.limit ?

Please have a look at this similar post :- 

Link:- http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.html/forum__myhm-i_am_testingasite.html

~kautuk

Kautuk Sahni
gkambara
gkambaraAuthorAccepted solution
Level 2
October 19, 2016

We solved the problem.

We were putting the params "offset" and "limit" in the map, to create the query.

map.put(PredicateGroup.PARAM_OFFSET, "0"); map.put(PredicateGroup.PARAM_LIMIT, PARAM_VALUE_UNLIMITED);

After removing these lines, the error is not logged anymore.

 

Thanks.

Terms & ConditionsAccessibility statement

Loading footer...