Solr index field types
A guide to the field types, parameters, and usage of HCL Commerce Solr index fields.
For an overview of the HCL Commerce Solr search implementation, see the Solr deployment and core organization reference. To see how these field types are applied across the product, category, and unstructured cores, see the Solr Product index schema and Solr Category index schema.
Note: The field types below are the custom HCL Commerce types and the standard
Solr types used across the HCL Commerce Solr cores. For the complete list
of Solr field types and parameters, refer to the Apache Solr field types
documentation.
Custom HCL Commerce field types
| Type Name | Parameters and Options | Usage | Description |
|---|---|---|---|
| wc_text_en | tokenization, English stemming, stop words, position gap (100) | searching | A field type for full-text search optimized for English. Values are tokenized and passed through an analyzer that applies English stemming and stop-word removal. A position increment gap of 100 prevents phrase queries from matching across field boundaries. Used for name, descriptions, and keyword content. |
| wc_keywordText | light tokenization, keyword-structure analysis | searching, faceting | A field type for keyword and phrase matching with light tokenization. The analysis maintains the keyword structure rather than breaking values into individual stemmed terms. Used for identifiers, faceting, and hierarchy fields. |
| wc_keywordTextLowerCase | tokenization, lowercase filter | searching, faceting | A field type for case-insensitive keyword matching. Values are lowercased and tokenized so that matching is not case sensitive. Used for normalized identifiers, SKUs, and part numbers. |
Standard Solr field types
| Type Name | Parameters and Options | Usage | Description |
|---|---|---|---|
| string | indexed, stored, docValues | filtering, sorting, exact match | A field type for exact-match values with no analysis. The value is indexed verbatim and is only matched by its exact value. Used for unique identifiers and status codes. |
| int, long, slong | indexed, stored, docValues | filtering, sorting | Numeric field types. Used for reference identifiers, counts, flags, and sequence values. |
| date | indexed, stored, docValues | filtering, sorting | A field type for date and time values in ISO 8601 format. Used for availability dates, publication dates, and index timestamps. |
Notes
- Field type options determine how a field behaves: indexed makes the field searchable in queries, stored makes the field value retrievable in results, tokenized means values are analyzed rather than treated as exact values, and multiValued allows a field to contain multiple values.
- Copy fields aggregate content from multiple source fields into a single searchable field. For example, name, shortDescription, keyword, and categoryname are copied into defaultSearch for broad text search.