Invalidate Cache for Reindex

[jdotcms]

Parent Issue

No response

Problem Statement

When the policy sent is WAIT_FOR or FORCE; the system has to wait for the ES callback and them proceed to invalidate the cache.

Steps to Reproduce

There are some scenarios where a contentlet is being added,

• cache invalidated,
• collection requested before the content is already reindexed
  consequently the previous resulted collection has not the latest results since does not includes the content previously inserted

Acceptance Criteria

When a contentlet is being inserted including WAIT_FOR policy and do a search to a collection that should contain that new contentlet, after the addition, the contentlet should be already there.

dotCMS Version

23.05

Proposed Objective

Core Features

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

[zJaaal]

Passed InternalQA

We need to be sure that everytime we execute a Workflow on Pages Portlet, it only triggers one _search request per Workflow action

Notes for QA (Update)

The table can trigger more _search requests via events, so be sure that the _search we are testing is the one after this request /fire?inode={inode}&indexPolicy=WAIT_FOR. If you don't trigger any table event, we should only see one _search request after we fire the workflow action

Docker Image: [dotcms/dotcms:23.06_c2efd860_SNAPSHOT]

Screenshots

Screen.Recording.2023-06-07.at.10.27.48.AM.mov

[bryanboza]

Fixed, tested according to the provided video and it is working as expected on release-23.06 // Docker // FF