Field v/s Facet
- Shree Harsha Sridharamurthy
Fields are the data points for an item in the index. Every field is created corresponding to your data item’s attribute. Fields hold the data in Hawksearch hence field removal is usually not a frequent activity. Field also defines how Hawksearch should index the attribute (ref. Field Configuration: Best Practices - Field Types).
Facets are the options on the left hand - the navigation choices. It is also termed guided navigation, dimensions, refinements, etc. Internally, a facet is an aggregation of the search results based on the attributes.
Facets are created based on the fields. One facet can be created based out of one field. Facet is the visual representation of the field’s aggregation. This means that the users interact with the facets on the search results page and landing pages.
The end users see the facets on their search and landing pages but not the fields.
Making field changes usually requires a full index rebuild but making changes to facet (except creation) doesn’t need indexing.
Facet changes involve settings cache to be rebuilt which is by default 12.15 minutes (729 seconds)
There cannot be two facets for the same field.
You do not need to create a facet for every field you have defined. Facet is required only if there is a need to show the filters.
Facets are virtual i.e., deleting facet won’t delete the data however deleting the field will.
Facets are created based out of fields. The exception is those facets whose FacetFieldType is set to search - they can exist without the need of any fields being created.
Changing the facet’s Display Type (e.g., from CheckboxList to LinkList) or any other changes to the facet do not affect the field or the underlying data but changing the field type can influence facet display (ref. https://hawksearch.atlassian.net/wiki/spaces/HSKB/pages/1643872276/Facet+and+Field+Types#Possible-Configurations ).