zeppelin-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From m...@apache.org
Subject svn commit: r1717006 - in /incubator/zeppelin/site/docs/0.6.0-incubating-SNAPSHOT: atom.xml interpreter/geode.html interpreter/postgresql.html rss.xml
Date Sat, 28 Nov 2015 22:23:09 GMT
Author: moon
Date: Sat Nov 28 22:23:09 2015
New Revision: 1717006

URL: http://svn.apache.org/viewvc?rev=1717006&view=rev
Log:
ZEPPELIN-466, ZEPPELIN-461 fix typos

Modified:
    incubator/zeppelin/site/docs/0.6.0-incubating-SNAPSHOT/atom.xml
    incubator/zeppelin/site/docs/0.6.0-incubating-SNAPSHOT/interpreter/geode.html
    incubator/zeppelin/site/docs/0.6.0-incubating-SNAPSHOT/interpreter/postgresql.html
    incubator/zeppelin/site/docs/0.6.0-incubating-SNAPSHOT/rss.xml

Modified: incubator/zeppelin/site/docs/0.6.0-incubating-SNAPSHOT/atom.xml
URL: http://svn.apache.org/viewvc/incubator/zeppelin/site/docs/0.6.0-incubating-SNAPSHOT/atom.xml?rev=1717006&r1=1717005&r2=1717006&view=diff
==============================================================================
--- incubator/zeppelin/site/docs/0.6.0-incubating-SNAPSHOT/atom.xml (original)
+++ incubator/zeppelin/site/docs/0.6.0-incubating-SNAPSHOT/atom.xml Sat Nov 28 22:23:09 2015
@@ -4,7 +4,7 @@
  <title>Apache Zeppelin (incubating)</title>
  <link href="http://zeppelin.incubator.apache.org/" rel="self"/>
  <link href="http://zeppelin.incubator.apache.org"/>
- <updated>2015-11-27T22:15:24+09:00</updated>
+ <updated>2015-11-29T07:22:53+09:00</updated>
  <id>http://zeppelin.incubator.apache.org</id>
  <author>
    <name>The Apache Software Foundation</name>

Modified: incubator/zeppelin/site/docs/0.6.0-incubating-SNAPSHOT/interpreter/geode.html
URL: http://svn.apache.org/viewvc/incubator/zeppelin/site/docs/0.6.0-incubating-SNAPSHOT/interpreter/geode.html?rev=1717006&r1=1717005&r2=1717006&view=diff
==============================================================================
--- incubator/zeppelin/site/docs/0.6.0-incubating-SNAPSHOT/interpreter/geode.html (original)
+++ incubator/zeppelin/site/docs/0.6.0-incubating-SNAPSHOT/interpreter/geode.html Sat Nov
28 22:23:09 2015
@@ -164,14 +164,14 @@ This interpreter supports the <a href="h
 
 <h3>Create Interpreter</h3>
 
-<p>By default Zeppelin creates one <code>Geode/OQL</code> instance. You
can remove it or create more instances. </p>
+<p>By default Zeppelin creates one <code>Geode/OQL</code> instance. You
can remove it or create more instances.</p>
 
-<p>Multiple Geode instances can be created, each configured to the same or different
backend Geode cluster. But over time a  <code>Notebook</code> can have only one
Geode interpreter instance <code>bound</code>. That means you <em>can not</em>
connect to different Geode clusters in the same <code>Notebook</code>. This is
a known Zeppelin limitation. </p>
+<p>Multiple Geode instances can be created, each configured to the same or different
backend Geode cluster. But over time a  <code>Notebook</code> can have only one
Geode interpreter instance <code>bound</code>. That means you <em>cannot</em>
connect to different Geode clusters in the same <code>Notebook</code>. This is
a known Zeppelin limitation.</p>
 
-<p>To create new Geode instance open the <code>Interprter</code> section
and click the <code>+Create</code> button. Pick a <code>Name</code>
of your choice and from the <code>Interpreter</code> drop-down select <code>geode</code>.
 Then follow the configuration instructions and <code>Save</code> the new instance.
</p>
+<p>To create new Geode instance open the <code>Interpreter</code> section
and click the <code>+Create</code> button. Pick a <code>Name</code>
of your choice and from the <code>Interpreter</code> drop-down select <code>geode</code>.
 Then follow the configuration instructions and <code>Save</code> the new instance.</p>
 
 <blockquote>
