Support Article

Search API not working after 7.1.7 upgrade

SA-4816

Summary



After upgrading to 7.1.7 searches using a custom search gadget based on the search API no longer return any results. Post upgrade distributed search (Elasticsearch) is now being used and when tracing you can see this by checking that step one of the pzSearch activity is processed.  Even though all the parameters appear to be correct based on the previous implementation of the search functionality the results are not being returned as expected. In the pzSearch activity we appear to be passing the pySearch page as the content page and then exiting the activity without populating the results to the pySearchResults page.  From the search API documentation the page should be created and the data set in the engine.

Root Cause



This issue is caused by the parameters being passed to the distributed search.  In this case the parameter that was causing the issue was the pySearchOnProperty.  The value was set to "contents".

Resolution



To resolve the issue all that is needed is to stop setting the value for this parameter.  The pySearchOnProperty is an internal field that shouldn't be set and will default to "_content" for the distributed search. 

 

Published January 31, 2016 - Updated October 8, 2020


0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.