The Indexing Queue is a new concept of indexing content in TYPO3. While the already known frontend indexing process might be enough for many cases, the Indexing Queue provides quite some advantages.
- Easy Setup: The Index Queue comes preconfigured for pages, tt_news, and tt_address. Additional tables can be configured through TypoScript defining database fields to Solr schema field mappings. Each table can be enabled or disabled for indexing individually.
- Easy and complete page indexing: The Indexing Queue Page Indexer automatically detects all the frontend user groups used on a page and indexes the page with each found group's access rights. The page indexer also automatically detects whether translations exist for a page and indexes those translations, too. In combination all translations are also indexed with each group access right.
- Frontend groups access restrictions are handled more granular as they are detected down to even content element or single record level, compared to page level only with regular frontend indexing.
- Faster indexing of custom record types as in most cases no specialized indexers need to be developed anymore. Like with pages, indexing custom records is as easy as configuring a mapping with TypoScript. Custom indexers can still be used by defining them in TypoScript. The Index Queue Worker Task will then use the specified indexer.
Extensions can also use the Indexing Queue API to add new records for indexing or mark them as needing reindexing. This usually shouldn't be necessary though.
- Near instant page and record indexing. Changes on all records in TYPO3 are tracked. When a change on a record type enabled for Indexing Queue indexing is detected the changed record is added to the Indexing Queue for new records or marked for reindexing for updated records. A scheduler Index Queue Worker Task then takes care of indexing the changed pages and records. Depending on the amount and frequency of changes the scheduler task can be configured to run on a flexible schedule up to every minute. Thus the index can be updated faster than compared to frontend indexing.
- Workspace handling (not implemented yet). Due to the tight integration with TYPO3 workspace swap and publish events can be monitored and new pages can be indexed.