-<p>Note: The <code>Name</code> of the instance is used only to distinct
the instances while binding them to the <code>Notebook</code>. The <code>Name</code>
is irrelevant inside the <code>Notebook</code>. In the <code>Notebook</code>
you must use <code>%geode.oql</code> tag. </p>
+<p>Note: The <code>Name</code> of the instance is used only to distinguish
the instances while binding them to the <code>Notebook</code>. The <code>Name</code>
is irrelevant inside the <code>Notebook</code>. In the <code>Notebook</code>
you must use <code>%geode.oql</code> tag.</p>
 </blockquote>
 
 <h3>Bind to Notebook</h3>
@@ -180,7 +180,7 @@ This interpreter supports the <a href="h
 
 <h3>Configuration</h3>
 
-<p>You can modify the configuration of the Geode from the <code>Interpreter</code>
section.  The Geode interpreter express the following properties:</p>
+<p>You can modify the configuration of the Geode from the <code>Interpreter</code>
section.  The Geode interpreter expresses the following properties:</p>
 
 <p><table class="table-configuration">
    <tr>
@@ -210,12 +210,12 @@ This interpreter supports the <a href="h
 <blockquote>
 <p><em>Tip 1: Use (CTRL + .) for OQL auto-completion.</em></p>
 
-<p><em>Tip 2: Alawys start the paragraphs with the full <code>%geode.oql</code>
prefix tag! The short notation: <code>%geode</code> would still be able run the
OQL queries but the syntax highlighting and the auto-completions will be disabled.</em></p>
+<p><em>Tip 2: Always start the paragraphs with the full <code>%geode.oql</code>
prefix tag! The short notation: <code>%geode</code> would still be able run the
OQL queries but the syntax highlighting and the auto-completions will be disabled.</em></p>
 </blockquote>
 
 <h4>Create / Destroy Regions</h4>
 
-<p>The OQL sepecification does not support  <a href="https://cwiki.apache.org/confluence/display/GEODE/Index#Index-MainConceptsandComponents">Geode
Regions</a> mutation operations. To <code>creaate</code>/<code>destroy</code>
regions one should use the <a href="http://geode-docs.cfapps.io/docs/tools_modules/gfsh/chapter_overview.html">GFSH</a>
shell tool instead. To wokr this it assumes that the GFSH is colocated with Zeppelin server.</p>
+<p>The OQL specification does not support  <a href="https://cwiki.apache.org/confluence/display/GEODE/Index#Index-MainConceptsandComponents">Geode
Regions</a> mutation operations. To <code>create</code>/<code>destroy</code>
regions one should use the <a href="http://geode-docs.cfapps.io/docs/tools_modules/gfsh/chapter_overview.html">GFSH</a>
shell tool instead. In the following it is assumed that the GFSH is colocated with Zeppelin
server.</p>
 <div class="highlight"><pre><code class="bash language-bash" data-lang="bash">%sh
 <span class="nb">source</span> /etc/geode/conf/geode-env.sh
 gfsh <span class="s">&lt;&lt; EOF</span>
@@ -230,26 +230,26 @@ gfsh <span class="s">&lt;&lt; EOF</span>
 <span class="s"> exit;</span>
 <span class="s">EOF</span>
 </code></pre></div>
-<p>Above snippet re-creates two regions: <code>regionEmployee</code> and
<code>regionCompany</code>. Note that you have to explicetely specify the locator
host and port. The values should match those you have used in the Geode Interpreter configuration.
Comprehensive  list of <a href="http://geode-docs.cfapps.io/docs/tools_modules/gfsh/gfsh_quick_reference.html">GFSH
Commands by Functional Area</a>.</p>
+<p>Above snippet re-creates two regions: <code>regionEmployee</code> and
<code>regionCompany</code>. Note that you have to explicitly specify the locator
host and port. The values should match those you have used in the Geode Interpreter configuration.
Comprehensive list of <a href="http://geode-docs.cfapps.io/docs/tools_modules/gfsh/gfsh_quick_reference.html">GFSH
Commands by Functional Area</a>.</p>
 
 <h4>Basic OQL</h4>
