You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@metron.apache.org by "Nick Allen (JIRA)" <ji...@apache.org> on 2018/11/16 21:38:00 UTC

[jira] [Commented] (METRON-1801) Allow Customization of Elasticsearch Document ID

    [ https://issues.apache.org/jira/browse/METRON-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16690028#comment-16690028 ] 

Nick Allen commented on METRON-1801:
------------------------------------

This approach was abandoned.  See https://issues.apache.org/jira/browse/METRON-1879.

> 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)