You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@phoenix.apache.org by Viswanathan J <ja...@gmail.com> on 2016/04/14 22:48:47 UTC
Map the hbase column qualifier which is in byte type to phoenix table view
Hi,
How to map the HBase column qualifier which is in byte type(highlighted
below) to the view in phoenix?
eg.,
\x00\x00\x00\x0B column=fact:\x05, timestamp=1460666736042,
value=\x02\x9E.\x8A
Please help.
--
Regards,
Viswa.J
Re: Map the hbase column qualifier which is in byte type to phoenix
table view
Posted by James Taylor <ja...@apache.org>.
It is not currently possible to use a \0 byte value in column names (i.e. for
the cq), but please feel free to file a JIRA.
On Saturday, April 16, 2016, Viswanathan J <ja...@gmail.com>
wrote:
> Please help on this.
> On Apr 15, 2016 11:47 PM, "Viswanathan J" <jayamviswanathan@gmail.com
> <javascript:_e(%7B%7D,'cvml','jayamviswanathan@gmail.com');>> wrote:
>
>> Hi Anil,
>>
>> We were creating/storing the cq in bytes to segregate some information
>> based on that cq value. I'm unable to read or specify that cq type in view
>> creation for that table in Phoenix.
>>
>> Could you please help.
>> On Apr 15, 2016 6:13 PM, "anil gupta" <anilgupta84@gmail.com
>> <javascript:_e(%7B%7D,'cvml','anilgupta84@gmail.com');>> wrote:
>>
>>> Hi Vishwanathan,
>>>
>>> Column qualifiers(cq) in HBase are supposed to be utf-8 encoded string.
>>> Can you use utf-8 string as cq? Is there any particular reason to use
>>> non-string cq? I am not pretty sure that non-string cq's are supported by
>>> Phoenix.
>>>
>>> HTH,
>>> Anil Gupta
>>>
>>> On Thu, Apr 14, 2016 at 11:57 PM, Viswanathan J <
>>> jayamviswanathan@gmail.com
>>> <javascript:_e(%7B%7D,'cvml','jayamviswanathan@gmail.com');>> wrote:
>>>
>>>> Please help.
>>>> On Apr 15, 2016 2:18 AM, "Viswanathan J" <jayamviswanathan@gmail.com
>>>> <javascript:_e(%7B%7D,'cvml','jayamviswanathan@gmail.com');>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> How to map the HBase column qualifier which is in byte
>>>>> type(highlighted below) to the view in phoenix?
>>>>>
>>>>> eg.,
>>>>>
>>>>> \x00\x00\x00\x0B column=fact:\x05, timestamp=1460666736042,
>>>>> value=\x02\x9E.\x8A
>>>>>
>>>>> Please help.
>>>>>
>>>>> --
>>>>> Regards,
>>>>> Viswa.J
>>>>>
>>>>
>>>
>>>
>>> --
>>> Thanks & Regards,
>>> Anil Gupta
>>>
>>
Re: Map the hbase column qualifier which is in byte type to phoenix
table view
Posted by Viswanathan J <ja...@gmail.com>.
Please help on this.
On Apr 15, 2016 11:47 PM, "Viswanathan J" <ja...@gmail.com>
wrote:
> Hi Anil,
>
> We were creating/storing the cq in bytes to segregate some information
> based on that cq value. I'm unable to read or specify that cq type in view
> creation for that table in Phoenix.
>
> Could you please help.
> On Apr 15, 2016 6:13 PM, "anil gupta" <an...@gmail.com> wrote:
>
>> Hi Vishwanathan,
>>
>> Column qualifiers(cq) in HBase are supposed to be utf-8 encoded string.
>> Can you use utf-8 string as cq? Is there any particular reason to use
>> non-string cq? I am not pretty sure that non-string cq's are supported by
>> Phoenix.
>>
>> HTH,
>> Anil Gupta
>>
>> On Thu, Apr 14, 2016 at 11:57 PM, Viswanathan J <
>> jayamviswanathan@gmail.com> wrote:
>>
>>> Please help.
>>> On Apr 15, 2016 2:18 AM, "Viswanathan J" <ja...@gmail.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> How to map the HBase column qualifier which is in byte type(highlighted
>>>> below) to the view in phoenix?
>>>>
>>>> eg.,
>>>>
>>>> \x00\x00\x00\x0B column=fact:\x05, timestamp=1460666736042,
>>>> value=\x02\x9E.\x8A
>>>>
>>>> Please help.
>>>>
>>>> --
>>>> Regards,
>>>> Viswa.J
>>>>
>>>
>>
>>
>> --
>> Thanks & Regards,
>> Anil Gupta
>>
>
Re: Map the hbase column qualifier which is in byte type to phoenix
table view
Posted by Viswanathan J <ja...@gmail.com>.
Hi Anil,
We were creating/storing the cq in bytes to segregate some information
based on that cq value. I'm unable to read or specify that cq type in view
creation for that table in Phoenix.
Could you please help.
On Apr 15, 2016 6:13 PM, "anil gupta" <an...@gmail.com> wrote:
> Hi Vishwanathan,
>
> Column qualifiers(cq) in HBase are supposed to be utf-8 encoded string.
> Can you use utf-8 string as cq? Is there any particular reason to use
> non-string cq? I am not pretty sure that non-string cq's are supported by
> Phoenix.
>
> HTH,
> Anil Gupta
>
> On Thu, Apr 14, 2016 at 11:57 PM, Viswanathan J <
> jayamviswanathan@gmail.com> wrote:
>
>> Please help.
>> On Apr 15, 2016 2:18 AM, "Viswanathan J" <ja...@gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> How to map the HBase column qualifier which is in byte type(highlighted
>>> below) to the view in phoenix?
>>>
>>> eg.,
>>>
>>> \x00\x00\x00\x0B column=fact:\x05, timestamp=1460666736042,
>>> value=\x02\x9E.\x8A
>>>
>>> Please help.
>>>
>>> --
>>> Regards,
>>> Viswa.J
>>>
>>
>
>
> --
> Thanks & Regards,
> Anil Gupta
>
Re: Map the hbase column qualifier which is in byte type to phoenix
table view
Posted by anil gupta <an...@gmail.com>.
Hi Vishwanathan,
Column qualifiers(cq) in HBase are supposed to be utf-8 encoded string. Can
you use utf-8 string as cq? Is there any particular reason to use
non-string cq? I am not pretty sure that non-string cq's are supported by
Phoenix.
HTH,
Anil Gupta
On Thu, Apr 14, 2016 at 11:57 PM, Viswanathan J <ja...@gmail.com>
wrote:
> Please help.
> On Apr 15, 2016 2:18 AM, "Viswanathan J" <ja...@gmail.com>
> wrote:
>
>> Hi,
>>
>> How to map the HBase column qualifier which is in byte type(highlighted
>> below) to the view in phoenix?
>>
>> eg.,
>>
>> \x00\x00\x00\x0B column=fact:\x05, timestamp=1460666736042,
>> value=\x02\x9E.\x8A
>>
>> Please help.
>>
>> --
>> Regards,
>> Viswa.J
>>
>
--
Thanks & Regards,
Anil Gupta
Re: Map the hbase column qualifier which is in byte type to phoenix
table view
Posted by Viswanathan J <ja...@gmail.com>.
Please help.
On Apr 15, 2016 2:18 AM, "Viswanathan J" <ja...@gmail.com> wrote:
> Hi,
>
> How to map the HBase column qualifier which is in byte type(highlighted
> below) to the view in phoenix?
>
> eg.,
>
> \x00\x00\x00\x0B column=fact:\x05, timestamp=1460666736042,
> value=\x02\x9E.\x8A
>
> Please help.
>
> --
> Regards,
> Viswa.J
>