Sunile,
Starting hive 0.12, you can use prefixes to pull the columns corresponding
to the column families. So in your case as long as you have sensible
prefixes, for example for everything in july, if you use "july-DATE-speed",
then you can simply do something like WITH SERDEPROPERTIES
('hbase.columns.mapping' = ':key,columnfamily:july.*') and it will pull
everything automatically related to the july column. In that way you don't
have to define things statically.
Hope that helps.
[1] https://issues.apache.org/jira/browse/HIVE-3725
On Tue, Aug 4, 2015 at 9:06 PM, Manjee, Sunile <sunile.man...@teradata.com>
wrote:
>
> I would appreciate any assistance.
>
> Hive forces me to predefine column mappings : WITH SERDEPROPERTIES
> ('hbase.columns.mapping' = ':key,columnfamily:july8-speed')
>
> I need to create columns in hbase based on dates (which are values in my
> source) and append some other field like measurement. This will then make
> up my column name i.e. July8-speed. Predefining these seem senseless as I
> do not know which dates and/or measurements I will get from source data.
> Hive forces me to create a static mapping like I have shown above.
>
> Any assistance or insights would be appreciated.
>
--
Swarnim
