[
https://issues.apache.org/jira/browse/METRON-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16308099#comment-16308099
]
ASF GitHub Bot commented on METRON-1005:
----------------------------------------
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/622
@nickwallen I haven't been following this discussion, but it seems like a
useful feature / enhancement that's been hanging out awhile after active
discussion petered out. What are the next steps here? Does this PR need
changes? Should the discussion be revived on the user lists? It doesn't seem
like there was any consensus on the approach, but again, I like this
enhancement a lot.
> 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)
