[GitHub] metron issue #1269: METRON-1879 Allow Elasticsearch to Auto-Generate the Doc...

2018-12-05 Thread nickwallen
Github user nickwallen commented on the issue: https://github.com/apache/metron/pull/1269 Prior to this change we use the Metron-generated GUID as the documentID. They were always the same. There were various places in the code where the name `guid`, `docID`, or `id` were used that

[GitHub] metron issue #1269: METRON-1879 Allow Elasticsearch to Auto-Generate the Doc...

2018-12-04 Thread mmiklavc
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,

[GitHub] metron issue #1269: METRON-1879 Allow Elasticsearch to Auto-Generate the Doc...

2018-11-19 Thread nickwallen
Github user nickwallen commented on the issue: https://github.com/apache/metron/pull/1269 This issue has been fixed. ---

[GitHub] metron issue #1269: METRON-1879 Allow Elasticsearch to Auto-Generate the Doc...

2018-11-19 Thread nickwallen
Github user nickwallen commented on the issue: https://github.com/apache/metron/pull/1269 I was doing some final testing and noticed that the 'guid' field for metaalerts is showing the document ID, rather than the guid. I need to fix the presentation of metaalerts in the UI.