1.3.  PARTsolutions
1.3.8.  Index administration
Prev  Next

1.3.8.  Index administration

1.3.8.1. New JavaLucene index
1.3.8.2. Function overview
1.3.8.3. User interface of the Index administration at a glance
1.3.8.4. Meaning of icons and display in the index tree
1.3.8.5. Docking "Index update"
1.3.8.6. Context menus
1.3.8.6.1. Properties
1.3.8.6.2. Display index
1.3.8.6.3. Full-text search index
1.3.8.6.4. LinkDB search index
1.3.8.6.5. Manage index
1.3.8.6.5.1. V12 functionality - Preconditions
1.3.8.6.5.2. Call dialog "Manage index"
1.3.8.6.5.3. Index tree in the "Manage index" dialog
1.3.8.6.5.4. Index generation in the dialog "Manage index"
1.3.8.6.5.5. Table mode / LinkDB mode in dialog "Manage index"
1.3.8.6.5.6. Tabbed pages in "Manage index" dialog
1.3.8.6.5.6.1. Statistic
1.3.8.6.5.6.2. Geo index
1.3.8.6.5.6.3. Full-text index / LinkDB index
1.3.8.6.5.6.4. Explanation of result
1.3.8.6.5.6.5. Search Variables
1.3.8.6.5.6.6. Index generation
1.3.8.6.5.6.7. Settings
1.3.8.6.6. Geometrical search index
1.3.8.6.6.1. Dependencies between software update and update of Geometrical search index
1.3.8.6.6.2. Create partition map
1.3.8.6.7. Check link index
1.3.8.6.8. Add to favorites:
1.3.8.6.9. Cleanup versions
1.3.8.6.10. Create CIP-File
1.3.8.6.11. Suppress appearance / Restore appearance
1.3.8.6.12. Sort catalogs
1.3.8.6.13. Uninstall catalog
1.3.8.6.14. Remove
1.3.8.6.15. Update Full-text search index (and Geometrical search index) for finding topological values via Full-text search
1.3.8.6.16. Geometrical search index for Partial search
1.3.8.7. Index administration at the client computer and/or in user mode
1.3.8.7.1. Display in user mode
1.3.8.7.2. Restricted configuration options and commands
1.3.8.8. Index administration - Background information
1.3.8.9. Repair geo, topo or partial index

PARTadmin -> Category PARTsolutions -> Index administration

PARTadmin -> Category PARTsolutions -> Index administration

Preconditions

With V12, the index management is built on a new JavaLucene index, which is activated in following key under $CADENAS_SETUP/partsol.cfg.

[INDEX:LUCENE]
JavaLucene=1

Even if there is a complete V11 index, for V12, the Full-text index has to be completely regenerated and furthermore also the LinkDB index, because it also uses the new index type. The Geo index is correctly displayed immediately, however, it should also be regenerated, because there are new algorithms which will improve the search options.

The figures shows the situation after switching to the new index. In this example, only for "ANSI / ASME", "commonpool" and "Assistent" catalog, the new index has been created.

The figures shows the situation after switching to the new index. In this example, only for "ANSI / ASME", "commonpool" and "Assistent" catalog, the new index has been created.

Prev Up Next
1.3.7.  Document types  Home 1.3.8.1. New JavaLucene index