[
https://issues.apache.org/jira/browse/METRON-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095186#comment-16095186
]
ASF GitHub Bot commented on METRON-1005:
----------------------------------------
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/622
> I don't think our current row key is totally opaque, it just needs a
brute-force approach to figure out. Not suitable for interactive queries, but
would be acceptable for a one-time pass to build (or re-build) the ToC.
For reference, here is what the existing row key looks-like.
salt (16B) + profile name (?) + entity name (?) + groups (?) + time (8B)
How would you decode it? The salt and the time components have known
lengths; 16B and 8B respectively. Other than those two components, I don't
know how to distinguish the profile name, entity or groups. I can only decode
the row key if I already know either the profile name or the entity, which
defeats the advantages of being able to decode it.
> 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)
