Getting InsufficientMemoryException

Hi, I am trying to do a join of three tables usng the following query: *select c.c_first_name, ca.ca_city, cd.cd_education_status from CUSTOMER_3 c join CUSTOMER_DEMOGRAPHICS_1 cd on c.c_current_cdemo_sk = cd.cd_demo_sk join CUSTOMER_ADDRESS_1 ca on c.c_current_addr_sk = ca.ca_address_sk

phoenix4.1.0 does not work against HBase0.98.1

HBase version is 0.98.1-cdh5.1.0. I copied phoenix-core-4.1.0.jar and phoenix-4.1.0-server-hadoop2.jar into /opt/cloudera/parcels/CDH-5.1.0-1.cdh5.1.0.p0.53/lib/hbase/lib/ folder, and restarted HBase. I can see the following output in RegionServer log. /opt/cloudera/parcels/CDH-5.1.0-1.cdh5.1.0

anyone relying on hadoop1 still?

Hello, We've been planning on dropping hadoop1 support for our 4.x releases for a while now and it looks like it'll happen in 4.2. It'd be nice if we could do the same for our 3.x releases, as the more similar the two branches are, the less time it takes to keep them in sync. Is anyone out there s

Re: Salt key hash code logic

See SaltingUtil.getSaltingByte(byte[] value, int offset, int length, int bucketNum) On Mon, Sep 22, 2014 at 12:07 AM, Pariksheet Barapatre wrote: > Hello All, > > When I create phoenix table with salting how it calculates SALT hex. > > e.g. > CREATE TABLE TEST.PHOENIX_TEST > ( > TDM INTEGER NOT N

ILIKE

Hi, I have pushed a small patch to add ILIKE keyword to Phoenix. It's simple and available there: PHOENIX-1273 I'm pretty sure it is complete but it's a first draft for review. I still need to update the PhoenixSQL.g file. Thanks, JM

Re: Phoenix client maven dependencies

> HBase does some build magic so they can release against both hadoop1 and > hadoop2 by changing the version to include -hadoopX in the name so they can > different named artifacts for each when they release. So obviously, its > possible for us to do it too :) It's an ugly hack not magic. We ha

Re: Phoenix client maven dependencies

See PHOENIX-1272 On Mon, Sep 22, 2014 at 9:31 AM, James Taylor wrote: > +1 to doing the same for hbase-testing-util. Thanks for the analysis, Andrew! > > James > > On Mon, Sep 22, 2014 at 9:18 AM, Andrew Purtell wrote: >> On Thu, Sep 18, 2014 at 3:01 PM, James Taylor wrote: >>> I see. That

Re: Phoenix client maven dependencies

>From @Flavio I think the jars on maven central are built against hadoop2, so it would be > REALLY nice to publish both flavours in the next release At the very least, the jars in maven should be what we build by default (which, AFAIK, is hadoop1). HBase does some build magic so they can release

Re: Phoenix client maven dependencies

+1 to doing the same for hbase-testing-util. Thanks for the analysis, Andrew! James On Mon, Sep 22, 2014 at 9:18 AM, Andrew Purtell wrote: > On Thu, Sep 18, 2014 at 3:01 PM, James Taylor wrote: >> I see. That makes sense, but it's more of an HBase request than a >> Phoenix request. If HBase

Re: Phoenix client maven dependencies

On Thu, Sep 18, 2014 at 3:01 PM, James Taylor wrote: > I see. That makes sense, but it's more of an HBase request than a > Phoenix request. If HBase had a "client-only" pom, then Phoenix could > have a "client-only" pom as well. > > Thanks, > James If you specify only the 'hbase-client' Maven mod

Salt key hash code logic

Hello All, When I create phoenix table with salting how it calculates SALT hex. e.g. CREATE TABLE TEST.PHOENIX_TEST ( TDM INTEGER NOT NULL ,RTYP VARCHAR NOT NULL ,SSID VARCHAR NOT NULL ,D.AGE UNSIGNED_INT ,D.CAT VARCHAR CONSTRAINT PK PRIMARY KEY (TDM,RTYP,SSID) ) SALT_BUCKETS = 20 ; WHEN I do UP