Re: unsubscribe

Send your unsubscribe request to user-unsubscr...@phoenix.apache.org to unsubscribe. :) On 29/03/2016 4:54 PM, Dor Ben Dov wrote: This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at

Exception while trying to connect to Phoenix client

Hello, We just upgraded phoenix to 4.6 from 4.5.3. Trying to start the client and I see this exception. Not sure if I am missing anything here. Any suggestions/help is greatly appreciated. Error: org.apache.phoenix.exception.PhoenixIOException:

Re: Speeding Up Group By Queries

Here's the chart for time it takes for each of the parallel scans after split. On RS where data is not read from disk scan gets back in ~20 secs but for the RS which has 6 it's ~45 secs. [image: Inline image 2] Yes I see disk reads with 607 ios/second on the hosts that stores 6 regions > Two

Re: Slow metadata update queries during upsert

Hi Ankur, Try setting the UPDATE_CACHE_FREQUENCY on your table (4.7.0 or above) to prevent the client from checking with the server on whether or not your table metadata is up to date. See here[1] for more information. You can issue a command like this which will hold on to your metadata on the

Re: Slow metadata update queries during upsert

Please ignore the same query from another email id of mine. I was getting failure notification while sending emails from other id but after few hours somehow they showed up. Sorry for spamming. Thanks, Ankur Jain From: Ankur Jain >

Slow metadata update queries during upsert

Hi  We are using phoenix as our transactional data store(though we are not yet using its latest transaction feature yet). Earlier we had our own custom query layer built on top of hbase that we are trying to replace. During tests we found that inserts are very slow as compared to regular hbase

Slow metadata update queries during upsert

Hi  We are using phoenix as our transactional data store(though we are not yet using its latest transaction feature yet). Earlier we had our own custom query layer built on top of hbase that we are trying to replace. During tests we found that inserts are very slow as compared to regular