About elserj

elserj · ‎06-16-2016

FWIW, this should be fixed in recent versions of Apache Phoenix and HDP.

elserj · ‎06-14-2016

The phoenix-sqlline command is not using PQS. You want to use /usr/hdp/current/phoenix-client/bin/sqlline-thin.py to interactive with PQS.

elserj · ‎06-13-2016

Accumulo would work for the same reasons that HBase does.

elserj · ‎06-09-2016

Nice table -- what version of HDP did you base it on?

elserj · ‎06-09-2016

To my understanding, CALCITE-1025 does provide what's necessary for Avatica to work with Knox (based on some earlier conversations with Knox folks), but there are two missing things still. Phoenix 4.8 was also just updated to use a version of Avatica which contains CALCITE-1025. Configuration in Phoenix to set the username:password "database" (properties file for Jetty) that Avatica is expecting Actual testing with Knox I think we're close, but it's definitely not going to work out of the box right now.

elserj · ‎06-07-2016

Yep, you're right: over time, compactions will bring data local and help with locality concerns. Lots of factors play into this, but I'm more of the mindset that just having homogeneous nodes is helpful in deployments. One less thing to worry about 🙂

elserj · ‎06-07-2016

It's generally recommended that you install HBase RegionServers on each datanode. RegionServers can benefit from "short-circuit" reads which can only happen when the RegionServer is co-located with the Datanode. You can run the Phoenix QueryServer on each RegionServer, but it is likely not as necessary as RegionServers. This decision should be based on the capacity requirements of your Phoenix users. One Phoenix QueryServer can easily service many users' workloads. Having a local RegionServer is not a concern for the Phoenix QueryServer. One QueryServer will talk to many RegionServers for each query. There isn't a notion of locality.

elserj · ‎06-06-2016

There may also be some issue communicating with the Master/RegionServers that is causing the client to hang. Check the HBase Master UI and make sure your RS's are online, there are no regions in transition, no "big scary red boxes", etc.

elserj · ‎06-03-2016

Apache HBase does not provide any API around JSON, but you can build your own. You might be interested in following the following JIRA issue about adding JSON as a native type to Apache Phoenix: PHOENIX-628

elserj · ‎05-26-2016

It seems possible that your application might be prematurely closing the HBase `Connection` while your tasks are still using HTable instances that use that Connection. Have you investigated this at all? Any chance you can share more about your application?

Online	Offline
Last Visited	‎07-01-2022 02:44 PM

Member Since	‎07-17-2019 08:58 AM
Last Visited	‎07-01-2022 02:44 PM
Posts	738
Kudos received	429

Cloudera Community

Re: Why can't Object Stores like Amazon S3 be used...

Re: Not a host:port pair: PBUF, how to resolve?

Re: versioning question in hbase

Re: Phoenix query call from java on larger data se...

Re: Revoke permissions to a superuser on Hbase

Re: Phoenix - Query Timeout

Re: Phoenix Query Server - Won't Start - java.net...

Re: Where to store a really wide table?

Re: HDP services supporting RESTFul read, write an...

Re: is there a way to setup Phoenix with Knox in H...

Re: Number of Region Servers, Phoenix Server on HB...

Re: Number of Region Servers, Phoenix Server on HB...

Re: Phoenix connection error while secure Hbase cl...

Re: JSON support to HBASE

Re: Unable to execute hbase job due to Unexpected...