You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "Casey Stella (JIRA)" <ji...@apache.org> on 2017/01/26 22:16:24 UTC

[jira] [Updated] (METRON-556) Profiler - Refactor 'Group By' Calculation

     [ https://issues.apache.org/jira/browse/METRON-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Casey Stella updated METRON-556:
--------------------------------
    Fix Version/s:     (was: Next + 1)
                   0.3.1

> Profiler - Refactor 'Group By' Calculation
> ------------------------------------------
>
>                 Key: METRON-556
>                 URL: https://issues.apache.org/jira/browse/METRON-556
>             Project: Metron
>          Issue Type: Improvement
>    Affects Versions: 0.3.0
>            Reporter: Nick Allen
>            Assignee: Nick Allen
>             Fix For: 0.3.1
>
>
> Currently a Profile's 'group by' expression is calculated in the context of the HBaseBolt.  Specifically it is calculated in the ProfileHBaseMapper.  This mapper is run by the HBaseBolt to define how the Profile values stored in a tuple get written to HBase.    This can be refactored so that the 'group by' expression is calculated at the same time as the 'result' expression in the context of the ProfileBuilderBolt.  
> This has a few advantages.  It allows any errors encountered in executing the 'group by' expression to be contained within the ProfileBuilderBolt instance responsible for the profile/entity pair alone.  Any exceptions cannot impact the functioning of the rest of the Profiler.  This is also more consistent and simple as the HBaseBolt will receive everything that it needs, pre-calculated, in the form of a ProfileMeasurement object.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)