Github user mraliagha commented on the issue:
https://github.com/apache/metron/pull/1218
> @mraliagha, that's a good suggestion. I believe we can functionally
achieve that be creating a custom id field in the format you suggest (with a
Stellar field transform) and set that field to be the ES id with the Ambari
property exposed in this PR. Do you feel it's worth documenting as an
optimization?
Yes, I think it is worth documenting as people can easily create serious
issues with Lucene based indexers by messing with ID. It can give users an
understanding of where it is safe to play with the ID and what the
recommendations are. I see if I can find any articles to share it as a part of
the manual.
---
