I need some help understanding the reindexing process for archived data. The system runs the Job Scheduler pyPegaIndexer to index archived data but in certain situations if we have to delete the index data and reindex it. Then how it is going to work for the archived cases which are no longer in the table? Does pega maintain the link somewhere?
Does @Will Cho 's discussion Archive case and its associated artifacts help here?
@Chetan.Chaudhari please could you comment on this question?
Below is a GenAI-powered tool. All generated answers require validation against the provided references.
The pyPegaIndexer Job Scheduler indexes the copied files into Elasticsearch. The index keeps the association between an archived case and its archived file in the secondary storage. If there’s a need to delete and reindex data, the pyArchival_ReIndexer Job Scheduler can be used to fix corrupted Elasticsearch indexes. However, if the data has been deleted from the main table because it has been moved to the archive, Pega platform doesn’t realize this and thus Elastic Search would not know. Therefore, the index will contain the old data unless a full re-index is triggered from the search landing page for that class or set of classes. As of now, Pega cannot track changes to tables which are not going through Obj-Save / Obj-Delete methods for the index to be updated. You could potentially write triggers on these tables which upon delete could populate the pr_sys_queue_ftsindexer table with the pzInsKeys of the records deleted. But this will cause duplicate entries during normal deletes (obj-delete).
the case archiving process > Case archival jobs
Need to retrieve the archived cases from the DB using Search functionality
@ManashPratimCAs Marije wrote above, please check out the article - Archive case and its associated artifacts | Support Center
Going forward, i’d suggest to use this new job scheduler - pyPegaArchiverUsingPipeline - which takes care of all three jobs (copy, index, and purge) that were done separate previously. The new job scheduler is working fine for our client. We’re using 8.8,4 which is lower than your 8.8.5, thus should be relevant to you as well.
In addition, this recently updated Pega doc helped us a lot to implement the new JS successfully - Pegasystems Documentation.
@Will Choand @ManashPratimC , pyArchival_ReIndexer Job Scheduler is used to reindex archived cases. The job (and underlying activity) goes to the archive, picks up archived cases and indexes again the exposed properties in Embedded Elastic Search or SRS index. No duplicate indexes would be created.
Hope this answers your question.
cc: @MarijeSchillern