Understanding Changes to Your HawkSearch Index: What to Do Next
When you make changes to your HawkSearch index using the Dashboard, it's essential to understand the steps required for these changes to take effect. While most production environments automate these processes, sandbox environments might require manual intervention. Additionally, sandbox environments differ from production environments, so some changes may take a few minutes to apply.
The table below provides details on the type of change you made, what you need to do next, and how long it takes for the change to take effect.
Note
You may notice a yellow message in the workbench at the top of some pages. This is intended to let the user know that a new index will be required before the change takes effect. Generally, the functional areas under Merchandising do not need a new index, while the functional areas under Keyword Search do need a new index.
| Category | Section | Changes Made | Require Full Index Rebuild | Time for Change to Take Effect |
|---|---|---|---|---|
| Data Configuration | Field | Created new fields | Yes | Changes are visible immediately after the full index rebuild, which takes roughly 10 minutes. |
| Updated fields | Yes | Changes are visible immediately after the full index rebuild, which takes roughly 10 minutes. | ||
| Deleted fields | Yes | Changes are visible immediately after the full index rebuild, which takes roughly 10 minutes. | ||
| Facet | Created new facets | Yes | Changes are visible immediately after the full index rebuild, which takes roughly 10 minutes. | |
| Updated fields | No | Changes are visible after the cache internal that can last up to 10-12 minutes. | ||
| Deleted fields | Yes | Changes are visible immediately after the full index rebuild, which takes roughly 10 minutes. | ||
| Merchandising | All | Create | No | Changes are visible after the cache internal that can last up to 10-12 minutes. |
| Update | No | Changes are visible after the cache internal that can last up to 10-12 minutes. | ||
| Delete | No | Changes are visible after the cache internal that can last up to 10-12 minutes. | ||
| Keyword Search | All | Create | Yes | Changes are visible immediately after the full index rebuild, which takes roughly 10 minutes. |
| Update | Yes | Changes are visible immediately after the full index rebuild, which takes roughly 10 minutes. | ||
| Delete | Yes | Changes are visible immediately after the full index rebuild, which takes roughly 10 minutes. | ||
| Index | N/A | New document inserted into the index | No Require Partial Index Rebuild | Changes are visible immediately after the partial index rebuild, which takes roughly 10 minutes |
Updated 9 months ago