Query Pipelines

​

Creating a Collection

1. From within an app, click Collections > Collections Manager.
2. At the upper right of the panel, click New.
3. Enter a Collection name. This name cannot be changed later.
4. To create the collection in the default Solr cluster and with other default settings, click Save Collection.

​

Creating a Collection with Advanced Options

1. From within an app, click Collections > Collections Manager.
2. At the upper right of the panel, click New.
3. Enter a Collection name. This name cannot be changed later.
4. Click Advanced.
5. Configure advanced options. The options are described below.
6. Click Save Collection.

​

Solr Cluster

​

Solr Cluster Layout

​

Solr Collection Import

​

Time Series Partitioning

​

Configuring Collections

• Configure a profile in Indexing > Indexing Profiles or Querying > Query Profiles.
• View reports about your collection’s activity in Analytics > Dashboards.

​

Collections Manager

​

Disable search logs

1. Hover over your collection name until the gear icon appears at the end of the line.
2. Click the gear icon.
3. Click Disable Search Logs.
4. On the confirmation screen, click Disable Search Logs.

• Fusion 5.x. Dashboards
• Fusion 4.x. Dashboards

​

Disable signals

1. Hover over your collection name until the gear icon appears at the end of the line.
2. Click the gear icon.
3. Click Disable Signals.
4. On the confirmation screen, click Disable Signals.

​

Hard commit a collection

1. Hover over your collection name until the gear icon appears at the end of the line.
2. Click the gear icon.
3. Click Hard Commit Collection.
4. On the confirmation screen, click Hard Commit Collection.

​

Datasources

​

Stopwords

1. Click the name of the text file you wish to edit.
2. Add a new word on a new line.
3. When you are done with your changes, click Save.

1. Click System > Import Fusion Objects.
2. Choose the file to upload.
3. Click Import >>.

• Fusion 5.x. stopwords
• Fusion 4.x. stopwords

​

Synonyms

• Fusion 5.x. synonyms
• Fusion 4.x. synonyms

1. From the Synonyms page, click Import and Save. A dialog box opens.
2. Choose the file to import.

• Enter new synonym definitions one per line.
  • To enter a string of terms that expand on the terms the user entered, enter the terms separated by commas, like Television, TV.
  • To enter a term that should be mapped to another term, enter the terms separated by an equal sign then a right angle bracket, =>, like i-pod=>ipod.
• Remove a line by clicking the x at the end of the line.
• Once you are finished with edits, click Save.

​

Profiles

• Fusion 5.x.
  • Index Profiles
  • Query Profiles
• Fusion 4.x.
  • Index Profiles
  • Query Profiles

​

Learn more

1. In Fusion UI, navigate to Indexing > Index Pipelines (for index pipelines) or Querying > Query Pipelines (for query pipelines).
2. Click Add a new pipeline stage.
3. Select Logging from the Troubleshooting section.
4. In the Label field, enter a descriptive name (for example, “Debug After Vectorize”).
5. Set the detailed property to true to print the full Request or PipelineDocument object.
6. Place the Logging stage after the stage you want to debug.
7. Click Save.
8. Run your pipeline and check the appropriate log file for your pipeline type:
   • Query pipelines: https://FUSION_HOST/var/log/api/api.log
   • Index pipelines: https://FUSION_HOST/var/log/api/fusion-indexing.log

1. Add a JavaScript stage to your pipeline.
2. Use the ctx variable to inspect context data:
   Copy

   function (request, response, ctx) {
     // View all context variables
     logger.info("Context: " + JSON.stringify(ctx));
   
     // Check specific variable (for example, vector from LWAI stage)
     if(ctx.get('vector') !== null) {
       logger.info("Vector: " + ctx.get('vector'));
     }
   }
   
3. Check logs at https://FUSION_HOST/var/log/api/api.log.

1. Navigate to Querying > Query Workbench.
2. Enter a test query and click Search.
3. Click the Debug tab. The debug view displays the following information:
   • Request parameters
   • Pipeline stage execution details
   • Response data including responseHeader and debug.explain
4. Switch to View As: JSON to see the full response structure.

1. In Fusion UI, navigate to your pipeline (Index or Query).
2. Click the LWAI stage you want to configure (for example, LWAI Vectorize Field or LWAI Vectorize Query).
3. Locate the Fail on Error checkbox at the bottom of the stage configuration.
4. Select the checkbox to enable any of the following behaviors:
   • Stop pipeline processing and throw an exception on errors
   • Get immediate feedback when LWAI models fail or are misconfigured
   • Guarantee data quality by preventing indexing of documents without vectors

6. Click Save.

1. Trigger an intentional error (for example, use an invalid model name or account).
2. Verify that the pipeline fails (when Fail on Error is enabled) or continues (when Fail on Error is disabled).
3. Review logs at https://FUSION_HOST/var/log/api/api.log for error messages.