[
https://issues.apache.org/jira/browse/METRON-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709410#comment-16709410
]
ASF GitHub Bot commented on METRON-1879:
----------------------------------------
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/1269
Refresh me on this - prior to this change, did we provide both a doc id and
a guid that were identical? And now with this change you would expect to see
guid != doc id (bc guid generated by Metron, doc id now generated by ES),
except where otherwise configured for backwards compatibility?
> Allow Elasticsearch to Auto-Generate the Document ID
> ----------------------------------------------------
>
> Key: METRON-1879
> URL: https://issues.apache.org/jira/browse/METRON-1879
> Project: Metron
> Issue Type: Sub-task
> Reporter: Nick Allen
> Assignee: Nick Allen
> Priority: Major
>
> The document ID should not be set so that Elasticsearch can auto-generate the
> document ID. This should significantly improve write performance.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
