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 2019/04/24 12:05:00 UTC

[jira] [Updated] (METRON-1005) Create Decodable Row Key for Profiler

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

Nick Allen updated METRON-1005:
-------------------------------
    Fix Version/s:     (was: Next + 1)

> Create Decodable Row Key for Profiler
> -------------------------------------
>
>                 Key: METRON-1005
>                 URL: https://issues.apache.org/jira/browse/METRON-1005
>             Project: Metron
>          Issue Type: Improvement
>    Affects Versions: 0.3.0
>            Reporter: Nick Allen
>            Assignee: Nick Allen
>            Priority: Major
>
> To be able to answer the types of questions that I outlined in METRON-450, we need a row key that is decodable.  Right now there is no logic to decode a row key, nor is the existing row key easily decodable.  
> Once the row keys can be decoded, you could scan all of the row keys in the Profiler's HBase table, decode each of them and extract things like, the names of all your profiles, the names of entities within a profile, the period duration of a given profile.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)