You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "Ryan Merriman (JIRA)" <ji...@apache.org> on 2019/05/09 21:47:00 UTC
[jira] [Updated] (METRON-2109) Add option to use Metron GUID as the
id in Elasticsearch
[ https://issues.apache.org/jira/browse/METRON-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan Merriman updated METRON-2109:
----------------------------------
Description: [METRON-1879|https://github.com/apache/metron/pull/1269] changed the ElasticsearchWriter to let Elasticsearch auto-generate ids rather than using the Metron GUID. This has the potential to create duplicates when messages are replayed which might be undesirable for some users. We should make this configurable. (was: [METRON-1879|[https://github.com/apache/metron/pull/1269]] changed the ElasticsearchWriter to let Elasticsearch auto-generate ids rather than using the Metron GUID. This has the potential to create duplicates when messages are replayed which might be undesirable for some users. We should make this configurable.)
> Add option to use Metron GUID as the id in Elasticsearch
> --------------------------------------------------------
>
> Key: METRON-2109
> URL: https://issues.apache.org/jira/browse/METRON-2109
> Project: Metron
> Issue Type: Improvement
> Reporter: Ryan Merriman
> Priority: Major
>
> [METRON-1879|https://github.com/apache/metron/pull/1269] changed the ElasticsearchWriter to let Elasticsearch auto-generate ids rather than using the Metron GUID. This has the potential to create duplicates when messages are replayed which might be undesirable for some users. We should make this configurable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)