On Mon, Mar 20, 2017 at 12:55 AM, Adi Meller wrote:
> Hello.
> I need to move some (5-6) big (2 tera each) tables from hive to Phoenix
> every day.
>
> I have cdh 5.7 and install phoenix 4.7 thought parcel.
> I have 4 region server with 94gb physical memory And 32 cores each.
>
> 1. I created csv
Look at the fix versions on HBASE-17587 for a released or soon to be released
version containing the fix.
> On Mar 21, 2017, at 8:30 AM, James Taylor wrote:
>
> The bug is HBASE-17587.
> Thanks,
> James
>
>> On Tue, Mar 21, 2017 at 7:54 AM Mike Prendergast
>> wrote:
>> According to the link
Phoenix uses log4j to print out log messages to the console. You can
modify the log level in the referenced logj4.properties...
On Mon, Mar 20, 2017 at 2:50 AM, rohitrk.10 wrote:
> Hi,
>
> We did not find any other logs. We have added
> "-Dsun.security.krb5.debug=true", even then there is no much
Hello Mike,
This fix has been incorporated into EMR’s HBase offering so this issue will not
be present on EMR.
Thanks,
Zach
From: James Taylor
Reply-To: "user@phoenix.apache.org"
Date: Tuesday, March 21, 2017 at 8:30 AM
To: "user@phoenix.apache.org"
Subject: Re: Phoenix 4.9 on Hbase 1.3.0
T
The bug is HBASE-17587.
Thanks,
James
On Tue, Mar 21, 2017 at 7:54 AM Mike Prendergast
wrote:
> According to the link below, it seems that Phoenix 4.9 won't work with
> Hbase 1.3.0, and they are waiting for 1.3.1 for a bug fix. What is the
> specific bug mentioned here?
>
> AWS EMR 5.4.0 uses 4.
According to the link below, it seems that Phoenix 4.9 won't work with
Hbase 1.3.0, and they are waiting for 1.3.1 for a bug fix. What is the
specific bug mentioned here?
AWS EMR 5.4.0 uses 4.9 on 1.3.0, so I am trying to determine if the bug
will be a problem for our team. Thanks!
https://blogs.