Re: Getting too many open files during table scan

We started with no salt buckets, but the performance was terrible in our testing. A leading date column is in our schema model. We don't seem to be getting hotspotting after salting. Date range scans are very common as are slice and dice on many dimension columns. We have tested with a range

Re: Getting too many open files during table scan

My recommendation: don't use salt buckets unless you have a monatomically increasing row key, for example one that leads with the current date/time. Otherwise you'll be putting more load (# of salt buckets more load worst case) for bread-and-butter small-range-scan Phoenix queries. Thanks, James

Re: Getting too many open files during table scan

The ulimit open files was only 1024 for the user executing the query. After increasing, the queries behaves better. How can we tell if we need to reduce/increase the number of salt buckets? Our team set this based on read/write performance using data volume and expected queries to be run by

Re: Explain Plan - Full scan vs Skip scan

Hi Michael, Would it be possible for you to provide an example with DDL, query, and explain plan? Thanks, James On Fri, Jun 23, 2017 at 2:36 AM Mike Prendergast wrote: > We are currently using Phoenix 4.9 in EMR 5.6. We have been constructing > queries that we would

phoenix query modtime

I have a phoenix table created on existing hbase table, and want to query something like select * from mytable where modtime>'2010-01-01', how do I query phoenix like this? seems it doesn't have a modtime column if I don't do the modtime mapping, which I can not do because it has to be part of

Re: Cant run map-reduce index builder because my view/idx is lower case

Great, i will try. > On 23 Jun 2017, at 00:24, Sergey Soldatov wrote: > > You may try to build Phoenix with patch from PHOENIX-3710 > applied.That should fix > the problem, I believe. > Thanks, > Sergey > > On

Re: Cant run map-reduce index builder because my view/idx is lower case

You may try to build Phoenix with patch from PHOENIX-3710 applied.That should fix the problem, I believe. Thanks, Sergey On Mon, Jun 19, 2017 at 11:28 AM, Batyrshin Alexander <0x62...@gmail.com> wrote: > Hello again, > > Could you, please,

Explain Plan - Full scan vs Skip scan

We are currently using Phoenix 4.9 in EMR 5.6. We have been constructing queries that we would expect the explain plan to describe as either skip scan or range scan queries. Instead, it returns 1-way round robin full scans in the plan output. However, when we execute the queries, Phoenix does not

How to create new table as existing table with same structure and data ??

HBase version : 1.2.6 Phoenix version : 4.10.0-HBase-1.2.6 I am trying to create new table by using the already existing table but I don't know how to do it ?? I have tried like: CREATE TABLE "+targerSchemaName+"."+targetTableName+" AS SELECT * FROM "+schemaName+"."+tableName and also i tried