-<div class="highlight"><pre><code class="sql language-sql" data-lang="sql"><span
class="o">%</span><span class="n">geode</span><span class="p">.</span><span
class="n">oql</span> 
-<span class="k">SELECT</span> <span class="k">count</span><span
class="p">(</span><span class="o">*</span><span class="p">)</span>
<span class="k">FROM</span> <span class="o">/</span><span class="n">regionEmploee</span>
+<div class="highlight"><pre><code class="sql language-sql" data-lang="sql"><span
class="o">%</span><span class="n">geode</span><span class="p">.</span><span
class="n">oql</span>
+<span class="k">SELECT</span> <span class="k">count</span><span
class="p">(</span><span class="o">*</span><span class="p">)</span>
<span class="k">FROM</span> <span class="o">/</span><span class="n">regionEmployee</span>
 </code></pre></div>
 <p>OQL <code>IN</code> and <code>SET</code> filters:</p>
 <div class="highlight"><pre><code class="sql language-sql" data-lang="sql"><span
class="o">%</span><span class="n">geode</span><span class="p">.</span><span
class="n">oql</span>
-<span class="k">SELECT</span> <span class="o">*</span> <span class="k">FROM</span>
<span class="o">/</span><span class="n">regionEmployee</span> 
+<span class="k">SELECT</span> <span class="o">*</span> <span class="k">FROM</span>
<span class="o">/</span><span class="n">regionEmployee</span>
 <span class="k">WHERE</span> <span class="n">companyId</span> <span
class="k">IN</span> <span class="k">SET</span><span class="p">(</span><span
class="mi">2</span><span class="p">)</span> <span class="k">OR</span>
<span class="n">lastName</span> <span class="k">IN</span> <span
class="k">SET</span><span class="p">(</span><span class="s1">&#39;Tzolov13&#39;</span><span
class="p">,</span> <span class="s1">&#39;Tzolov73&#39;</span><span
class="p">)</span>
 </code></pre></div>
 <p>OQL <code>JOIN</code> operations</p>
 <div class="highlight"><pre><code class="sql language-sql" data-lang="sql"><span
class="o">%</span><span class="n">geode</span><span class="p">.</span><span
class="n">oql</span>
 <span class="k">SELECT</span> <span class="n">e</span><span class="p">.</span><span
class="n">employeeId</span><span class="p">,</span> <span class="n">e</span><span
class="p">.</span><span class="n">firstName</span><span class="p">,</span>
<span class="n">e</span><span class="p">.</span><span class="n">lastName</span><span
class="p">,</span> <span class="k">c</span><span class="p">.</span><span
class="n">id</span> <span class="k">as</span> <span class="n">companyId</span><span
class="p">,</span> <span class="k">c</span><span class="p">.</span><span
class="n">companyName</span><span class="p">,</span> <span class="k">c</span><span
class="p">.</span><span class="n">address</span>
-<span class="k">FROM</span> <span class="o">/</span><span class="n">regionEmployee</span>
<span class="n">e</span><span class="p">,</span> <span class="o">/</span><span
class="n">regionCompany</span> <span class="k">c</span> 
+<span class="k">FROM</span> <span class="o">/</span><span class="n">regionEmployee</span>
<span class="n">e</span><span class="p">,</span> <span class="o">/</span><span
class="n">regionCompany</span> <span class="k">c</span>
 <span class="k">WHERE</span> <span class="n">e</span><span class="p">.</span><span
class="n">companyId</span> <span class="o">=</span> <span class="k">c</span><span
class="p">.</span><span class="n">id</span>
 </code></pre></div>
-<p>By default the QOL responses contain only the region entry values. To access the
keys,  query the <code>EntrySet</code> instead:</p>
+<p>By default the QOL responses contain only the region entry values. To access the
keys, query the <code>EntrySet</code> instead:</p>
 <div class="highlight"><pre><code class="sql language-sql" data-lang="sql"><span
class="o">%</span><span class="n">geode</span><span class="p">.</span><span
class="n">oql</span>
-<span class="k">SELECT</span> <span class="n">e</span><span class="p">.</span><span
class="k">key</span><span class="p">,</span> <span class="n">e</span><span
class="p">.</span><span class="n">value</span><span class="p">.</span><span
class="n">companyId</span><span class="p">,</span> <span class="n">e</span><span
class="p">.</span><span class="n">value</span><span class="p">.</span><span
class="n">email</span> 
+<span class="k">SELECT</span> <span class="n">e</span><span class="p">.</span><span
class="k">key</span><span class="p">,</span> <span class="n">e</span><span
class="p">.</span><span class="n">value</span><span class="p">.</span><span
class="n">companyId</span><span class="p">,</span> <span class="n">e</span><span
class="p">.</span><span class="n">value</span><span class="p">.</span><span
class="n">email</span>
 <span class="k">FROM</span> <span class="o">/</span><span class="n">regionEmployee</span><span
