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."
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
