-
Notifications
You must be signed in to change notification settings - Fork 470
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Unique Fields] : Unique Field calculation problem in customer instance #31262
Comments
On
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Parent Issue
Problem Statement
When enabling the
DOT_FEATURE_FLAG_DB_UNIQUE_FIELD_VALIDATION
feature flag in a specific customer environment, the process is taking a long time before failing with the following error in the log:Considering that the same initialization process works with smaller datasets, we believe that this error might be related to data inconsistencies or corruption. There are a few things we have in mind:
Steps to Reproduce
The issue was reported by the Enterprise Support Team, after enabling the Unique Validation via database, and restarting the customer's instance.
Acceptance Criteria
We need to improve the error handling and reporting of the process that loads unique field data in a dotCMS instance.
dotCMS Version
25.01.17, and latest main
Proposed Objective
Core Features
Proposed Priority
Priority 1 - Show Stopper
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
Slack threads:
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered: