Don't perform a content re-index when the METADATA index is upgraded

XMLWordPrintable

      Currently - when the METADATA index is upgraded, all of the head content will also be upgraded.

      We need to version the CONTENT index separately to the METADATA index and allow these to upgraded independently.

      From AtlasEye:

                                                                            
[atlassian]   metadata index took: 243s. 69778 changesets             
[bamboo]   metadata index took: 1207s. 68533 changesets               
[office-connector]   metadata index took: 150s.                       
[public]   metadata index took: 1475s. 7417 changesets                
[intsys]   metadata index took: 417s.                                 
[customware]   metadata index took: 8s.                               
[crowd]   metadata index took: 334s.                                  
[connector-intellij]   metadata index took: 173s.                     
[connector-eclipse]   metadata index took: 470s.                      
[connector-commons]   metadata index took: 28s.                       
[confluence-tools]   metadata index took: 2s.                         
[confluence-plugins]   metadata index took: 39s.                      
[confluence]   metadata index took: 1361s.                            
[jira]   metadata index took: 5903s.

      Content:

      [jira]   content index took: 2508s.
[public]   content index took: 2894s.
[bamboo]   content index took: 792s.
[confluence]   content index took: 2308s.

            Assignee:
            Unassigned
            Reporter:
            Nick
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: