Question
Tekclan Software Solutions
IN
Last activity: 3 Feb 2021 22:00 EST
Embeded properties search in report definition by using elastic search database
I am working to retrieve work object data by using report definition configuration by having elastic search as database
I have created an custom search properties and dedicated index for App-Name-work-travel class. After that i reindexed dedicated indexes in search landing page. I am have created a report definition in App-Name-work-travel class. I have chossed Prefer Elasticsearch index in data access tab.
While runnning report i am getting results from elastic search(i have ensured it is returning from elastic search by seeing elastic search query in tracer )if i configured single value properties like .FirstName, .LastName.
But i am trying to use .Traveller.FirstName. traveller is a single page property while trying to run report definition i am seeing SQL query in tracer.
Is there any possible way to retrieve results from elastic search for embedded properties.
DXC
SG
In the custom serach properties is the embeded property is been added and is this also exposed column mapping is done for the same.
Pegasystems Inc.
IN
We have the same scenario like we need to fetch embedded properties and when I have contacted the corresponding team in Pega who owns this functionality.
They clearly said embedded properties are not supported for elastic search from RD.
Alternatively we need to use pxRetrieveSearchData activity in Report definition class to use elastic search for embedded properties.
Updated: 26 Jan 2021 9:27 EST
Tekclan Software Solutions
IN
Thanks @tiruk . But while trying to run Report definition(source --> prefer elastic search in data access tab in Report definition) in pxRetrieveSearchData activity sql query is found (while checking with tracer sql query is found, no elastic search query is found in tracer). How i will ensure pxRetrieveSearchData is retrieving from elastic search index.
Pegasystems Inc.
IN
Hi @DhanasekarC0202,
For the pxRetrieveSearchData, you need to send the query param which is nothing but a query in the JSON format. And also the activity is solely purposed for the elastic search purposes only.
Please let me know if you need any further assistance.
Updated: 1 Feb 2021 1:34 EST
Tekclan Software Solutions
IN
Thanks @seguv.
Can you share sample query in JSON. To understand more clearly..
Bluevoir
IN
@DhanasekarC0202 elastic search query will not be seen from tracer.
However, if you are interested enable loggers on PegaSearch.Searcher.ESSearcher this will print all the elastic search queries in logs.
This way you can track the ES query being executed on indices and the results.
Updated: 2 Feb 2021 7:00 EST
Tekclan Software Solutions
IN
Thanks @Hoyath. I have tried to find this setting in prlog4j.xml to enable but PegaSearch.Searcher.ESSearcher not found in the log file. Can you help me where to add this setting in pega..
Accepted Solution
Updated: 3 Feb 2021 22:00 EST
Bluevoir
IN
@DhanasekarC0202 you dont need to change your prlog4j2 for this.
Just navigate to Configure->system->operations->Logs and then Choose Log Level Settings and enter "PegaSearch.Searcher.ESSearcher" and then set the level to ALL or Debug
Logs will look something like :
@DhanasekarC0202 you dont need to change your prlog4j2 for this.
Just navigate to Configure->system->operations->Logs and then Choose Log Level Settings and enter "PegaSearch.Searcher.ESSearcher" and then set the level to ALL or Debug
Logs will look something like :
2021-02-02 17:55:53,443 [http-nio-8410-exec-9] [ STANDARD] [ ] [ Chandana:01.01.01] (PegaSearch.Searcher.ESSearcher) DEBUG localhost|0:0:0:0:0:0:0:1 hoyath - Executing query on indices data* : { "from" : 0, "size" : 50, "query" : { "bool" : { "must" : [ { "query_string" : { "query" : "*W-1001*", "default_field" : "_instancename", "fields" : [ ], "use_dis_max" : true, "tie_breaker" : 0.0, "default_operator" : "and", "auto_generate_phrase_queries" : false, "max_determinized_states" : 10000, "allow_leading_wildcard" : true, "enable_position_increments" : true, "fuzziness" : "AUTO", "fuzzy_prefix_length" : 0, "fuzzy_max_expansions" : 50, "phrase_slop" : 0, "analyze_wildcard" : true, "escape" : false, "split_on_whitespace" : true, "boost" : 1.0 } } ], "filter" : [ { "query_string" : { "query" : "NOT _isexternal:true", "default_field" : "_instancename", "fields" : [ ], "use_dis_max" : true, "tie_breaker" : 0.0, "default_operator" : "and", "auto_generate_phrase_queries" : false, "max_determinized_states" : 10000, "allow_leading_wildcard" : true, "enable_position_increments" : true, "fuzziness" : "AUTO", "fuzzy_prefix_length" : 0, "fuzzy_max_expansions" : 50, "phrase_slop" : 0, "escape" : false, "split_on_whitespace" : true, "boost" : 1.0 } } ], "disable_coord" : false, "adjust_pure_negative" : true, "boost" : 1.0 } }, "stored_fields" : "*" } 2021-02-02 17:55:53,451 [http-nio-8410-exec-9] [ STANDARD] [ ] [ Chandana:01.01.01] (PegaSearch.Searcher.ESSearcher) DEBUG localhost|0:0:0:0:0:0:0:1 hoyath - Total hits [0], Current hits [0] 2021-02-02 17:55:53,451 [http-nio-8410-exec-9] [ STANDARD] [ ] [ Chandana:01.01.01] (PegaSearch.Searcher.ESSearcher) DEBUG localhost|0:0:0:0:0:0:0:1 hoyath - Running count (unique): 0, Hit count: 0
Updated: 3 Feb 2021 8:32 EST
Tekclan Software Solutions
IN
Thanks @Hoyath . Now i am able to see query generated on log file. It is very helpful