[Unique Fields] : Avoid validation when Unique Field values have not changed
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by tracing the Contentlet update flow and the Unique Fields recalculation process, comparing the Elasticsearch Strategy with the Database Strategy. Verify how unchanged and changed Unique Field values are detected; done means recalculation is not triggered for unchanged values while updates to those values still trigger it.
Written by the indexing model from the issue text.
Description
Parent Issue
- #29459
Task
When updating a Contentlet with one or more Unique Fields, we're always triggering the recalculation process on their values, even when they've not changed at all. This is not a big deal when using the Elasticsearch Strategy; however, it might not be a great idea when using the Database Strategy.
We need to be able to detect whether those values have changed or not, so we don't kick off the re-generation process when is not required.
Proposed Objective
Core Features
Proposed Priority
Priority 2 - Important
Acceptance Criteria
The recalculation process must not be kicked off when Unique Fields haven't been updated.
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
Unless we log a message, the only way for QA to figure out when the recalculation process was not triggered is to notice that updating a Contentlet with an unchanged Unique Field takes less time compared to the moment it was created.
Sub-Tasks & Estimates
No response
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotCMS/core
-
dotCMS : Build Team : Falcon Type : Task
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
OKR : Customer Support Team : Maintenance
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Team : Modernization
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
dotCMS : Workflow Team : Cloud Eng
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
-
Team : Maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
objectionary/hone-maven-plugin#1061 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
spring-projects/spring-modulith#1895 ·