phoenix table/view such that query is always optimized.
Thanks in advance.
--
Regards,
Nishant Patel
,
Nishant
On Jun 12, 2015 4:55 AM, "James Taylor" 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
thout 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
> wrote:
>
>> Thanks James for your response.
>>
>> Yes. Currently I have used | as seperato
ists in where clause.
Thanks in advance.
Regards,
Nishant
On Sat, Jun 13, 2015 at 9:42 AM, Nishant Patel
wrote:
> 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, &
Hi,
I have create one table in Hbase. My hbase rowkey is combination of
multiple qualifier. I tried multiple things but nothing working as per my
expectation.
Case 1:
CREATE view IF NOT EXISTS EICIPERFORMANCE1 (
pk VARCHAR PRIMARY KEY,
"0"."CustomerName" VARCHAR,
"0"."LocationName" VARCHAR,
"0".
a byte[] in HBase. It has no column qualifier, so you
> wouldn't want to prefix those columns with any column family.
>
> Thanks,
> James
>
>
>
> On Sun, Jun 14, 2015 at 11:58 PM, Nishant Patel
> wrote:
> > Hi,
> >
> > I have create one table in
Hi,
I am trying to measure performance for Hbase and Phoenix.
I have generated 1000 records per day with combination of Column1 and
Column2.
I have created 5 different combination for column1 and column2 and created
data for 365 days. Total records I have generated 5 * 5 * 365 * 1000 =
9125000
a known
> row id. Am I wrong?
>
> One thing I am currently trying is to have indexed columns and "hot"
> content in one column family and let "cold" content in another family. It
> speed up scanning the table when you need to
>
> Le mer. 1 juil. 2015 à 06:
ry settings related to heap in hbase site.xml.
>>
>>
>>
>> Try naming the Column Qualifiers as single alphabets. They consume space
>> and takes more time to scan.
>>
>>
>>
>> Thanks
>>
>> Puneet.
>>
>>
>>
>