Work Item text search does not find right number of matches
![]()
It appears that we are not getting the same number of matches when we do a text search on work items after migrating from 1.0 to 1.0.1.1. We moved to a new machine during the migration. We did not copy the workitemindex folder, but ran repotools -rebuildTextIndices. However, we're seeing fewer number of matches in our 1.0.1.1 instance than we did with 1.0.
How can we fix this problem? Thanks. |
5 answers
![]()
kmunir wrote:
It appears that we are not getting the same number of matches when we Let me add a bit more detail, The server was moved to a different machine The first sign that something was wrong was when users entered search text in the "Quick search" widget and the results were missing workitems. Running the same search on the original machine got more hits. It was hoped that running the "-rebuildTextIndices" would resolve the problem but it did NOT. |
![]()
Alan wrote:
kmunir wrote: Yes, that is the right command to reindex all artifacts to support text searches again. It would be interesting to find out if those work items not in the index fail to be indexed for some reason. Work Items get indexed whenever saved. Maybe you could try saving such a work item (e.g. add a comment) and then run the search again to see if its picked up properly. Also, maybe something got logged when running the repotools, could you have a look? -- Benjamin Pasero Work Item & UI Commons Team |
![]()
Benjamin Pasero wrote:
Alan wrote: Running the search again after updating a workitem that *should be* in the query results (using full text) fixes the problem. On the weekend a rebuild was run with a *cleared* workitemindex directory. The rebuild ran without any errors in the rebuild log BUT I noticed that the Fulltext rebuild took 0ms. That can't be a good sign. We have about 800+ workitems (this is straight from the log) 2009-05-09 01:16:31,065 Running pre-rebuild index for "Fulltext"... |
![]()
Benjamin Pasero wrote:
Alan wrote: There is a rebuildIndices and a rebuildTextIndices We have only been running the TextIndices Should we run both? |
![]()
kmunir wrote:
It appears that we are not getting the same number of matches when we Problem resolved... The teamserver.properties had a relative directory for fulltext.indexLocation The server was running under WAS and therefore the workitemindex directory was in a different location relative to where the repotools command expected it. So when we ran the rebuildTextIndices it was against the wrong directory. We updated the teamserver.properties file to point to a fully qualified workitemindex directory and after running the rebuildTextIndices the search now works. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.