You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@phoenix.apache.org by ja...@apache.org on 2016/03/04 04:09:21 UTC
svn commit: r1733556 - in /phoenix/site: publish/index.html
source/src/site/markdown/index.md
Author: jamestaylor
Date: Fri Mar 4 03:09:21 2016
New Revision: 1733556
URL: http://svn.apache.org/viewvc?rev=1733556&view=rev
Log:
Updates to overview
Modified:
phoenix/site/publish/index.html
phoenix/site/source/src/site/markdown/index.md
Modified: phoenix/site/publish/index.html
URL: http://svn.apache.org/viewvc/phoenix/site/publish/index.html?rev=1733556&r1=1733555&r2=1733556&view=diff
==============================================================================
--- phoenix/site/publish/index.html (original)
+++ phoenix/site/publish/index.html Fri Mar 4 03:09:21 2016
@@ -209,10 +209,10 @@
<p>For any omitted parts, the relevant property value, hbase.zookeeper.quorum, hbase.zookeeper.property.clientPort, and zookeeper.znode.parent will be used from hbase-site.xml configuration file. The optional <tt>principal</tt> and <tt>keytab file</tt> may be used to connect to a Kerberos secured cluster. If only <tt>principal</tt> is specified, then this defines the user name with each distinct user having their own dedicated HBase connection (HConnection). This provides a means of having multiple, different connections each with different configuration properties on the same JVM.</p>
<p>For example, the following connection string might be used for longer running queries, where the <tt>longRunningProps</tt> specifies Phoenix and HBase configuration properties with longer timeouts: </p>
<div>
- <pre><tt>Connection conn = DriverManager.getConnection(âjdbc:phoenix:server1,server2:3333:longRunningâ, longRunningProps);</tt></pre>
+ <pre><tt>Connection conn = DriverManager.getConnection(âjdbc:phoenix:my_server:longRunningâ, longRunningProps);</tt></pre>
</div> while the following connection string might be used for shorter running queries:
<div>
- <pre><tt>Connection conn = DriverManager.getConnection("jdbc:phoenix:server1,server2:3333:shortRunning", shortRunningProps);</tt></pre>
+ <pre><tt>Connection conn = DriverManager.getConnection("jdbc:phoenix:my_server:shortRunning", shortRunningProps);</tt></pre>
</div>
<div class="section">
<div class="section">
Modified: phoenix/site/source/src/site/markdown/index.md
URL: http://svn.apache.org/viewvc/phoenix/site/source/src/site/markdown/index.md?rev=1733556&r1=1733555&r2=1733556&view=diff
==============================================================================
--- phoenix/site/source/src/site/markdown/index.md (original)
+++ phoenix/site/source/src/site/markdown/index.md Fri Mar 4 03:09:21 2016
@@ -83,10 +83,10 @@ user having their own dedicated HBase co
configuration properties on the same JVM.
For example, the following connection string might be used for longer running queries, where the <code>longRunningProps</code> specifies Phoenix and HBase configuration properties with longer timeouts:
-<pre><code>Connection conn = DriverManager.getConnection("jdbc:phoenix:server1,server2:3333:longRunning", longRunningProps);</code></pre>
+<pre><code>Connection conn = DriverManager.getConnection("jdbc:phoenix:my_server:longRunning", longRunningProps);</code></pre>
while the following connection string might be used for shorter running queries:
-<pre><code>Connection conn = DriverManager.getConnection("jdbc:phoenix:server1,server2:3333:shortRunning", shortRunningProps);</code></pre>
+<pre><code>Connection conn = DriverManager.getConnection("jdbc:phoenix:my_server:shortRunning", shortRunningProps);</code></pre>
####Not Supported