-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Component/s: Search - Automation and Indexing
-
Severity 2 - Major
Issue Summary
This is part of a PIR action item for HOT-119118.
In the HOT, the overwriting of last modification date on content trash broke some V2 APIs, affecting ecosystem customers. Reindexing a content when it is deleted is an important step of the reindexing process. Update all consumers of the deletion date to use `deleted-at` in the contentproperties table.
deleted-at PR
Steps to Reproduce
- Delete a piece of content, make sure `use_content_property_for_trashed_last_mod_date` is on (it's fully rolled out for all tenants now)
- Observe in contentproperties table that `deleted-at` shows the deletion date, not content.lastmoddate
Expected Results
Content lastmoddate should not change on deletion and deleted-at cp should be added on deletion
Actual Results
(ignore this part)
The below exception is thrown in the xxxxxxx.log file:
...
Workaround
(ignore this part)
- PIR - High Priority Action
-
PIR-26595 Loading...