[ https://issues.apache.org/jira/browse/METRON-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095924#comment-16095924 ]
ASF GitHub Bot commented on METRON-1005: ---------------------------------------- Github user mattf-horton commented on the issue: https://github.com/apache/metron/pull/622 Here's what I've got on decoding old rowkeys: https://gist.github.com/mattf-horton/8e685e373b1a3fa6aeec8ef8828be096 The format of the keys is `salt (4B) + profile name (?) + entity name (?) + groupvalues (?) + period (8B)` with most of it (all but the salt and period number) in the clear as human-readable strings. Deducing periodDuration has a nice arithmetic answer, I think. The NLP issues are of course harder. Enjoy the read, it's only two pages. > 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 > Fix For: Next + 1 > > > 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 (v6.4.14#64029)