Author: minalee
Date: Wed Sep 28 03:59:23 2016
New Revision: 1762602

URL: http://svn.apache.org/viewvc?rev=1762602&view=rev
Log:
https://github.com/apache/zeppelin/pull/1436

Modified:
    zeppelin/site/docs/0.7.0-SNAPSHOT/atom.xml
    zeppelin/site/docs/0.7.0-SNAPSHOT/interpreter/jdbc.html
    zeppelin/site/docs/0.7.0-SNAPSHOT/rss.xml
    zeppelin/site/docs/0.7.0-SNAPSHOT/search_data.json

Modified: zeppelin/site/docs/0.7.0-SNAPSHOT/atom.xml
URL: 
http://svn.apache.org/viewvc/zeppelin/site/docs/0.7.0-SNAPSHOT/atom.xml?rev=1762602&r1=1762601&r2=1762602&view=diff
==============================================================================
--- zeppelin/site/docs/0.7.0-SNAPSHOT/atom.xml (original)
+++ zeppelin/site/docs/0.7.0-SNAPSHOT/atom.xml Wed Sep 28 03:59:23 2016
@@ -4,7 +4,7 @@
  <title>Apache Zeppelin</title>
  <link href="http://zeppelin.apache.org/"; rel="self"/>
  <link href="http://zeppelin.apache.org"/>
- <updated>2016-09-27T12:46:46+09:00</updated>
+ <updated>2016-09-28T12:58:09+09:00</updated>
  <id>http://zeppelin.apache.org</id>
  <author>
    <name>The Apache Software Foundation</name>

Modified: zeppelin/site/docs/0.7.0-SNAPSHOT/interpreter/jdbc.html
URL: 
http://svn.apache.org/viewvc/zeppelin/site/docs/0.7.0-SNAPSHOT/interpreter/jdbc.html?rev=1762602&r1=1762601&r2=1762602&view=diff
==============================================================================
--- zeppelin/site/docs/0.7.0-SNAPSHOT/interpreter/jdbc.html (original)
+++ zeppelin/site/docs/0.7.0-SNAPSHOT/interpreter/jdbc.html Wed Sep 28 03:59:23 
2016
@@ -456,41 +456,79 @@ limitations under the License.
 
 <h3>Phoenix</h3>
 
-<h4>Properties</h4>
+<p>Phoenix supports <code>thick</code> and <code>thin</code> connection 
types:</p>
+
+<ul>
+<li>Thick client is faster, but must connect directly to ZooKeeper and HBase 
RegionServers.</li>
+<li>Thin client has fewer dependencies and connects through a <a 
href="http://phoenix.apache.org/server.html";>Phoenix Query Server</a> 
instance.</li>
+</ul>
+
+<p>Use the appropriate <code>phoenix.driver</code> and 
<code>phoenix.url</code> for your connection type.</p>
+
+<h4>Properties:</h4>
 
 <p><table class="table-configuration">
    <tr>
      <th>Name</th>
      <th>Value</th>
+     <th>Description</th>
    </tr>
    <tr>
      <td>phoenix.driver</td>
      <td>org.apache.phoenix.jdbc.PhoenixDriver</td>
+     <td>&#39;Thick Client&#39;, connects directly to Phoenix</td>
+   </tr>
+   <tr>
+     <td>phoenix.driver</td>
+     <td>org.apache.phoenix.queryserver.client.Driver</td>
+     <td>&#39;Thin Client&#39;, connects via Phoenix Query Server</td>
    </tr>
    <tr>
      <td>phoenix.url</td>
      <td>jdbc:phoenix:localhost:2181:/hbase-unsecure</td>
+     <td>&#39;Thick Client&#39;, connects directly to Phoenix</td>
+   </tr>
+   <tr>
+     <td>phoenix.url</td>
+     
<td>jdbc:phoenix:thin:url=http://localhost:8765;serialization=PROTOBUF</td>
+     <td>&#39;Thin Client&#39;, connects via Phoenix Query Server</td>
    </tr>
    <tr>
      <td>phoenix.user</td>
      <td>phoenix<em>user</td>
+     <td></td>
    </tr>
    <tr>
      <td>phoenix.password</td>
      <td>phoenix</em>password</td>
+     <td></td>
    </tr>
  </table></p>
 
