HCL Commerce Version 9.1.10.0 or later

Tutorial: Ingesting custom database fields into Elasticsearch

Optional custom database fields such as FIELD1, FIELD2, etc. in the HCL Commerce catalog data model are often used in Ingest customization. These fields help reduce the need for custom extension tables. This tutorial shows you how to use them with the Ingest service.

In this tutorial you create a custom field connector using the Ingest service API. You configure the connector/pipeline progress groups and processors in NiFi, defining your ingest SQL and your Elasticsearch schema mapping, and determining where you intend to include your field(s) in the dataflow processing.