[MNT-13384] Failure to create indexes for metadata query indexes is ignored Created: 17-Feb-15 Updated: 06-Nov-15 Resolved: 03-Jun-15
|Project:||Service Packs and Hot Fixes|
|Type:||Service Pack Request|
|Reporter:||Luis Colorado [X] (Inactive)||Assignee:||Closed Bugs (Inactive)|
|Remaining Estimate:||0 minutes|
|Time Spent:||2 days, 1 hour|
|Original Estimate:||Not Specified|
Plain vanilla Alfresco
Technical Description of the issue. If the creation of the required indexes for metadata queries fail, metadata queries will be extremely slow or will timeout, and the root cause would be difficult to detect.
During an upgrade, the failure to create the index is being reported as a warning, but buried under a patch temporary report. Here is the warning in the log:
2015-02-12 13:53:58,860 WARN [ domain.schema.SchemaBootstrap ] [ localhost-startStop-1 ] Schema validation found 1 potential problems, results written to: J:\alf424\tomcat\temp\Alfresco\Alfresco-AlfrescoOracle9Dialect-Validation-Post-Upgrade-alf_-3227840462705701270.txt
The temporary file contains the actual error. It could have something like the following:
Error report -
It is not possible for users to discern that the message should be linked to the performance problem that is affecting them.
Although strictly speaking Alfresco is reporting the error, it is difficult to interpret. A high level of knowledge of the database and indexes is required in order to understand the implications of the error buried in the db diagnostic file. We cannot expect users to make sense out of that error.
If the upgrade script failed, and the metadata queries were enabled, maybe we should not let Alfresco to start at all.
Customers Description of the problem.
Steps to reproduce
1. Created a 4.1.9 environment.
If the indexes were not created, and system.metadata-query-indexes.ignored=false, then application of the patch should be considered as failed, and the bootstrap should be stopped.
Alfresco starts without problems.
Analysis to date
Customer business impact / priority / urgency. Customer has already diagnosed and solved the problem manually. However, this issue could be difficult to detect for users upgrading to version 4.2 and willing to take advantage of metadata queries.
Ideal Fix Version. 4.2.N