Report defination on elastic search index
Hello,
I am working on Pega version 8.1.2 and trying to configure report definition on Elastic search index, I have done all the configurations on the report definition and necessary setting for enabling elastic search.
But when I trace the activity I still see pre and post SQLs in the report definition page.
My question for you:
1. is there any link which guides for these configurations?
2. How do I make sure that my report definition is running against elastic search index and not the normal way.
Please help me understand if I am missing anything.
Thanks,
Niharika
Instellars
IN
Hi Niharika,
Following is the link for configuring RDs against Elastic Search:
Please check if you have followed all the steps correctly.
Also, the indexes on the Search landing page should be complete and in an available state. If a report query cannot be run against elastic search, Pega automatically uses a SQL query.
Rabobank
NL
Hello Ajay,
Thank you for the response. Yes all configuration mentioned in the above link has been taken care.
but unfortunately status of All data and all work = UNAVAILABLE.
Also Its good to mention that for custom search properties I have not created "use dedicated index". do you think its necessary?
Also how do I verify that my report definition is running against elastic search index?
Thanks,
Niharika
Instellars
IN
If the status of the objects is UNAVAILABLE, that means you will have to build the indexes first. Please go ahead and initiate the re-indexing.
Dedicated index is not necessary for custom search. However, it does makes the search process faster.
As this functionality is still in its initial stages, there are a lot of things which needs to be in line for the reporting to use elastic search properly. If you have complex reports or have embedded properties, you might need to enable a few more DSS. By default, full-text search only allows report definitions to filter based on top-level scalar properties.
These type of messages in the tracer/logs should tell you if the report attempted to use elastic search or not before jumping to a SQL query.
Falling back to RDBMS. Reason: Missing property.
Labb Ltd
GB
Have you enabled the DSS and set the pyContent.pyGetCachedDistinctValues to true.
Also ensure that the Report definition is compliant with Elasticsearch. If the RD is not compliant for Elasticsearch the engine falls back to SQL queries automatically
Rabobank
NL
Hello Murali,
no I have not set any dss for pyContent.pyGetCachedDistinctValues but enabled it in the report definition.
Do we need to set a DSS? if yes for which ruleset ?
Thanks,
NIharika
Labb Ltd
GB
Yes that setting is in RD only.
But the DSS needed is "reporting/searchdata/enabled" it must be enabled by default.
Owning Ruleset : Pega-Reporting
Purpose : reporting/searchdata/enabled
Value : true
As you are in 8.1.2 its better to check if it is enabled.
Labb Ltd
GB
As Ajay suggested, do you see the below error/warning in logs
These type of messages in the tracer/logs should tell you if the report attempted to use elastic search or not before jumping to a SQL query.
Falling back to RDBMS. Reason: Missing property.
TCS
IN
If you run tracer and enable DB query in the settings, you will be able to see where the query is running. Is it on DB or on the index. if it's running on index, then the report content page will have a property called pxESQueryPost which will look something like this... { "from" : 0, "size" : 50, "timeout" : "30000ms", "query" : { "bool" : { "filter" .......
If it's running in DB, it will have pxSQLStatementPre and pxSQLStatementPost properties containing the DB query. attached images how the elastic and db query steps will look like in the tracer.
Rabobank
NL
Thank you so much for all the information,
unfortunately, even after all the configurations, I still see db query being called on execution of RD.
please let me know if you have any pointers to debug it.
Thanks,
Niharika