phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcelo Valle <>
Subject Re: jdbc driver - fat vs thin and hbase-site.xml
Date Fri, 22 Dec 2017 17:48:56 GMT
Hi Josh,

Thanks for answering. Out of curiosity, is there any way of connecting to
phoenix without having to add files on class path? I was hoping it would
work if I inform the DNS of a single node of zoo keeper quorum, as the rest
of the nodes can be found from the node itself.


On 21 December 2017 at 20:02, Josh Elser <> wrote:

> Hi Marcelo,
> The requirement for hbase-site.xml and core-site.xml to be on the
> classpath are a "wart", resulting from the close ties to HBase and Hadoop
> -- much of the Kerberos authentication code is inherited from Hadoop, and
> thus requires some of that configuration.
> I'd encourage you to look at the contents of the core-site.xml and
> hbase-site.xml files. There is very likely nothing that you would need to
> change in these files if you add a new node to your cluster.
> The thin-client talks to the Phoenix Query Server instead of talking
> directly to HBase which does simplify the scenario. However, using the thin
> driver implies that you're (always) doing more work to answer a equivalent
> query as compared to the thick driver.
> On 12/21/17 11:11 AM, Marcelo Valle wrote:
>> Hi,
>> I am new to Apache Phoenix and I am trying to use it in a new project. I
>> am sorry if I am asking something basic here, but I was struggling to find
>> this info on the web.
>> I successfully created a simple application using jdbc fat driver,
>> starting up phoenix using HBaseTestingUtility without any problems, I was
>> able to connect, test, and make sure my code is working as expected.
>> Now it's time to connect to the real cluster we have in dev environment.
>> I was surprised when I found out that just JDBC connection url and kerberos
>> auth are not enough to connect to the real cluster, I have to add some
>> hbase xml files with the cluster information to the classpath, so the
>> driver can know about the cluster nodes.
>> Question - is there a way to avoid that? If I use the thin driver, will I
>> still need these XML files? Suppose I add a new node to my phoenix cluster,
>> does it mean I will have to redeploy my application so the new node can be
>> considered?
>> Thanks,
>> --
>> Marcelo Valle
>> - @mvallebr

Marcelo Valle - @mvallebr

View raw message