class="p">.</span><span class="n">entrySet</span> <span class="n">e</span>
 </code></pre></div>
 <p>Following query will return the EntrySet value as a Blob:</p>
@@ -269,7 +269,7 @@ gfsh -e <span class="s2">&quot;connect&q
 </code></pre></div>
 <h4>Apply Zeppelin Dynamic Forms</h4>
 
-<p>You can leverage <a href="https://zeppelin.incubator.apache.org/docs/manual/dynamicform.html">Zepplein
Dynamic Form</a> inside your OQL queries. You can use both the <code>text input</code>
and <code>select form</code> parametrization features</p>
+<p>You can leverage <a href="../manual/dynamicform.html">Zeppelin Dynamic Form</a>
inside your OQL queries. You can use both the <code>text input</code> and <code>select
form</code> parameterization features</p>
 <div class="highlight"><pre><code class="sql language-sql" data-lang="sql"><span
class="o">%</span><span class="n">geode</span><span class="p">.</span><span
class="n">oql</span>
 <span class="k">SELECT</span> <span class="o">*</span> <span class="k">FROM</span>
<span class="o">/</span><span class="n">regionEmployee</span> <span
class="n">e</span> <span class="k">WHERE</span> <span class="n">e</span><span
class="p">.</span><span class="n">employeeId</span> <span class="o">&gt;</span>
<span class="err">${</span><span class="n">Id</span><span class="err">}</span>
 </code></pre></div>
@@ -299,7 +299,7 @@ start-dev-rest-api=true
 </code></pre></div>
 <h3>Auto-completion</h3>
 
-<p>The Geode Interpreter provides a basic auto-completion functionality. On <code>(Ctrl+.)</code>
it list the most relevant suggesntions in a pop-up window. </p>
+<p>The Geode Interpreter provides a basic auto-completion functionality. On <code>(Ctrl+.)</code>
it list the most relevant suggestions in a pop-up window.</p>
 
   </div>
 </div>

Modified: incubator/zeppelin/site/docs/0.6.0-incubating-SNAPSHOT/interpreter/postgresql.html
URL: http://svn.apache.org/viewvc/incubator/zeppelin/site/docs/0.6.0-incubating-SNAPSHOT/interpreter/postgresql.html?rev=1717006&r1=1717005&r2=1717006&view=diff
==============================================================================
--- incubator/zeppelin/site/docs/0.6.0-incubating-SNAPSHOT/interpreter/postgresql.html (original)
+++ incubator/zeppelin/site/docs/0.6.0-incubating-SNAPSHOT/interpreter/postgresql.html Sat
Nov 28 22:23:09 2015
@@ -142,7 +142,7 @@
   <tr>
     <td>%psql.sql</td>
     <td>PostgreSqlInterpreter</td>
-    <td>Provides SQL environment for Postgresql, HAWQ and Greenplum</td>
+    <td>Provides SQL environment for PostgreSQL, HAWQ and Greenplum</td>
   </tr>
 </table></p>
 
@@ -152,8 +152,8 @@
 <p>This interpreter seamlessly supports the following SQL data processing engines:</p>
 
 <ul>
-<li><a href="http://www.postgresql.org/">PostgreSQL</a> - OSS, Object-relational
database management system (ORDBMS) </li>
-<li><a href="http://pivotal.io/big-data/pivotal-hawq">Apache HAWQ</a> -
Powerful <a href="https://wiki.apache.org/incubator/HAWQProposal">Open Source</a>
SQL-On-Hadoop engine. </li>
+<li><a href="http://www.postgresql.org/">PostgreSQL</a> - OSS, Object-relational
database management system (ORDBMS)</li>
+<li><a href="http://pivotal.io/big-data/pivotal-hawq">Apache HAWQ</a> -
Powerful <a href="https://wiki.apache.org/incubator/HAWQProposal">Open Source</a>
SQL-On-Hadoop engine.</li>
 <li><a href="http://pivotal.io/big-data/pivotal-greenplum-database">Greenplum</a>
- MPP database built on open source PostgreSQL.</li>
 </ul>
 
@@ -161,14 +161,14 @@
 
 <h3>Create Interpreter</h3>
 
-<p>By default Zeppelin creates one <code>PSQL</code> instance. You can
remove it or create new instances. </p>
+<p>By default Zeppelin creates one <code>PSQL</code> instance. You can
remove it or create new instances.</p>
 
