Re: Guidance to improve upsert performance

Hi Zach, Here are some things to try: - make sure you're batching your upserts by turning off auto commit. Maybe start with a batch size of 1000 and commit when you reach this. - to reduce RPC traffic, set the UPDATE_CACHE_FREQUENCY (4.7 or above) on your table and indexes when you create them (or

Re: Java Query timeout

Regarding your second question, try export HBASE_CONF_DIR= before running the client. > On Aug 4, 2016, at 3:01 PM, kannan.ramanat...@barclays.com wrote: > > Any pointers? > > From: Ramanathan, Kannan: R (NYK) > Sent: Wednesday, August 03, 2016 15:08 > To: user@phoenix.apache.org

RE: Java Query timeout

Any pointers? From: Ramanathan, Kannan: R (NYK) Sent: Wednesday, August 03, 2016 15:08 To: user@phoenix.apache.org Subject: RE: Java Query timeout Can someone please take a look? From: Ramanathan, Kannan: IT (NYK) Sent: Tuesday, August 02, 2016 15:59 To:

Re: Unset `MAX_FILESIZE` for index table

Thanks Jean. Yeah, I can do that in HBase shell for sure. I am wondering if there is a way to do it in Phoenix upon creation. > On Aug 4, 2016, at 10:57 AM, Jean-Marc Spaggiari > wrote: > > Hi, > > Have you tried something like this? > > alter ‘t1’, METHOD =>

Unset `MAX_FILESIZE` for index table

Hi all, Global index tables have `MAX_FILESIZE` automatically set upon creation. This option can be overridden by setting `MAX_FILESIZE = xx` in DDL. But how can we force it to be unset in DDL? Thanks in advance! Best, Simon

Cant do select = Row length is 0

while doing a ---> (select * from BIDDING_EVENTS_PROD WHERE wTs IS NOT NULL AND TS >= 1470201526501 AND TS < 1470287926501;) java.lang.RuntimeException: org.apache.phoenix.exception.PhoenixIOException: org.apache.phoenix.exception.PhoenixIOException: