The index configuration for an application is associated with one or more import owners. An import owner provides a way of indicating that a portion of an application's configuration came from one source rather than another source. The name of the import owner typically identifies the source. For example, the name of an import owner could reflect a product catalog system.
In addition to any number of import owners, there is also one default
system owner. The
system owner is typically a developer who uses the
utility to augment index configuration and troubleshoot data issues as part of
update processing.
An import owner is typically created during the data import operation
using the Endeca Configuration Import API. The owner name is specified as
argument to the
ConfigRepositoryImporter constructor. For details, see
the
Endeca Configuration Import API Reference (Javadoc). You
can also create an import owner using the
-o option of the
set-config task. If the owner does not already exist,
the utility creates it.
The index configuration associated with an owner is removed using the
delete-owner task.
You can retrieve and examine index configuration for an owner using
the
get-config task and the
-o option. The task returns a JSON file with the index
configuration for the specified owner. If the file contains configuration from
multiple import owners, each import owner's configuration is represented as a
node within the file.
As described in
Setting the index configuration for an application ,
the
set-config task overwrites all previous index
configuration for a specified owner.
During baseline update processing, the Content Acquisition System merges and processes index configuration from all owners into a consolidated set of MDEX-compatible output files.
If multiple import owners modify the same attribute, the configuration
from the
system owner always overrides other import owners
during the merge process.
For example, suppose an import owner named
ATG creates an attribute that represents an Endeca
property. Then the
system owner updates the Endeca property to become an
Endeca dimension with
isAutogen set to
true. The merged configuration processes the attribute
and updates it to become an autogen dimension.
