You can transform and filter the enrichment data as it is loaded into HBase by
using Stellar extractor properties in the extractor configuration file. HCP supports
the following Stellar extractor properties:

Extractor Property

Description

Example

value_transform

Transforms fields defined in the columns mapping
with Stellar transformations. New keys introduced in the transform
are added to the key metadata.

"value_transform" : {
"domain" : "DOMAIN_REMOVE_TLD(domain)"

value_filter

Allows additional filtering with Stellar predicates based on
results from the value transformations. In the following example,
records whose domain property is empty after removing the TLD are
omitted.

"value_filter" : "LENGTH(domain) > 0",
"indicator_column" : "domain",

indicator_transform

Transforms the indicator column independent of the
value transformations. You can refer to the original indicator
value by using indicator as the variable name, as
shown in the following example. In addition, if you prefer to
piggyback your transformations, you can refer to the variable
domain, which allows your indicator transforms
to inherit transformations done to this value during the value
transformations.

Allows additional filtering with Stellar predicates based on
results from the value transformations. In the following example,
records whose indicator value is empty after removing the TLD are
omitted.

"indicator_filter" : "LENGTH(indicator) > 0",
"type" : "top_domains",

If you include all of the supported Stellar extractor properties in the extractor
configuration file, it will look similar to the following:

The extractor_config.json file is not stored anywhere by the
loader. This file is used once by the bulk loader to parse the enrichment dataset.
If you would like to keep a copy of this file, be sure to save a copy to another
location.