-<p>Multiple PSQL instances can be created, each configured to the same or different
backend databases. But over time a  <code>Notebook</code> can have only one PSQL
interpreter instance <code>bound</code>. That means you <em>can not</em>
connect to different databases in the same <code>Notebook</code>. This is a known
Zeppelin limitation. </p>
+<p>Multiple PSQL instances can be created, each configured to the same or different
backend databases. But over time a  <code>Notebook</code> can have only one PSQL
interpreter instance <code>bound</code>. That means you <em>cannot</em>
connect to different databases in the same <code>Notebook</code>. This is a known
Zeppelin limitation.</p>
 
-<p>To create new PSQL instance open the <code>Interprter</code> section
and click the <code>+Create</code> button. Pick a <code>Name</code>
of your choice and from the <code>Interpreter</code> drop-down select <code>psql</code>.
 Then follow the configuration instructions and <code>Save</code> the new instance.
</p>
+<p>To create new PSQL instance open the <code>Interpreter</code> section
and click the <code>+Create</code> button. Pick a <code>Name</code>
of your choice and from the <code>Interpreter</code> drop-down select <code>psql</code>.
 Then follow the configuration instructions and <code>Save</code> the new instance.</p>
 
 <blockquote>
-<p>Note: The <code>Name</code> of the instance is used only to distinct
the instances while binding them to the <code>Notebook</code>. The <code>Name</code>
is irrelevant inside the <code>Notebook</code>. In the <code>Notebook</code>
you must use <code>%psql.sql</code> tag. </p>
+<p>Note: The <code>Name</code> of the instance is used only to distinct
the instances while binding them to the <code>Notebook</code>. The <code>Name</code>
is irrelevant inside the <code>Notebook</code>. In the <code>Notebook</code>
you must use <code>%psql.sql</code> tag.</p>
 </blockquote>
 
 <h3>Bind to Notebook</h3>
@@ -217,7 +217,7 @@
 </code></pre></div>
 <h4>DDL and SQL commands</h4>
 
-<p>Start the paragraphs with the full <code>%psql.sql</code> prefix tag!
The short notation: <code>%psql</code> would still be able run the queries but
the syntax highlighting and the auto-completions will be disabled. </p>
+<p>Start the paragraphs with the full <code>%psql.sql</code> prefix tag!
The short notation: <code>%psql</code> would still be able run the queries but
the syntax highlighting and the auto-completions will be disabled.</p>
 
 <p>You can use the standard CREATE / DROP / INSERT commands to create or modify the
data model:</p>
 <div class="highlight"><pre><code class="sql language-sql" data-lang="sql"><span
class="o">%</span><span class="n">psql</span><span class="p">.</span><span
class="k">sql</span>
@@ -260,12 +260,12 @@ psql -h phd3.localdomain -U gpadmin -p 5
 </code></pre></div>
 <h4>Apply Zeppelin Dynamic Forms</h4>
 
-<p>You can leverage <a href="https://zeppelin.incubator.apache.org/docs/manual/dynamicform.html">Zepplein
Dynamic Form</a> inside your queries. You can use both the <code>text input</code>
and <code>select form</code> parametrization features</p>
+<p>You can leverage <a href="../manual/dynamicform.html">Zeppelin Dynamic Form</a>
inside your queries. You can use both the <code>text input</code> and <code>select
form</code> parametrization features</p>
 <div class="highlight"><pre><code class="sql language-sql" data-lang="sql"><span
class="o">%</span><span class="n">psql</span><span class="p">.</span><span
class="k">sql</span>
-<span class="k">SELECT</span> <span class="err">${</span><span
class="n">group_by</span><span class="err">}</span><span class="p">,</span>
<span class="k">count</span><span class="p">(</span><span class="o">*</span><span
class="p">)</span> <span class="k">as</span> <span class="k">count</span>

-<span class="k">FROM</span> <span class="n">retail_demo</span><span
class="p">.</span><span class="n">order_lineitems_pxf</span> 
-<span class="k">GROUP</span> <span class="k">BY</span> <span class="err">${</span><span
class="n">group_by</span><span class="o">=</span><span class="n">product_id</span><span
class="p">,</span><span class="n">product_id</span><span class="o">|</span><span
class="n">product_name</span><span class="o">|</span><span class="n">customer_id</span><span
class="o">|</span><span class="n">store_id</span><span class="err">}</span>

