[
https://issues.apache.org/jira/browse/METRON-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16646812#comment-16646812
]
ASF GitHub Bot commented on METRON-1801:
----------------------------------------
Github user merrimanr 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?
I spun this up in full dev and ran through all the testing instructions.
Everything worked as advertised. I think there are just a couple open
questions but this is pretty close in my opinion.
> Allow Customization of Elasticsearch Document ID
> ------------------------------------------------
>
> Key: METRON-1801
> URL: https://issues.apache.org/jira/browse/METRON-1801
> Project: Metron
> Issue Type: Sub-task
> Reporter: Nick Allen
> Assignee: Nick Allen
> Priority: Major
>
> The user should be able to customize the document ID that is set by the
> client when indexing documents into Elasticsearch. The user should be able
> to use the Metron GUID, define their own custom document ID, or choose to not
> have the document ID set by the client.
>
> This task covers Elasticsearch only. An additional task should be created to
> cover Solr.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
