Rate limiting in Enterprise Search
Rate limiting of Enterprise Search can occur if too many of the same queries are made directly to Elasticsearch (ES) rather than effectively utilizing caching.
Ready to get started with WordPress VIP? Contact us
Showing page 14 of 17
Rate limiting of Enterprise Search can occur if too many of the same queries are made directly to Elasticsearch (ES) rather than effectively utilizing caching.
Indexing compiles a site's content and inserts it into an Elasticsearch (ES) index. Indexing can be triggered with a VIP-CLI command.
Enterprise Search features such as facets, related posts, terms, and more can be enabled per site with custom WP-CLI commands run with VIP-CLI.
Post meta is not indexed by default. If post meta is not explicitly defined in the allow list, it will not be indexed.
Similar to post types, any registered taxonomy that is public will be indexed by default.
Enterprise Search automatically indexes all public post types.
To fully enable Enterprise Search, the feature must be code-enabled then an Elasticsearch (ES) index for a site's content is created using CLI commands.
Plugins must be installed by adding them to the /plugins
directory of an application’s GitHub repository in order to be available for activation. Once installed, it is possible to activate the plugins in the WordPress Admin dashboard (WP Admin). However, it is recommend to code-activate plugins instead to gain greater control and consistency across all environments (e.g., production, non-production, and local development environments).
These instructions will demonstrate how to determine a DNS record's Time to Live using common command line tools.
The WP-CLI search-replace
command can be used to search and replace strings in a selection of database tables. This is useful for updating post content and options, especially when changing URLs for sites on a WordPress multisite.