Re: Revert PR #1218

I wouldn't call this complex. It is much easier to roll it back, so I can work on a proper fix without impacting the ongoing work of others. The existing Elasticsearch DAOs do not distinguish between document ID and Metron GUID as there was no need to before. So I need to disambiguate those

Re: Revert PR #1218

Would it not make more sense to fix the bug on the DAO side, and roll forward? I suspect what we need to do is add a stage in the update capability to configure the key field used for update, or worst case have a pre-query to lookup the internal ID in the relatively rare scenario where we escalate

Revert PR #1218

Hi Guys - @rmerriman tracked down some problems that were introduced with my PR #1218. Thanks to him for finding this. The change was intended to improve Elasticsearch write performance by allowing Elasticsearch to set its own document ID. The problem is that if you then go to the Alerts UI

Re: Invite to Slack Channel

Done On October 23, 2018 at 02:19:54, Mustafa Akmal (mustafa.ak...@abcdata.org) wrote: Hi, Please send me an invitation link to the slack channel aswell. Thanks! Mustafa Akmal Big Data Consultant mustafa.ak...@abcdata.org (mailto:mustafa.ak...@abcdata.org) +923365257705 (tel:+923365257705)

Re: HBaseDao and IndexDao abstraction

Hi All, I have got a solution for this using SHEW ( Simple HBase Enrichment Writer ) which is documented in confluence but not in metron current book documentation

Re: Invite to Slack Channel

Hi, Please send me an invitation link to the slack channel aswell. Thanks! Mustafa Akmal Big Data Consultant mustafa.ak...@abcdata.org (mailto:mustafa.ak...@abcdata.org) +923365257705 (tel:+923365257705) NUST (Technology Incubation Centre), Office No. 208, H-12, Islamabad, Pakistan