I think cloudera has a phoenix parcel available to download and use. You can
google “cloudera phoenix support” and you should find a instruction about how
to connect to a cloudera phoenix repo and install parcel etc.
Yanlin
> On Jun 23, 2015, at 3:36 PM, Kevin Verhoeven
> wrote:
>
> I f
IRA when you have a chance.
> Thanks,
> James
>
> On Tue, Jun 16, 2015 at 2:03 PM, yanlin wang wrote:
>> Thanks James. My example is bad …
>>
>>
>>> On Jun 16, 2015, at 1:39 PM, James Taylor wrote:
>>>
>>> Hi Yanlin,
>>> The firs
mitation of derived tables (PHOENIX-2041).
>
> Thanks,
> James
>
> On Tue, Jun 16, 2015 at 11:48 AM, yanlin wang wrote:
>> Hi James,
>>
>> I figured the error i got was not the phoenix version issue and here is the
>> test case you can reproduc
SQLState: 42I01
ErrorCode: 1001
Thx
Yanlin
> On Jun 16, 2015, at 10:57 AM, yanlin wang wrote:
>
> Hi James,
>
> Thanks for the info. I am using cloudera distribution
> CLABS_PHOENIX-4.3.0-1.clabs_phoenix1.0.0.p0.78 that can be the issue. I will
> try to play with other
| COL1 |
> +--+
> | b|
> +------+
> 1 row selected (0.031 seconds)
>
>
> On Mon, Jun 15, 2015 at 6:07 PM, yanlin wang wrote:
>> Hi,
>>
>> I am trying to setup phoenix working with some BI
Hi,
I am trying to setup phoenix working with some BI solution. The issue i have is
that given a tool generated query like this -> select fact.col1 from (select
col1 from t1) as fact, phoenix will confuse the table alias with column family.
Any suggestion?
Thx
Yanlin
>>> On Sun, Jun 14, 2015 at 5:59 PM, James Taylor
>>> wrote:
>>> Good idea. Please file a JIRA. Would be good to quantify the potential gain
>>> with and without FAST_DIFF encoding (the default) and/or Snappy compression.
>>>
>>>
>&
PM, James Taylor wrote:
>
> Good idea. Please file a JIRA. Would be good to quantify the potential gain
> with and without FAST_DIFF encoding (the default) and/or Snappy compression.
>
> On Sunday, June 14, 2015, yanlin wang <mailto:wangyan...@gmail.com>> wrote:
> Than
e because using short column names is
> a common thing in HBase.
>
> Thanks,
> Anil Gupta
>
> On Sun, Jun 14, 2015 at 12:19 PM, yanlin wang <mailto:wangyan...@gmail.com>> wrote:
> Hi,
>
> Usually one method to reduce IO in hbase is to reduce the size of col
Hi,
Usually one method to reduce IO in hbase is to reduce the size of column
qualifier’s length and use a dictionary to map the application column name to
the actual column qualifier. Kiji schema project is doing exactly that. Is
there any column name encoding support in Phoenix? if no, any pla
10 matches
Mail list logo
