S3 template should choose a distinct elastic search index name for each feed

Description

This problem is due to using a constant for the index name. See `integrations/nifi/nifi-nar-bundles/nifi-core-bundle/nifi-core-processors/src/main/java/com/thinkbiganalytics/nifi/v2/ingest/CreateElasticsearchBackedHiveTable.java:137`

The problem is that an ES index will write field type information to the index. One feeds field by "nameA;type B" may need to be a field of "nameA:typeC" in another feed. Feeds with uniquely named fields should not have an issue.

Example of field defintion in the index:

Assignee

Tim Harsch

Reporter

Tim Harsch

Labels

Reviewer

None

Epic Link

Components

Priority

Medium
Configure