Query profiles let you consistently point your search application at a static endpoint, but give you the flexibility to change the actual query pipeline being used (and optionally, the collection and/or configuration parameters for the query pipeline). For example, an e-commerce site might want to create a query pipeline to support a month-long promotion. After the query pipeline is configured, it can be easily enabled by changing the query profile in use by the front-end application to use the new pipeline. To run a query through a query profile, use the REST API as described below. For CRUD operations, you can use either the REST API or the Managed Fusion UI.

​
Rules Simulator query profile

ImportantRules Simulator is only available for Managed Fusion organizations that do not have a valid Predictive Merchandiser or Experience Optimizer license.
The Rules Simulator allows product owners to experiment with rules and other query rewrites in the COLLECTION_NAME_query_rewrite_staging collection before deploying them to the COLLECTION_NAME_query_rewrite collection. Each app has a COLLECTION_NAME_rules_simulator query profile, configured to use the COLLECTION_NAME_query_rewrite_staging collection for query rewrites instead of the COLLECTION_NAME_query_rewrite collection. This profile is created automatically whenever a new app is created. See Configure the Rules Simulator Query Profile for more information about configuration.
Each app has a _rules_simulator query profile, configured to use the _query_rewrite_staging collection for query rewrites instead of the _query_rewrite collection. This profile is created automatically whenever a new app is created.By default, this query profile points to your default query pipeline and collection. You can configure it to point to any pipeline or collection, for example when testing a new pipeline before it has been deployed.How to change the query pipeline, collection, and query parameters used by the _rules_simulator query profile
  1. Open the Fusion UI.
  2. Navigate to Querying > Query Profiles.
  3. Select the _rules_simulator query profile for your app. For example, if your app is called “Demo” then the name of the query profile is Demo_rules_simulator. rules_simulator query profile
  4. Modify the configuration as desired.
  5. Click Save.
LucidAcademyLucidworks offers free training to help you get started.The Course for Index and Query Profiles focuses on how index and query profiles operate, and how to configure and manage them:
Index and Query ProfilesPlay Button
Visit the LucidAcademy to see the full training catalog.

​
Query profiles in the REST API

  • Query Profiles API (/query-profiles)
    Create, read, update, and delete query profiles.
  • Query API (/query)
    Run a query through a query profile by specifying the profile ID and appending the request with a Solr query string, as in /api/query/<id>?<solrQuery>.

​
Query profiles in the UI

To configure query profiles, click Querying > Query Profiles.