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.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
