data table index does not auto rebuild with upgraded searching module

data table index does not auto rebuild with upgraded searching module

recently, Pega help to upgrade our searching module, the upgraded searching setting section is like below

Pega support said that, after this upgrade, the data table index can auto rebuild once any update on the table.

Previously, we need manually rebuild the index.

However, after upgraded, we still need do so, no auto rebuild we can see. Any idea? Thanks.

@MaxonL16591286 search is externalized ?

@MaxonL16591286 might have got corrupted due to some reasons. Please try rebuilding the indexes.

@Anoop Krishna

Manually rebuild works normally.

So whether the upgraded searching function support auto rebuild?

@MaxonL16591286 yes but for that to work, class form should be configured with RuleForm in Advance tab. Please check below url.

https://support.pega.com/question/elastic-search-data-class-not-indexing-new-records

@Anoop Krishna thanks for the info.

However we met another more urgent issue now, after upgraded, the case searching OOTB tool: D_pyWorkSearch, does not work at all.

Previously, it can return case list by keyword, now it always return nothing.

I manually do index for all our case type tables, not useful.

Could you kindly advise?

@MaxonL16591286 after doing the work class reindexing can you tell me what status it is displaying?

@MaxonL16591286 can you please check the logs if its showing any errors.

@Anoop Krishna

status all normal. Pls note there 10+ pages and I reindex all.

@Anoop Krishna

I did not find any entry to check log in above Searching section.

Do you mean checking Pega system log?

@MaxonL16591286 yes right, please check cluster one also. Also please check if search node is healthy. If all good please try below steps and check if it’s working fine.

https://support.pega.com/question/adding-column-custom-search-property-search-results-pyworksearchresults

As verified in diff env that before/after SRS upgraded, we are sure that it’s caused by SRS upgrade issue.

We have raised incident to Pega support team to follow up.

@MaxonL16591286 pega team will mention the cause of the issue after upgrade and the fix for it. Please mention that too here.