[
https://issues.apache.org/jira/browse/METRON-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100356#comment-16100356
]
ASF GitHub Bot commented on METRON-1005:
----------------------------------------
Github user mattf-horton commented on the issue:
https://github.com/apache/metron/pull/622
@cestella , tl;dr: The discussion of serial numbers is a distraction.
Let's just use the profileHash and forget the serial number. It was a
micro-optimization.
Answer to your question: Two cases:
- If you have the profileHash, then you can look up the Profile using an
hbase wildcard query for rowkey \<profileHash\>\* , and since the profileHash
is unique, it will be essentially as efficient as using the full rowkey.
- If you are trying to decode a rowkey and only have the serial number then
I stated some assumptions: "The expectation is that we will seldom (almost
never) need to reference back to the Profile specification, and the total usage
of Profile specs will be human-scale finite, **so it is okay to "scan" the
ProfileSpecs table to find the full Profile spec referenced by a profileSN.**
If this is not true, use the full hash as both the rowkey in the PeriodSpecs
table, and as the reference element in the Profile rowkeys."
> 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)
