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
wrote:
> Please help on this.
> On Apr 15, 2016 11:47 PM, "Viswanathan J" > wrote:
>
>> Hi Anil,
>>
>> We were creating/storing
Please help on this.
On Apr 15, 2016 11:47 PM, "Viswanathan J"
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.
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" wrote:
> Hi Vishwanathan,
>
> Column qualif
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, Visw
Please help.
On Apr 15, 2016 2:18 AM, "Viswanathan J" 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\x0Bcolumn=fact:\x05, timestamp=1460666736042,
> value=\x02\x9E.\x8A
>
> Please help.
>
> --
Hi,
How to map the HBase column qualifier which is in byte type(highlighted
below) to the view in phoenix?
eg.,
\x00\x00\x00\x0Bcolumn=fact:\x05, timestamp=1460666736042,
value=\x02\x9E.\x8A
Please help.
--
Regards,
Viswa.J