-<h4>Dependencies</h4>
+<h4>Dependencies:</h4>
+
+<p>Include the dependency for your connection type (it should be only 
<em>one</em> of the following).</p>
 
 <p><table class="table-configuration">
    <tr>
      <th>Artifact</th>
      <th>Excludes</th>
+     <th>Description</th>
    </tr>
    <tr>
      <td>org.apache.phoenix:phoenix-core:4.4.0-HBase-1.0</td>
      <td></td>
+     <td>&#39;Thick Client&#39;, connects directly to Phoenix</td>
+   </tr>
+   <tr>
+     <td>org.apache.phoenix:phoenix-server-client:4.7.0-HBase-1.1</td>
+     <td></td>
+     <td>&#39;Thin Client&#39; for Phoenix 4.7, connects via Phoenix Query 
Server</td>
+   </tr>
+   <tr>
+     <td>org.apache.phoenix:phoenix-queryserver-client:4.8.0-HBase-1.2</td>
+     <td></td>
+     <td>&#39;Thin Client&#39; for Phoenix 4.8+, connects via Phoenix Query 
Server</td>
    </tr>
  </table></p>
 

Modified: zeppelin/site/docs/0.7.0-SNAPSHOT/rss.xml
URL: 
http://svn.apache.org/viewvc/zeppelin/site/docs/0.7.0-SNAPSHOT/rss.xml?rev=1762602&r1=1762601&r2=1762602&view=diff
==============================================================================
--- zeppelin/site/docs/0.7.0-SNAPSHOT/rss.xml (original)
+++ zeppelin/site/docs/0.7.0-SNAPSHOT/rss.xml Wed Sep 28 03:59:23 2016
@@ -5,8 +5,8 @@
         <description>Apache Zeppelin - The Apache Software 
Foundation</description>
         <link>http://zeppelin.apache.org</link>
         <link>http://zeppelin.apache.org</link>
-        <lastBuildDate>2016-09-27T12:46:46+09:00</lastBuildDate>
-        <pubDate>2016-09-27T12:46:46+09:00</pubDate>
+        <lastBuildDate>2016-09-28T12:58:09+09:00</lastBuildDate>
+        <pubDate>2016-09-28T12:58:09+09:00</pubDate>
         <ttl>1800</ttl>
 
 