-<span class="k">ORDER</span> <span class="k">BY</span> <span class="k">count</span>
<span class="err">${</span><span class="k">order</span><span class="o">=</span><span
class="k">DESC</span><span class="p">,</span><span class="k">DESC</span><span
class="o">|</span><span class="k">ASC</span><span class="err">}</span>

+<span class="k">SELECT</span> <span class="err">${</span><span
class="n">group_by</span><span class="err">}</span><span class="p">,</span>
<span class="k">count</span><span class="p">(</span><span class="o">*</span><span
class="p">)</span> <span class="k">as</span> <span class="k">count</span>
+<span class="k">FROM</span> <span class="n">retail_demo</span><span
class="p">.</span><span class="n">order_lineitems_pxf</span>
+<span class="k">GROUP</span> <span class="k">BY</span> <span class="err">${</span><span
class="n">group_by</span><span class="o">=</span><span class="n">product_id</span><span
class="p">,</span><span class="n">product_id</span><span class="o">|</span><span
class="n">product_name</span><span class="o">|</span><span class="n">customer_id</span><span
class="o">|</span><span class="n">store_id</span><span class="err">}</span>
+<span class="k">ORDER</span> <span class="k">BY</span> <span class="k">count</span>
<span class="err">${</span><span class="k">order</span><span class="o">=</span><span
class="k">DESC</span><span class="p">,</span><span class="k">DESC</span><span
class="o">|</span><span class="k">ASC</span><span class="err">}</span>
 <span class="k">LIMIT</span> <span class="err">${</span><span
class="k">limit</span><span class="o">=</span><span class="mi">10</span><span
class="err">}</span><span class="p">;</span>
 </code></pre></div>
 <h4>Example HAWQ PXF/HDFS Tables</h4>
@@ -279,11 +279,11 @@ psql -h phd3.localdomain -U gpadmin -p 5
 </code></pre></div>
 <p>And retrieve content</p>
 <div class="highlight"><pre><code class="sql language-sql" data-lang="sql"><span
class="o">%</span><span class="n">psql</span><span class="p">.</span><span
class="k">sql</span>
-<span class="n">seelect</span> <span class="o">*</span> <span
class="k">from</span> <span class="n">retail_demo</span><span class="p">.</span><span
class="n">payment_methods_pxf</span>
+<span class="k">select</span> <span class="o">*</span> <span class="k">from</span>
<span class="n">retail_demo</span><span class="p">.</span><span
class="n">payment_methods_pxf</span>
 </code></pre></div>
 <h3>Auto-completion</h3>
 
-<p>The PSQL Interpreter provides a basic auto-completion functionality. On <code>(Ctrl+.)</code>
it list the most relevant suggesntions in a pop-up window. In addition to the SQL keyword
the interpter provides suggestions for the Schema, Table, Column names as well. </p>
+<p>The PSQL Interpreter provides a basic auto-completion functionality. On <code>(Ctrl+.)</code>
it list the most relevant suggestions in a pop-up window. In addition to the SQL keyword the
interpreter provides suggestions for the Schema, Table, Column names as well.</p>
 
   </div>
 </div>

Modified: incubator/zeppelin/site/docs/0.6.0-incubating-SNAPSHOT/rss.xml
URL: http://svn.apache.org/viewvc/incubator/zeppelin/site/docs/0.6.0-incubating-SNAPSHOT/rss.xml?rev=1717006&r1=1717005&r2=1717006&view=diff
==============================================================================
--- incubator/zeppelin/site/docs/0.6.0-incubating-SNAPSHOT/rss.xml (original)
+++ incubator/zeppelin/site/docs/0.6.0-incubating-SNAPSHOT/rss.xml Sat Nov 28 22:23:09 2015
@@ -5,8 +5,8 @@
         <description>Apache Zeppelin (incubating) - The Apache Software Foundation</description>
         <link>http://zeppelin.incubator.apache.org</link>
         <link>http://zeppelin.incubator.apache.org</link>
-        <lastBuildDate>2015-11-27T22:15:24+09:00</lastBuildDate>
-        <pubDate>2015-11-27T22:15:24+09:00</pubDate>
+        <lastBuildDate>2015-11-29T07:22:53+09:00</lastBuildDate>
+        <pubDate>2015-11-29T07:22:53+09:00</pubDate>
         <ttl>1800</ttl>
 
 



Mime
View raw message