You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Gabriel Reid (JIRA)" <ji...@apache.org> on 2014/03/16 08:19:08 UTC

[jira] [Resolved] (PHOENIX-389) Complex Qualifiers

     [ https://issues.apache.org/jira/browse/PHOENIX-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gabriel Reid resolved PHOENIX-389.
----------------------------------

    Resolution: Fixed

Bulk resolve of closed issues imported from GitHub. This status was reached by first re-opening all closed imported issues and then resolving them in bulk.

> Complex Qualifiers
> ------------------
>
>                 Key: PHOENIX-389
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-389
>             Project: Phoenix
>          Issue Type: Task
>            Reporter: maillard
>
> Another strength of hbase is to be able to use column names as information value as well.
> Complex column qualifiers are a frequent use case.
> So say I wanted to keep track of clics and impressions of adds in different postions of a web page for every day.
> I could say my colum name would be "positionName"&click or "positionName"&impression and the value would be numeric.
> It would be nice to ba able to query all my columns with a given pattern say select cf."positionName"* would bring me back the clicks and impressions of the particuler positionName.
> Does this make sense?
> Sorry for the repost I actually  thought this deserved a particuler issue.



--
This message was sent by Atlassian JIRA
(v6.2#6252)