Modified: zeppelin/site/docs/0.7.0-SNAPSHOT/search_data.json
URL: 
http://svn.apache.org/viewvc/zeppelin/site/docs/0.7.0-SNAPSHOT/search_data.json?rev=1762602&r1=1762601&r2=1762602&view=diff
==============================================================================
--- zeppelin/site/docs/0.7.0-SNAPSHOT/search_data.json (original)
+++ zeppelin/site/docs/0.7.0-SNAPSHOT/search_data.json Wed Sep 28 03:59:23 2016
@@ -4,7 +4,7 @@
 
     "/atom.xml": {
       "title": "Atom Feed",
-      "content"  : " Apache Zeppelin   2016-09-27T12:46:46+09:00 
http://zeppelin.apache.org    The Apache Software Foundation   
[email protected]  ",
+      "content"  : " Apache Zeppelin   2016-09-28T12:58:09+09:00 
http://zeppelin.apache.org    The Apache Software Foundation   
[email protected]  ",
       "url": " /atom.xml",
       "group": "",
       "excerpt": ""
@@ -269,7 +269,7 @@
 
     "/interpreter/jdbc.html": {
       "title": "Generic JDBC Interpreter for Apache Zeppelin",
-      "content"  : "&lt;!--Licensed under the Apache License, Version 2.0 (the 
&quot;License&quot;);you may not use this file except in compliance with the 
License.You may obtain a copy of the License 
athttp://www.apache.org/licenses/LICENSE-2.0Unless required by applicable law 
or agreed to in writing, softwaredistributed under the License is distributed 
on an &quot;AS IS&quot; BASIS,WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, 
either express or implied.See the License for the specific language governing 
permissions andlimitations under the License.--&gt;Generic JDBC Interpreter for 
Apache ZeppelinOverviewThis interpreter lets you create a JDBC connection to 
any data source, by now it has been tested 
with:PostgresMySqlMariaDBRedshiftApache HiveApache PhoenixApache Drill (Details 
on using Drill JDBC Driver)Apache TajoIf someone else used another database 
please report how it works to improve functionality.Create InterpreterWhen you 
create a interpreter by default use PostgreSQL with
  the next properties:      name    value        common.max_count    1000       
 default.driver    org.postgresql.Driver        default.password    ********    
    default.url    jdbc:postgresql://localhost:5432/        default.user    
gpadmin        It is not necessary to add driver jar to the classpath for 
PostgreSQL as it is included in Zeppelin.Simple connectionPrior to creating the 
interpreter it is necessary to add maven coordinate or path of the JDBC driver 
to the Zeppelin classpath. To do this you must edit dependencies artifact(ex. 
mysql:mysql-connector-java:5.1.38) in interpreter menu as shown:        To 
create the interpreter you need to specify connection parameters as shown in 
the table.      name    value        common.max_count    1000        
default.driver    driver name        default.password    ********        
default.url    jdbc url        default.user    user name        Multiple 
connectionsJDBC interpreter also allows connections to multiple data sources. 
It is 
 necessary to set a prefix for each connection to reference it in the paragraph 
in the form of %jdbc(prefix). Before you create the interpreter it is necessary 
to add each driver&amp;#39;s maven coordinates or JDBC driver&amp;#39;s jar 
file path to the Zeppelin classpath. To do this you must edit the dependencies 
of JDBC interpreter in interpreter menu as following:        You can add all 
the jars you need to make multiple connections into the same JDBC interpreter. 
To create the interpreter you must specify the parameters. For example we will 
create two connections to MySQL and Redshift, the respective prefixes are 
default and redshift:      name    value        common.max_count    1000        
default.driver    com.mysql.jdbc.Driver        default.password    ********     
   default.url    jdbc:mysql://localhost:3306/        default.user    
mysql-user        redshift.driver    com.amazon.redshift.jdbc4.Driver        
redshift.password    ********        redshift.url    jdbc:redshift:
 //examplecluster.abc123xyz789.us-west-2.redshift.amazonaws.com:5439        
redshift.user    redshift-user        Bind to NotebookIn the Notebook click on 
the settings icon at the top-right corner. Use select/deselect to specify the 
interpreters to be used in the Notebook.More PropertiesYou can modify the 
interpreter configuration in the Interpreter section. The most common 
properties are as follows, but you can specify other properties that need to be 
connected.        Property Name     Description           {prefix}.url     JDBC 
URL to connect, the URL must include the name of the database            
{prefix}.user     JDBC user name           {prefix}.password     JDBC password  
         {prefix}.driver     JDBC driver name.           common.max_result     
Max number of SQL result to display to prevent the browser overload. This is  
common properties for all connections           zeppelin.jdbc.auth.type     
Types of authentications&amp;#39; methods supported are SIMPLE, and KERBERO
 S           zeppelin.jdbc.principal     The principal name to load from the 
keytab           zeppelin.jdbc.keytab.location     The path to the keytab file  
  To develop this functionality use this method. For example if a connection 
needs a schema parameter, it would have to add the property as follows:      
name    value        {prefix}.schema    schema_name  ExamplesHiveProperties     
   Name     Value           hive.driver     org.apache.hive.jdbc.HiveDriver     
      hive.url     jdbc:hive2://localhost:10000           hive.user     
hiveuser           hive.password     hivepassword    Dependencies        
Artifact     Excludes           org.apache.hive:hive-jdbc:0.14.0                
org.apache.hadoop:hadoop-common:2.6.0         PhoenixProperties        Name     
Value           phoenix.driver     org.apache.phoenix.jdbc.PhoenixDriver        
   phoenix.url     jdbc:phoenix:localhost:2181:/hbase-unsecure           
phoenix.user     phoenixuser           phoenix.password     phoenixpa
 ssword    Dependencies        Artifact     Excludes           
org.apache.phoenix:phoenix-core:4.4.0-HBase-1.0         TajoProperties        
Name     Value           tajo.driver     org.apache.tajo.jdbc.TajoDriver        
   tajo.url     jdbc:tajo://localhost:26002/default    Dependencies        
Artifact     Excludes           org.apache.tajo:tajo-jdbc:0.11.0         How to 
useReference in paragraphStart the paragraphs with the %jdbc, this will use the 
default prefix for connection. If you want to use other connection you should 
specify the prefix of it as follows %jdbc(prefix):%jdbcSELECT * FROM 
db_name;or%jdbc(prefix)SELECT * FROM db_name;Apply Zeppelin Dynamic FormsYou 
can leverage Zeppelin Dynamic Form inside your queries. You can use both the 
text input and select form parametrization features%jdbc(prefix)SELECT name, 
country, performerFROM demo.performersWHERE name=&amp;#39;&amp;#39;Bugs 
&amp;amp; ReportingIf you find a bug for this interpreter, please create a JIRA 
ticket.",
+      "content"  : "&lt;!--Licensed under the Apache License, Version 2.0 (the 
&quot;License&quot;);you may not use this file except in compliance with the 
License.You may obtain a copy of the License 
athttp://www.apache.org/licenses/LICENSE-2.0Unless required by applicable law 
or agreed to in writing, softwaredistributed under the License is distributed 
on an &quot;AS IS&quot; BASIS,WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, 
either express or implied.See the License for the specific language governing 
permissions andlimitations under the License.--&gt;Generic JDBC Interpreter for 
Apache ZeppelinOverviewThis interpreter lets you create a JDBC connection to 
any data source, by now it has been tested 
with:PostgresMySqlMariaDBRedshiftApache HiveApache PhoenixApache Drill (Details 
on using Drill JDBC Driver)Apache TajoIf someone else used another database 
please report how it works to improve functionality.Create InterpreterWhen you 
create a interpreter by default use PostgreSQL with
  the next properties:      name    value        common.max_count    1000       
 default.driver    org.postgresql.Driver        default.password    ********    
    default.url    jdbc:postgresql://localhost:5432/        default.user    
