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 Fusion UI.
Rules Simulator query profile
|Rules Simulator is only available for Fusion 5.x.x 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
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.
Query profiles in the REST API
Query Profiles API (
Create, read, update, and delete query profiles.
Query API (
Run a query through a query profile by specifying the profile ID and appending the request with a Solr query string, as in
Query profiles in the UI
Query profiles are configured at Querying > Query Profiles.