I don't understand all the different repotools indexing commands
5 answers
Use repotools -rebuildTextIndices when you have one of the following symptoms:
You run a quick search (the edit box in the lower left hand side of the thick client, or upper right side of the web client) for a RM requirement, and you don't get the result you expected. The error often will reference Lucene.
Could we also have some inputs on the functionality of -compacttdb --Compact the RDF indexes too on this very comment?
If the reindex is reducing the size of the indices to half and so does -compacttd, what is it that this command does? Is there any specific switch with -verifyJFSIndexes that could prompt the admins to opt for a compacttdb?
Comments
The -verifyJFSIndexes command reads the indices into Jena Triple store data structures. From there the data structures are checked to see if they are internally consistent. That is that the index.properties file in the index matches the actual index files, that the data structures contain non-empty data, etc. The extended command looks for more extensively for issues.
If you find an issue with verifyJFSIndexes, you should reindex (repotools<cmd> -reindex all) . The tool makes this suggestion.
The -compactdb option changes the representation of the indices on disk, but doesn't affect their underlying value. Data is sometimes stored in journals, lists of commands to apply to the index data, as opposed to the actual data that makes up the index. If the journal contains a list of commands that was committed, it can be played back up to the commit point. This reduces the total index size.
1 vote
Hi Rosa,
- Part 1: Query, Search and indexing technologies in CLM
- Part 2: Indices storage and management: Backup, recovery and recreation