gpadmin        It is not necessary to add driver jar to the classpath for 
PostgreSQL as it is included in Zeppelin.Simple connectionPrior to creating the 
interpreter it is necessary to add maven coordinate or path of the JDBC driver 
to the Zeppelin classpath. To do this you must edit dependencies artifact(ex. 
mysql:mysql-connector-java:5.1.38) in interpreter menu as shown:        To 
create the interpreter you need to specify connection parameters as shown in 
the table.      name    value        common.max_count    1000        
default.driver    driver name        default.password    ********        
default.url    jdbc url        default.user    user name        Multiple 
connectionsJDBC interpreter also allows connections to multiple data sources. 
It is 
 necessary to set a prefix for each connection to reference it in the paragraph 
in the form of %jdbc(prefix). Before you create the interpreter it is necessary 
to add each driver&amp;#39;s maven coordinates or JDBC driver&amp;#39;s jar 
file path to the Zeppelin classpath. To do this you must edit the dependencies 
of JDBC interpreter in interpreter menu as following:        You can add all 
the jars you need to make multiple connections into the same JDBC interpreter. 
To create the interpreter you must specify the parameters. For example we will 
create two connections to MySQL and Redshift, the respective prefixes are 
default and redshift:      name    value        common.max_count    1000        
default.driver    com.mysql.jdbc.Driver        default.password    ********     
   default.url    jdbc:mysql://localhost:3306/        default.user    
mysql-user        redshift.driver    com.amazon.redshift.jdbc4.Driver        
redshift.password    ********        redshift.url    jdbc:redshift:
 //examplecluster.abc123xyz789.us-west-2.redshift.amazonaws.com:5439        
redshift.user    redshift-user        Bind to NotebookIn the Notebook click on 
the settings icon at the top-right corner. Use select/deselect to specify the 
interpreters to be used in the Notebook.More PropertiesYou can modify the 
interpreter configuration in the Interpreter section. The most common 
properties are as follows, but you can specify other properties that need to be 
connected.        Property Name     Description           {prefix}.url     JDBC 
URL to connect, the URL must include the name of the database            
{prefix}.user     JDBC user name           {prefix}.password     JDBC password  
         {prefix}.driver     JDBC driver name.           common.max_result     
Max number of SQL result to display to prevent the browser overload. This is  
common properties for all connections           zeppelin.jdbc.auth.type     
Types of authentications&amp;#39; methods supported are SIMPLE, and KERBERO
 S           zeppelin.jdbc.principal     The principal name to load from the 
keytab           zeppelin.jdbc.keytab.location     The path to the keytab file  
  To develop this functionality use this method. For example if a connection 
