Re: Regarding rowkey encoding in Phoenix as compared to HBase

2014-07-30 Thread Abhilash L L
@Ashish Phoenix flips the sign bit, so that negative numbers are sorted before positive values Refer http://phoenix.apache.org/language/datatypes.html for more details. Regards, Abhilash L L Capillary Technologies M:919886208262 abhil...@capillarytech.com | www.capillarytech.com Email from peop

Re: Phoenix and HDP 2.0

2014-07-30 Thread Russell, Bob
Nicolas, Error message for both 3.0 and 4.0 below. Hopefully, there is something simple to get this going without going through upgrade. *With Phoenix 3.0 I get the following:* Setting property: [isolation, TRANSACTION_READ_COMMITTED] issuing: !connect jdbc:phoenix:localhost:2181 none none org

Re: Phoenix and HDP 2.0

2014-07-30 Thread James Taylor
Hi Bob, Phoenix doesn't support HBase 0.96. You'll need to either: - upgrade to HDP 2.1 - fix PHOENIX-848 Thanks, James On Wed, Jul 30, 2014 at 10:32 AM, Russell, Bob wrote: > Nicolas, > > Error message for both 3.0 and 4.0 below. Hopefully, there is something > simple to get this going witho

select distinct on a casted value

2014-07-30 Thread Abe Weinograd
I am testing some queries in Squirrel. Because we are using unsigned_date, squirrel isn't terribly happy about that and I frequently am casting those values to date or timestamp. When I do SELECT CAST(column1 AS TIMESTAMP), ... FROM table that seems to work fine. If I put a distinct in front of

Re: select distinct on a casted value

2014-07-30 Thread James Taylor
Not a known issue as far as I know. Please file a JIRA. If you can try against the latest in the 3.0 branch to see if the problem is fixed already, that would be much appreciated. Thanks, James On Wed, Jul 30, 2014 at 11:20 AM, Abe Weinograd wrote: > I am testing some queries in Squirrel. Becaus

Re: Split rowkey in HBASE to composite key in phoenix

2014-07-30 Thread Ravi Kiran
Hi Thanapool, Though its easy to do a import of a sql table to hbase tables backed by phoenix using Sqoop, we do notice issues when the row key of the hbase table is a set of composite columns. This is because the delimiter used by Phoenix is different from what Sqoop uses by default. We are