Calendar Bookings are not indexed properly when being recycled

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.0.X, Master
• Fix Version/s: 7.0.0 DXP FP37, 7.0.0 DXP SP7, 7.0.5 CE GA6, 7.0.X, 7.1.0 M1, 7.1.X, Master
• Component/s: Calendar
• Labels:
  • QA-AUTOMATION
  • backend_test
  • ee-ts
  • fw_code_review
  • fw_test_integration
  • liferay-digital-enterprise-70-sp7
  • liferay-fixpack-de-37-7010
• Branch Version/s:
  7.0.x
• Backported to Branch:
  Committed
• Story Points: 1
• Fix Priority: 3
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/54002

Note, this issue relies on LPS-76651 for testing via the search portlets.  Without LPS-76651, you must look at the index in Elastic in order to determine the results.

When removing a calendar booking and sending it to the recycle bin, the index is deleted instead of being updated.  This prevents searching through the recycle bin portlet's search bar for the calendar booking.

Steps to reproduce:

1. Add a calendar portlet to a site page
2. Create a new calendar booking with the title "Calendar Title" and the description "Calendar Description"
3. Search for "Title", "Description", or "Calendar" in the search portlet.  Notice each search returns the calendar booking.
4. Or, view the index within Elastic
5. Delete the calendar booking
6. Go to the recycle bin portlet and perform the same search.
7. Or, attempt to view the index within Elastic

 

Expected Results: the calendar booking is returned with each search, and the index is present

Actual Results: The calendar booking is not returned because the index is not present.

Reproduced in master 5d3a9a4c29aa1deb43a189b298f60b1a4195c0c8