needs a schema parameter, it would have to add the property as follows:      
name    value        {prefix}.schema    schema_name  ExamplesHiveProperties     
   Name     Value           hive.driver     org.apache.hive.jdbc.HiveDriver     
      hive.url     jdbc:hive2://localhost:10000           hive.user     
hiveuser           hive.password     hivepassword    Dependencies        
Artifact     Excludes           org.apache.hive:hive-jdbc:0.14.0                
org.apache.hadoop:hadoop-common:2.6.0         PhoenixPhoenix supports thick and 
thin connection types:Thick client is faster, but must connect directly to 
ZooKeeper and HBase RegionServers.Thin client has fewer dependencies and 
connects through a Phoenix Query Server instance.Use the appropriate phoen
 ix.driver and phoenix.url for your connection type.Properties:        Name     
Value     Description           phoenix.driver     
org.apache.phoenix.jdbc.PhoenixDriver     &amp;#39;Thick Client&amp;#39;, 
connects directly to Phoenix           phoenix.driver     
org.apache.phoenix.queryserver.client.Driver     &amp;#39;Thin Client&amp;#39;, 
connects via Phoenix Query Server           phoenix.url     
jdbc:phoenix:localhost:2181:/hbase-unsecure     &amp;#39;Thick Client&amp;#39;, 
connects directly to Phoenix           phoenix.url     
jdbc:phoenix:thin:url=http://localhost:8765;serialization=PROTOBUF     
&amp;#39;Thin Client&amp;#39;, connects via Phoenix Query Server           
phoenix.user     phoenixuser                phoenix.password     
phoenixpassword         Dependencies:Include the dependency for your connection 
type (it should be only one of the following).        Artifact     Excludes     
Description           org.apache.phoenix:phoenix-core:4.4.0-HBase-1.0          
&amp;#39;T
 hick Client&amp;#39;, connects directly to Phoenix           
org.apache.phoenix:phoenix-server-client:4.7.0-HBase-1.1          &amp;#39;Thin 
Client&amp;#39; for Phoenix 4.7, connects via Phoenix Query Server           
org.apache.phoenix:phoenix-queryserver-client:4.8.0-HBase-1.2          
&amp;#39;Thin Client&amp;#39; for Phoenix 4.8+, connects via Phoenix Query 
Server    TajoProperties        Name     Value           tajo.driver     
org.apache.tajo.jdbc.TajoDriver           tajo.url     
jdbc:tajo://localhost:26002/default    Dependencies        Artifact     
Excludes           org.apache.tajo:tajo-jdbc:0.11.0         How to useReference 
in paragraphStart the paragraphs with the %jdbc, this will use the default 
prefix for connection. If you want to use other connection you should specify 
the prefix of it as follows %jdbc(prefix):%jdbcSELECT * FROM 
db_name;or%jdbc(prefix)SELECT * FROM db_name;Apply Zeppelin Dynamic FormsYou 
can leverage Zeppelin Dynamic Form inside your queries. You ca
 n use both the text input and select form parametrization 
features%jdbc(prefix)SELECT name, country, performerFROM demo.performersWHERE 
name=&amp;#39;&amp;#39;Bugs &amp;amp; ReportingIf you find a bug for this 
interpreter, please create a JIRA ticket.",
       "url": " /interpreter/jdbc.html",
       "group": "interpreter",
       "excerpt": "Generic JDBC Interpreter lets you create a JDBC connection 
to any data source. You can use Postgres, MySql, MariaDB, Redshift, Apache 
Hive, Apache Phoenix, Apache Drill and Apache Tajo using JDBC interpreter."
@@ -523,7 +523,7 @@
 
     "/rss.xml": {
       "title": "RSS Feed",
-      "content"  : "        Apache Zeppelin        Apache Zeppelin - The 
Apache Software Foundation        http://zeppelin.apache.org        
http://zeppelin.apache.org        2016-09-27T12:46:46+09:00        
2016-09-27T12:46:46+09:00        1800",
+      "content"  : "        Apache Zeppelin        Apache Zeppelin - The 
Apache Software Foundation        http://zeppelin.apache.org        
http://zeppelin.apache.org        2016-09-28T12:58:09+09:00        
2016-09-28T12:58:09+09:00        1800",
       "url": " /rss.xml",
       "group": "",
       "excerpt": ""


Reply via email to