Re: Phoenix Client threads

Hi Sergey, Thanks for your response..I got the issue.. Could you please throw some light on the Phoenix thread and Hconnections? Is it like 1 phoenix thread creates 30 Hconnections . Assuming we are running 30 concurrent reads queries which would need 30 * 30 = 900 Hconnections but I guess we

Re: Hash aggregation

Since the performance running a group-by aggregation on client side is most likely bad, it’s usually not desired. The original implementation was for functionality completeness only so it chose the easiest way, which reused some existing classes. In some cases, though, the client group-by can

Re: Hash aggregation

Hello, Any guidance or thoughts on the thread below? Thanks, Gerald On Fri, May 18, 2018 at 11:39 AM, Gerald Sangudi wrote: > Maryann, > > Can Phoenix provide hash aggregation on the client side? Are there design > / implementation reasons not to, or should I file a

Re: Phoenix Client threads

Salting byte is calculated using a hash function for the whole row key (using all pk columns). So if you are using only one of PK columns in the WHERE clause, Phoenix is unable to identify which salting byte (bucket number) should be used, so it runs scans for all salting bytes. All those threads

Phoenix Client threads

Hi, We have table with key as (type, id1, id2) (type is same for all rows where as id1 and id2 are unique for each row) which is salted (30 salt buckets) The load on this table is about 30 queries/sec with each query taking ~6ms we are using phoenix 4.7.0 non-thin client we have query like below

Re: Phoenix ODBC driver limitations

Hey Stepan, There is a driver called phoenix-sharp (https://github.com/Azure/hdinsight-phoenix-sharp) from MS Azure. The project has not been updated for a while though. Francis On 22/05/2018 6:16 PM, Stepan Migunov wrote: Hi, Is the ODBC driver from Hortonworks the only way to access

Phoenix ODBC driver limitations

Hi, Is the ODBC driver from Hortonworks the only way to access Phoenix from .NET code now? The problem is that driver has some critical limitations - it seems, driver doesn't support Namespace Mapping (it couldn't be able to connect to Phoenix if phoenix.schema.isNamespaceMappingEnabled=true)