GitHub user prabhjyotsingh opened a pull request:
https://github.com/apache/zeppelin/pull/1103
[ZEPPELIN-1076] Set hbase.client.retries.number for JDBC
### What is this PR for?
If a user has "org.apache.phoenix:phoenix-core:4.x.x" jar added as a
dependency in JDBC interpreter, and for some reason phoenix was not accessible
or not properly configured; then the phoenix tries to for 35 times (which is
default for hbase.client.retries.number) and each retires is 8 second apart,
before it finally fails.
### What type of PR is it?
[Bug Fix]
### Todos
* [x] - Set phoenix.hbase.client.retries.number for JDBC
### What is the Jira issue?
* [ZEPPELIN-1076](https://issues.apache.org/jira/browse/ZEPPELIN-1076)
### How should this be tested?
In JDBC interpreter add `org.apache.phoenix:phoenix-core:4.4.0-HBase-1.0`
as dependency, but don't configure phoenix setting.
Then try to run any sql query with any of the configured JDBC driver (like
`show tables`)
- Without this it will take slightly more than about 5 mins
- With this it should fetch result sooner (in less than a minute)
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update? n/a
* Is there breaking changes for older versions? n/a
* Does this needs documentation? n/a
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/prabhjyotsingh/zeppelin ZEPPELIN-1076
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1103.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1103
----
commit 4da9763645a4f7832a435ff383b4cb78aa5ae2d2
Author: Prabhjyot Singh <prabhjyotsi...@gmail.com>
Date: 2016-06-28T18:12:03Z
Set phoenix.hbase.client.retries.number for JDBC
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
