Yes. Will try same thing. If value is not there it is including null byte. Let me try with all these changes.
Thanks, Nishant On Jun 12, 2015 12:23 PM, "James Taylor" <[email protected]> wrote: > If use a zero byte instead of a |, then you can create your view with a > four column primary key without any issues. If a value is not present, make > sure to still include the null byte separator. > Thanks, > James > > On Thursday, June 11, 2015, Nishant Patel <[email protected]> > wrote: > >> Thanks James for your response. >> >> Yes. Currently I have used | as seperator. >> >> I think phoenix does not support to use custom seperator. I am planning >> to use one byte as seperator which phoenix use when you load through >> phoenix. >> >> All the variables are variable length and they are strings. >> >> Thanks, >> Nishant >> On Jun 12, 2015 4:55 AM, "James Taylor" <[email protected]> wrote: >> >>> Hi Nishant, >>> So your row key has the '|' embedded in the row key as a separator >>> character? Are the qualifiers fixed length or variable length? Are >>> they strings? >>> Thanks, >>> James >>> >>> On Wed, Jun 10, 2015 at 11:48 PM, Nishant Patel >>> <[email protected]> wrote: >>> > Hi All, >>> > >>> > I have hbase table where rowkey is composite key of 4 columns. >>> > >>> > Rowkey Example: >>> > >>> > qualifier1|qualifier2|qualifier3|qualifier4 >>> > >>> > I want to create phoenix table mapping this hbase table. I always >>> receive >>> > qualifier1, qualifier2 and qualifier3 as filter condition in query. >>> > >>> > How can I map phoenix table/view such that query is always optimized. >>> > >>> > Thanks in advance. >>> > >>> > -- >>> > Regards, >>> > Nishant Patel >>> > >>> >>
