[
https://issues.apache.org/jira/browse/METRON-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16060278#comment-16060278
]
ASF GitHub Bot commented on METRON-1005:
----------------------------------------
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/622
I strongly vote that you move these changes to a new RowKeyBuilder and keep
the old one default until a major release. The sad thing is, I don't think
there *is* a way to migrate the old data, so we're kinda screwed here in terms
of backwards compatibility. I definitely agree that we should move to a
profiler row key that is decodable, though, so it's very good work @nickwallen .
> 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)
