Question

ElasticSearch in 8.2 Clarification

Hi All,

I'm in the middle of testing Pega 8.2.2 as an upgrade of our 7.31 installation and was playing around with new ElasticSearch reporting functionality.

Can someone clarify somethings for me please?

There is now a new option to use elasticsearch in the data retrieval section of the report definition.

https://community.pega.com/knowledgebase/articles/improve-reporting-performance-configuring-elasticsearch-indexing

However it doesn't work when usng embedded properties. Instead falling back to using the database.

Falling back to RDBMS. Reason: Missing property. : .Manager.Name

So does this mean, that even with this new option, for embedded properties we still need to call the report definition via activity pxRetrieveSearchData ?

https://community.pega.com/sites/default/files/help_v82/procomhelpmain.htm#engine/search/eng-search-embedded-config-tsk.htm

And another question. Using this new option seems to need the report definition in the Implementation layer, even if "Include Implementation class only" option is used for "Report on descendant class instances". Is this correct?

Thanks
Craig

***Edited by Moderator: Lochan to update platform capability tags***

Comments

Keep up to date on this post and subscribe to comments

September 17, 2019 - 12:40pm

Hello Craig,

Your assumptions are correct.

We specifically answer this question in this help page:
https://community.pega.com/sites/default/files/help_v82/procomhelpmain.htm#data-/data-customproperties-/data-customproperties-search/new.htm

By default, full-text search only allows report definitions to filter based on top-level scalar properties. You can configure search to allow filtering based on embedded properties using the indexing/useDataInstances Dynamic System Setting and invoking search using the pxRetrieveSearchData activity.

From that description we also link the page that you linked in your post to describe setting up that DSS to leverage pxRetrieveSearchData for embedded properties.