Re: Thin Client Commits?

Thanks for the response; I'll wait for 4.7. On Mon, Feb 22, 2016 at 3:22 PM, Josh Elser wrote: > I only wired up commit/rollback in Calcite/Avatica in Calcite-1.6.0 [1], > so I Phoenix-4.6 isn't going to have that in the binaries that you can > download (Phoenix-4.6 is

Re: Multiple versions for single row key

PHOENIX-590 is currently unassigned, so I'm not sure when it will be implemented. We are always looking for contributions. On Mon, Feb 22, 2016 at 1:23 PM, wrote: > Thanks Thomas. Do we have rough estimate of when PHOENIX-590 will be done? > > -Original

Re: Thin Client Commits?

I only wired up commit/rollback in Calcite/Avatica in Calcite-1.6.0 [1], so I Phoenix-4.6 isn't going to have that in the binaries that you can download (Phoenix-4.6 is using 1.3.0-incubating). This should be included in the upcoming Phoenix-4.7.0. Sadly, I'm not sure why autoCommit=true

Re: Multiple versions for single row key

You need to set the versions attribute of the scan : scan ‘t1’, {RAW => true, VERSIONS => 10} As James said in a previous post, getting all versions of a row using a phoenix query is not implemented yet (https://issues.apache.org/jira/browse/PHOENIX-590) Thanks, Thomas On Mon, Feb 22, 2016 at

Re: Thin Client Commits?

I spoke too soon. This is odd. I'm using SQuirreL Client with the thin 4.6 thin client driver, and sometimes the updates/deletes take effect, and sometimes they don't. Seems like when I make a new connection the commits work, but when I go back to that same tab later, they don't. I could

Re: Phoenix rowkey

You do it exactly the way you described. Separate varchars by zero and use fixed 8 bytes for the long. So, for example if you have (varchar, u_long, varchar) primary key, the rowkey for values like 'X',1,'Y' will be : ('X', 0x00) (0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01), ('Y') Thanks,

RE: Multiple versions for single row key

Hi James, I don’t quite get it to work or I didn’t understand how it’s supposed to work. I have created a simple table to test this. Create table statement with support for 5 versions: create table MULTI_ROW_KEYS (ID VARCHAR PRIMARY KEY, PRICE DOUBLE) VERSIONS=5 Sample java code snippet to get

Phoenix rowkey

Hi, I have a HBase table created using Phoenix and the primary key is a combination of 7 columns out of which one is of type UNSIGNED_LONG and the rest are varchar. I want to perform select and upsert operation on this table using direct HBase api's. How do I construct the rowkey in this case ?

Way to alter a column datatype(INTEGER to BIGINT) in phoenix tables?

Hi All, We have a situation where we have to change the datatype of the existing column of a phoenix table from INTEGER to BIGINT. is there a way to alter the datatype without loosing the existing data? Have tried to take the snapshot of hbase table and restored it in a new pheonix table with

Re: Phoenix creates 224 regions for SYSTEM.SEQUENCE and then it kills all region servers

Hi Johannes, To override this behavior, you can do the following: - set phoenix.sequence.saltBuckets in your client-side hbase-site.xml to 0. - manually disable and drop SYSTEM.SEQUENCE from an HBase shell. Note - this assumes you're not using sequences - if you are, let us know. - re-connect a