Understand the wiring under the hood
Following the naming conventions for the exported views and the text analytics modules is important.
When the Extraction application sees a value of email in the logtype field in the metadata.json, it goes through the following process.
- It looks for a compiled text analytics module with the name extractor_email in the custom JAQL module. When you build your new AQL, the compiled module will be automatically generated in this location. If it does not find one, then it will default to using extractor_generic.
- After publishing, deploying and running the customized application, you will see the CSV file with sample results. The header values in the CSV file will represent each field_type field from each view exported from the extractor_email module.
In the next article, you will see that each field_type field from each view exported from the extractor_email module is also available for faceted searching.