[
https://issues.apache.org/jira/browse/METRON-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100379#comment-16100379
]
ASF GitHub Bot commented on METRON-1005:
----------------------------------------
Github user mattf-horton commented on the issue:
https://github.com/apache/metron/pull/622
@nickwallen brought up the issue of wildcard queries on our rowkeys. It
has always bothered me that we can't do wildcard queries on groups. If you
have, for example, a single groupBy based on day of week, that's just 7
possible values, and if you want them all you could just do 7 queries and
combine them. But if you have three groupBy's, and they have 7, 31, and 256
possible values, then to simulate a wildcard query you would have to do over
55,000 individual queries! Of course you would just do an hbase scan, but it
would require a full table scan to select the time range desired.
I propose that we re-order the rowkey elements to support prefix queries on
Profile and time range, with wildcarding for primarily groups, and secondarily
entities, ie:
\<salt\>\<magic\>\<profileHash\>\<period\>\<entity\>\<groups\>
So if I want the results for all rows in a time range regarding entity
"192.168.222.123" regardless of group, I can query it, and if I want all rows
in a time range regardless of entity value or group, I can query that too, as
efficiently as an ordinary time range query. What do you think?
> 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)
