In the Endeca Server cluster, the way to identify the host and port of the Endeca Server instance for loading data using Bulk Load Interface has changed.
In the previous release, to use the Bulk Load Interface, you had to specify the host and port of the machine on which the Endeca data store was running to the BulkIngester constructor of the Bulk Load Interface. If the data store was running in the Endeca Server cluster, this machine was the one on which the leader Dgraph node was running. Because the system administrator was responsible for configuring the leader node, this was the node whose host and port had to be configured for the Bulk Ingest Interface.
In this release, the initial allocation (and the subsequent appointment) of the leader node occur automatically in the Endeca Server cluster, for each data domain hosted in it. Therefore, before you can specify the host and port of the machine for loading data into the data domain with the Bulk Load Interface, you need to request this information from the Endeca Server cluster. Use the allocateBulkLoadPort operation of the Manage Web Service to obtain the host and port of the Endeca Server instance that is allowed to perform data loading operations for the data domain.