This is an automated email from the ASF dual-hosted git repository.
dzamo pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/drill-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 3e6a18c Website update.
3e6a18c is described below
commit 3e6a18c80ddeb2ded5adeeee0e420cae29d3b84f
Author: James Turton <[email protected]>
AuthorDate: Fri Jun 4 16:59:52 2021 +0200
Website update.
---
README.md | 161 +++++++++++++++-
data/index.html | 4 +-
.../index.html | 30 +--
.../index.html | 206 ++-------------------
docs/rest-api-introduction/index.html | 78 +++++++-
docs/string-manipulation/index.html | 23 ++-
feed.xml | 48 ++---
7 files changed, 307 insertions(+), 243 deletions(-)
diff --git a/README.md b/README.md
index 0a10cba..f46f670 100644
--- a/README.md
+++ b/README.md
@@ -1,8 +1,157 @@
-# Apache Drill
-[](http://www.apache.org/licenses/LICENSE-2.0)
-The Apache Drill website is built using [Jekyll](http://jekyllrb.com/).
+The Apache Drill website is built using [Jekyll](http://jekyllrb.com/), from
Markdown sources in the
+[drill/gh-pages](https://github.com/apache/drill/tree/gh-pages branch of the
main Drill code repository.
+Changes made anywhere downstream of that will be lost in the next build and
deploy cycle.
-# Leave Me Alone
-Drill-site is automatically built from Markdown sources in the
[drill/gh-pages](https://github.com/apache/drill/tree/gh-pages) branch by
Jekyll CMS.
+To make documenation contributions easier, pull requests to the gh-pages
branch do not require any
+additional process, such as the creation of a JIRA ticket.
-⛔ **PLEASE DON'T CHANGE ANYTHING HERE** ⛔
+# Configuring env
+
+1. Install `ruby`
+2. Install `bundler` and `jekyll` `v3.9.0`:
+
+```
+gem install bundler jekyll:3.9.0
+```
+
+3. Install `jekyll-redirect-from` `v0.9.1`:
+
+```
+gem install jekyll-redirect-from:0.9.1
+```
+
+4. Install Python 3
+
+Please make sure that specific versions of libraries are installed since
building the site with other versions
+may cause some issues like including md document index into the references,
etc.
+
+## Note for existing contributors
+
+The software version numbers above underwent a major increase in 2020 and the
Markdown processor
+changed from Redcarpet to Kramdown. Please check the versions in your
environment if you're having
+trouble generating the site.
+
+# Documentation Guidelines
+
+The documentation pages are placed under `_docs`. You can modify existing .md
files, or you can create new .md files to add to the Apache Drill documentation
site. Create pull requests to submit your documentation updates. The Kramdown
Markdown processor employed by Jekyll supports [a dialect of
Markdown](https://kramdown.gettalong.org/quickref.html) which is a superset of
standard Markdown.
+
+## Creating New Markdown Files
+
+If you create new Markdown (.md) files, include the required YAML front matter
and name the file using the methods described in this section.
+
+The YAML front matter has three important parameters:
+
+- `title:` - This is the title of the page enclosed in quotation marks. Each
page must have a _unique_ title
+- `slug:` - Set this to the same value as `title`, it will be slugified
automatically by Jekyll.
+- `date:` - This field is needed for Jekyll to write a last-modified date.
Initially, leave this field blank.
+- `parent:` - This is the title of the page's parent page. It should be empty
for top-level sections/guides, and be identical to the title attribute of
another page in all other cases.
+
+The name of the file itself doesn't matter except for the alphanumeric order
of the filenames. Files that
+share the same parent are ordered alphanumerically. Note that the content of
parent files is ignored, so add an
+overview/introduction child when needed.
+
+Best practices:
+
+- Prefix the filenames with `010-foo.md`, `020-bar.md`, `030-baz.md`, etc.
This allows room to add files in-between
+ (eg, `005-qux.md`).
+- Use the slugified title as the filename. For example, if the title is
"Getting Started with
+ Drill", name the file `...-getting-started-with-drill.md`. If you're not
sure what the slug is, you should be
+ able to see it in the URL and then adjust (the URLs are auto-generated based
on the title attribute).
+
+# Developing and Previewing the Website
+
+To preview the website on your local machine:
+
+```bash
+jekyll build --config _config.yml,_config-prod.yml
+_tools/createdatadocs.py
+jekyll serve --config _config.yml,_config-prod.yml [--livereload]
[--incremental]
+```
+
+Note that you can skip the first two commands (and only run `jekyll serve`) if
you haven't changed the title or
+path of any of the documentation pages.
+
+## One Time Setup for Last-Modified-Date
+
+To automatically add the `last-modified-on date`, a one-time local setup is
required:
+
+1. In your cloned directory of Drill, in `drill/.git/hooks`, create a file
named `pre-commit` (no extension) that contains this script:
+
+```
+#!/bin/sh
+# Contents of .git/hooks/pre-commit
+
+git diff --cached --name-status | grep "^M" | while read a b; do
+ cat $b | sed "/---.*/,/---.*/s/^date:.*$/date: $(date -u "+%Y-%m-%d")/" > tmp
+ mv tmp $b
+ git add $b
+done
+```
+
+2. Make the file executable.
+
+```
+chmod +x pre-commit
+```
+
+On the page you create, in addition to the title, and `parent:`, you now need
to add `date:` to the front matter of any file you create. For example:
+
+```
+---
+title: "Configuring Multitenant Resources"
+parent: "Configuring a Multitenant Cluster"
+date:
+---
+```
+
+Do not fill in or alter the date: field. Jekyll and git take care of that when
you commit the file.
+
+## One Time Setup for Redirecting gh-pages
+
+Locally install the `jekyll-redirect-from` gem:
+
+```
+gem install jekyll-redirect-from
+```
+
+On any page you want to redirect, add the redirect_to: and the URL to the
front matter. For example:
+
+```
+---
+title: "Configuring Multitenant Resources"
+parent: "Configuring a Multitenant Cluster"
+date:
+redirect_to:
+ - http://<new_url>
+---
+```
+
+# Compiling the Website
+
+Once the website is ready, you'll need to compile the site to static HTML so
that it can then be published to Apache. This is as simple as running the
`jekyll build` command. The `_config-prod.yml` configuration file causes a few
changes to the site:
+
+- The `noindex` meta tag is removed. We want the production site to be indexed
by search engines, but we don't want the staging site to be indexed.
+- The base URL is set to `/`. The production site is at `/`, whereas the
staging site is at `/drill` (convenient for previewing on GitHub Pages:
<http://apache.github.io/drill>).
+
+```bash
+jekyll build --config _config.yml,_config-prod.yml
+_tools/createdatadocs.py
+jekyll serve --config _config.yml,_config-prod.yml
+```
+
+# Uploading to the Apache Website (Drill Committers Only)
+
+Apache project websites use a system called svnpubsub for publishing.
Basically, the static HTML needs to be pushed by one of the committers into the
Apache SVN.
+
+```bash
+git clone -b asf-site https://gitbox.apache.org/repos/asf/drill-site.git
../drill-site
+rm -rf ../drill-site/*
+cp -R _site/* ../drill-site/
+cd ../drill-site
+git status
+git add *
+git commit -m "Website update"
+git push
+```
+
+The updates should then be live: <http://drill.apache.org>.
diff --git a/data/index.html b/data/index.html
index 01a03a6..079e485 100644
--- a/data/index.html
+++ b/data/index.html
@@ -2046,8 +2046,8 @@
"relative_path":
"_docs/sql-reference/sql-functions/090-time-series-analysis-functions.md"
},
{
- "url": "/docs/ip-network-functions/",
- "title": "IP Network functions",
+ "url": "/docs/ip-networking-functions/",
+ "title": "IP Networking functions",
"parent": "SQL Functions",
"relative_path":
"_docs/sql-reference/sql-functions/100-ip-net-functions.md"
},
diff --git a/docs/apache-drill-contribution-guidelines/index.html
b/docs/apache-drill-contribution-guidelines/index.html
index a8bba04..5172a55 100644
--- a/docs/apache-drill-contribution-guidelines/index.html
+++ b/docs/apache-drill-contribution-guidelines/index.html
@@ -1421,7 +1421,7 @@ Drill. For ideas about <em>what</em> you might
contribute, please see open ticke
<h2 id="step-2-get-approval-and-modify-the-source-code">Step 2: Get approval
and modify the source code.</h2>
-<p>Before you start, send a message to the <a
href="http://mail-archives.apache.org/mod_mbox/drill-dev/";>Drill developer
mailing list</a> or file a bug report in <a
href="https://issues.apache.org/jira/browse/DRILL";>JIRA</a> describing your
proposed changes. Doing this helps to verify that your changes will work with
what others are doing and have planned for the project. Be patient, it may take
folks a while to understand your requirements. For detailed designs, the Drill
team uses <a h [...]
+<p>Before you start, send a message to the <a
href="https://mail-archives.apache.org/mod_mbox/drill-dev/";>Drill developer
mailing list</a> or file a bug report in <a
href="https://issues.apache.org/jira/browse/DRILL";>JIRA</a> describing your
proposed changes. Doing this helps to verify that your changes will work with
what others are doing and have planned for the project. Be patient, it may take
folks a while to understand your requirements. For detailed designs, the Drill
team uses <a [...]
<p>Once your suggested changes are approved, you can modify the source code
and add some features using your favorite IDE.</p>
@@ -1432,8 +1432,8 @@ Drill. For ideas about <em>what</em> you might
contribute, please see open ticke
<p>Please adhere to the points outlined below:</p>
<ul>
- <li>All public classes and methods should have informative <a
href="http://www.oracle.com/technetwork/java/javase/documentation/index-137868.html";>Javadoc
comments</a>. Do not use @author tags.</li>
- <li>Code should be formatted according to <a
href="http://www.oracle.com/technetwork/java/codeconvtoc-136057.html";>Sun’s
conventions</a>, with the following exceptions:
+ <li>All public classes and methods should have informative <a
href="https://www.oracle.com/technical-resources/articles/java/javadoc-tool.html";>Javadoc
comments</a>. Do not use @author tags.</li>
+ <li>Code should be formatted according to <a
href="https://www.oracle.com/java/technologies/javase/codeconventions-contents.html";>Sun’s
conventions</a>, with the following exceptions:
<ul>
<li>Indent two (2) spaces per level, not four (4).</li>
<li>Line length limit is 120 chars, instead of 80 chars.</li>
@@ -1441,7 +1441,7 @@ Drill. For ideas about <em>what</em> you might
contribute, please see open ticke
</li>
<li>Contributions should not introduce new Checkstyle violations.</li>
<li>Contributions should pass existing unit tests.</li>
- <li>New unit tests should be provided to demonstrate bugs and fixes. <a
href="http://www.junit.org";>JUnit</a> 4.1 is our test framework which has the
following requirements:
+ <li>New unit tests should be provided to demonstrate bugs and fixes. <a
href="https://junit.org/junit4/";>JUnit</a> 4.12 is our test framework which has
the following requirements:
<ul>
<li>You must implement a class that contains test methods annotated with
JUnit’s 4.x @Test annotation and whose class name ends with <code
class="language-plaintext highlighter-rouge">Test</code>.</li>
<li>Define methods within your class whose names begin with <code
class="language-plaintext highlighter-rouge">test</code>, and call JUnit’s many
assert methods to verify conditions; these methods will be executed when you
run <code class="language-plaintext highlighter-rouge">mvn clean
test</code>.</li>
@@ -1460,7 +1460,7 @@ following settings into your browser:</p>
<h3 id="understanding-maven">Understanding Maven</h3>
-<p>You can use the Maven Java build tool to build Drill. To get started with
Maven, see the <a
href="http://maven.apache.org/guides/getting-started/maven-in-five-minutes.html";>Maven
tutorial</a>.</p>
+<p>You can use the Maven Java build tool to build Drill. To get started with
Maven, see the <a
href="https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html";>Maven
tutorial</a>.</p>
<p>To build Drill with Maven, run the following command:</p>
@@ -1481,10 +1481,10 @@ following settings into your browser:</p>
<ol>
<li>The contributor writes the code that addresses a specific JIRA report as
a contribution to the Apache Drill project.</li>
<li>The contributor organizes (squashes) their code into commits that
segregate out refactoring/reorg, as necessary, to enable efficient review. The
following list identifies how to combine code into commits:<br />
- * Combine WIP and other small commits together.
- * Address multiple JIRAs, for smaller bug fixes or enhancements, with a
single commit.
- * Use separate commits to allow efficient review, separating out
formatting changes or simple refactoring from core changes or additions.
- * Rebase this chain of commits on top of the current master.</li>
+ * Combine WIP and other small commits together.
+ * Address multiple JIRAs, for smaller bug fixes or enhancements, with a
single commit.
+ * Use separate commits to allow efficient review, separating out
formatting changes or simple refactoring from core changes or additions.
+ * Rebase this chain of commits on top of the current master.</li>
</ol>
<div class="admonition note">
<p class="first admonition-title">Note</p>
@@ -1518,6 +1518,14 @@ This information can be found in the <a
href="https://issues.apache.org/jira/bro
</li>
</ol>
+<h3 id="continuous-integration">Continuous Integration</h3>
+
+<p>All Pull requests at Github are automatically tested:</p>
+<ul>
+ <li>On Linux x86_64 at <a
href="https://github.com/apache/drill/actions";>Github Actions</a> with JDK 8,
11 and 14</li>
+ <li>on Linux ARM64 at <a
href="https://travis-ci.com/github/apache/drill";>Travis CI</a> with JDK 8</li>
+</ul>
+
<h2 id="additional-information">Additional Information</h2>
<h3 id="where-is-a-good-place-to-start-contributing">Where is a good place to
start contributing?</h3>
@@ -1570,8 +1578,8 @@ markdown or plain text and the committer can incorporate
it with little bureaocr
<h3 id="see-also">See Also</h3>
<ul>
- <li><a href="http://www.apache.org/dev/contributors.html";>Apache contributor
documentation</a></li>
- <li><a href="http://www.apache.org/foundation/voting.html";>Apache voting
documentation</a></li>
+ <li><a href="https://infra.apache.org/contributors.html";>Apache contributor
documentation</a></li>
+ <li><a href="https://www.apache.org/foundation/voting.html";>Apache voting
documentation</a></li>
</ul>
diff --git a/docs/apache-drill-contribution-guidelines/index.html
b/docs/ip-networking-functions/index.html
similarity index 83%
copy from docs/apache-drill-contribution-guidelines/index.html
copy to docs/ip-networking-functions/index.html
index a8bba04..1cde91e 100644
--- a/docs/apache-drill-contribution-guidelines/index.html
+++ b/docs/ip-networking-functions/index.html
@@ -7,7 +7,7 @@
<meta name=viewport content="width=device-width, initial-scale=1">
-<title>Apache Drill Contribution Guidelines - Apache Drill</title>
+<title>IP Networking functions - Apache Drill</title>
<link
href="//maxcdn.bootstrapcdn.com/font-awesome/4.3.0/css/font-awesome.min.css"
rel="stylesheet" type="text/css"/>
<link href='//fonts.googleapis.com/css?family=PT+Sans' rel='stylesheet'
type='text/css'/>
@@ -1154,8 +1154,8 @@
- <li class="toctree-l1 current_section "><a href="javascript:
void(0);">Developer Information</a></li>
- <ul class="current_section">
+ <li class="toctree-l1"><a href="javascript: void(0);">Developer
Information</a></li>
+ <ul style="display: none">
<li class="toctree-l2"><a href="javascript: void(0);">REST
API</a></li>
@@ -1183,9 +1183,9 @@
<li class="toctree-l2"><a href="javascript: void(0);">Contribute
to Drill</a></li>
- <ul style="">
+ <ul style="display: none">
- <li class="toctree-l3 current"><a class="reference internal"
href="/docs/apache-drill-contribution-guidelines/">Apache Drill Contribution
Guidelines</a></li>
+ <li class="toctree-l3"><a class="reference internal"
href="/docs/apache-drill-contribution-guidelines/">Apache Drill Contribution
Guidelines</a></li>
<li class="toctree-l3"><a class="reference internal"
href="/docs/apache-drill-contribution-ideas/">Apache Drill Contribution
Ideas</a></li>
@@ -1368,22 +1368,18 @@
<li><a href="/docs/">Docs</a></li>
- <li><a href="/docs/developer-information/">Developer Information</a></li>
-
- <li><a href="/docs/contribute-to-drill/">Contribute to Drill</a></li>
-
- <li>Apache Drill Contribution Guidelines</li>
+ <li>IP Networking functions</li>
</nav>
<div class="main-content-wrapper">
<div class="main-content">
- <a class="edit-link"
href="https://github.com/apache/drill/blob/gh-pages/_docs/developer-information/contribute-to-drill/010-apache-drill-contribution-guidelines.md";
target="_blank"><i class="fa fa-pencil-square-o"></i></a>
+ <a class="edit-link"
href="https://github.com/apache/drill/blob/gh-pages/_docs/sql-reference/sql-functions/100-ip-net-functions.md";
target="_blank"><i class="fa fa-pencil-square-o"></i></a>
<div class="int_title left">
- <h1>Apache Drill Contribution Guidelines</h1>
+ <h1>IP Networking functions</h1>
</div>
@@ -1393,192 +1389,14 @@
<div class="int_text" align="left">
- <p>Disclaimer: These contribution guidelines are largely based on
Apache Hive
-contribution guidelines.</p>
-
-<p>This page describes the mechanics of <em>how</em> to contribute software to
Apache
-Drill. For ideas about <em>what</em> you might contribute, please see open
tickets in
-<a href="https://issues.apache.org/jira/browse/DRILL";>Jira</a>.</p>
-
-<h2 id="code-contribution-steps">Code Contribution Steps</h2>
-
-<p>The following steps outline the process for contributing code to the Apache
Drill project:</p>
-
-<ul>
- <li><a
href="/docs/apache-drill-contribution-guidelines/#step-1:-get-the-source-code.">Step
1: Get the source code.</a></li>
- <li><a
href="/docs/apache-drill-contribution-guidelines/#step-2:-get-approval-and-modify-the-source-code.">Step
2: Get approval and modify the source code.</a></li>
- <li><a
href="/docs/apache-drill-contribution-guidelines/#step-3:-get-your-code-reviewed-and-committed-to-the-project.">Step
3: Get your code reviewed and committed to the project. </a></li>
-</ul>
-
-<p>You may also be interested in the <a
href="/docs/apache-drill-contribution-guidelines/#additional-information">additional
information</a> at the end of this document.</p>
-
-<h2 id="step-1-get-the-source-code">Step 1: Get the source code.</h2>
-
-<p>First, you need the Drill source code. You can use Git to put the source
code on your local drive. Most development is done on “master.”</p>
-
-<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>git clone https://gitbox.apache.org/repos/asf/drill.git
-</code></pre></div></div>
-
-<h2 id="step-2-get-approval-and-modify-the-source-code">Step 2: Get approval
and modify the source code.</h2>
-
-<p>Before you start, send a message to the <a
href="http://mail-archives.apache.org/mod_mbox/drill-dev/";>Drill developer
mailing list</a> or file a bug report in <a
href="https://issues.apache.org/jira/browse/DRILL";>JIRA</a> describing your
proposed changes. Doing this helps to verify that your changes will work with
what others are doing and have planned for the project. Be patient, it may take
folks a while to understand your requirements. For detailed designs, the Drill
team uses <a h [...]
-
-<p>Once your suggested changes are approved, you can modify the source code
and add some features using your favorite IDE.</p>
-
-<p>The following sections provide tips for working on the project:</p>
-
-<h3 id="coding-convention">Coding Convention</h3>
-
-<p>Please adhere to the points outlined below:</p>
-
-<ul>
- <li>All public classes and methods should have informative <a
href="http://www.oracle.com/technetwork/java/javase/documentation/index-137868.html";>Javadoc
comments</a>. Do not use @author tags.</li>
- <li>Code should be formatted according to <a
href="http://www.oracle.com/technetwork/java/codeconvtoc-136057.html";>Sun’s
conventions</a>, with the following exceptions:
- <ul>
- <li>Indent two (2) spaces per level, not four (4).</li>
- <li>Line length limit is 120 chars, instead of 80 chars.</li>
- </ul>
- </li>
- <li>Contributions should not introduce new Checkstyle violations.</li>
- <li>Contributions should pass existing unit tests.</li>
- <li>New unit tests should be provided to demonstrate bugs and fixes. <a
href="http://www.junit.org";>JUnit</a> 4.1 is our test framework which has the
following requirements:
- <ul>
- <li>You must implement a class that contains test methods annotated with
JUnit’s 4.x @Test annotation and whose class name ends with <code
class="language-plaintext highlighter-rouge">Test</code>.</li>
- <li>Define methods within your class whose names begin with <code
class="language-plaintext highlighter-rouge">test</code>, and call JUnit’s many
assert methods to verify conditions; these methods will be executed when you
run <code class="language-plaintext highlighter-rouge">mvn clean
test</code>.</li>
- </ul>
- </li>
-</ul>
-
-<h3 id="formatter-configuration">Formatter Configuration</h3>
-
-<p>Setting up IDE formatters is recommended and can be done by importing the
-following settings into your browser:</p>
-
-<ul>
- <li><a
href="https://github.com/apache/drill/blob/master/dev-support/formatter";>Eclipse
and IntelliJ IDEA</a></li>
-</ul>
-
-<h3 id="understanding-maven">Understanding Maven</h3>
-
-<p>You can use the Maven Java build tool to build Drill. To get started with
Maven, see the <a
href="http://maven.apache.org/guides/getting-started/maven-in-five-minutes.html";>Maven
tutorial</a>.</p>
-
-<p>To build Drill with Maven, run the following command:</p>
-
-<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>mvn clean install
-</code></pre></div></div>
-
-<h2 id="step-3-get-your-code-reviewed-and-committed-to-the-project">Step 3:
Get your code reviewed and committed to the project.</h2>
-
-<p>This section describes the GitHub pull request-based review process for
Apache Drill.</p>
-
-<div class="admonition note">
- <p class="first admonition-title">Note</p>
- <p class="last">JIRA remains the primary site for discussions on issues. We
are not using the GitHub issue tracker. </p>
-</div>
-
-<p>The following steps outline the code review and commit process required to
contribute new code to the Apache Drill project:</p>
-
-<ol>
- <li>The contributor writes the code that addresses a specific JIRA report as
a contribution to the Apache Drill project.</li>
- <li>The contributor organizes (squashes) their code into commits that
segregate out refactoring/reorg, as necessary, to enable efficient review. The
following list identifies how to combine code into commits:<br />
- * Combine WIP and other small commits together.
- * Address multiple JIRAs, for smaller bug fixes or enhancements, with a
single commit.
- * Use separate commits to allow efficient review, separating out
formatting changes or simple refactoring from core changes or additions.
- * Rebase this chain of commits on top of the current master.</li>
-</ol>
-<div class="admonition note">
- <p class="first admonition-title">Note</p>
- <p class="last">The discussion that is automatically copied over from GitHub
adds the review process into the Apache infrastructure. The final commit ends
up in the Apache Git repo, which is the critical part. As such, there is no
requirement to have your intermediate work placed anywhere outside of the
GitHub pull request. </p>
-</div>
-<ol>
- <li>
- <p>The contributor opens a pull request against the GitHub mirror, based
on the branch that contains their work, which has been squashed together as
described in step 2.
- * Open the pull request against this repo: https://github.com/apache/drill/
- * Mention the JIRA number in the heading of the pull request, like
“DRILL-3000” to automatically link to JIRA.
- * For more information about pull requests, see <a
href="https://help.github.com/articles/using-pull-requests/";>Using Pull
Requests</a>.</p>
- </li>
- <li>The contributor asks a committer who has experience with the affected
component for review.
-This information can be found in the <a
href="https://issues.apache.org/jira/browse/DRILL/?selectedTab=com.atlassian.jira.jira-projects-plugin:components-panel";>component
owners</a> section of JIRA, or by running <code class="language-plaintext
highlighter-rouge">git blame</code> on the primary files changed in the pull
request. For pull requests that affect multiple areas, send a message to the
dev list to find a reviewer.</li>
- <li>The contributor sets the Reviewer field to the assigned reviewer and
marks the status as REVIEWABLE.</li>
- <li>The reviewer reviews the pull request in GitHub and adds comments or a
+1 to the general discussion if the pull request is ready to commit.<br />
- * If there are issues to address, the reviewer changes the JIRA status to
“In Progress.”
- * If the reviewer gives a +1, the reviewer adds a “ready-to-commit” label
to the Labels field in the Jira. The contributor should continue to step 9 in
this process.</li>
- <li>The contributor addresses review comments. This can be done with new
commits on the branch or with work made on the branch locally, squashed into
the commit(s) posted in the original pull request and force pushed to the
branch the pull request is based on.</li>
- <li>Return to step 5.</li>
- <li>
- <p>A Drill committer completes the following steps to commit the patch:
- * If the master branch has moved forward since the review, rebase the
branch from the pull request on the latest master and re-run tests.
- * If all tests pass, the committer amends the last commit message in the
series to include “this closes #1234”, where 1234 is the pull request number,
not the JIRA number. This can be done with interactive rebase. When on the
branch issue:</p>
-
- <div class="language-plaintext highlighter-rouge"><div
class="highlight"><pre class="highlight"><code> git rebase -i HEAD^
-* Change where it says “pick” on the line with the last commit, replacing it
with “r” or “reword”. It replays the commit giving you the opportunity the
change the commit message.
-* The committer pushes the commit(s) to the Apache repo (the GitHub repo is
just a read-only mirror).
-* The committer resolves the JIRA with a message like `"Fixed in <Git
commit SHA>"`.
-</code></pre></div> </div>
- </li>
-</ol>
-
-<h2 id="additional-information">Additional Information</h2>
-
-<h3 id="where-is-a-good-place-to-start-contributing">Where is a good place to
start contributing?</h3>
-
-<p>After getting the source code, building and running a few simple queries,
one
-of the simplest places to start is to implement a DrillFunc. DrillFuncs are
the way that Drill expresses all scalar functions (UDF or system).</p>
-
-<p>First you can put together a JIRA for one of the DrillFuncs that we don’t
yet have, but should (referencing the capabilities of something like
Postgres<br />
-or SQL Server). Then try to implement one.</p>
-
-<p>See this example DrillFunc:</p>
-
-<p><a
href="https://github.com/apache/drill/blob/3f93454f014196a4da198ce012b605b70081fde0/exec/java-exec/src/main/codegen/templates/ComparisonFunctions.java";>ComparisonFunctions.java</a></p>
-
-<p>Also, you can visit the JIRA issues and implement one of those too.</p>
-
-<p>More contribution ideas are located on the <a
href="/docs/apache-drill-contribution-ideas">Contribution Ideas</a> page.</p>
-
-<h3 id="what-are-the-jira-guidelines">What are the JIRA guidelines?</h3>
-
-<p>Please comment on issues in JIRA, making their concerns known. Please also
-vote for issues that are a high priority for you.</p>
-
-<p>Please refrain from editing descriptions and comments if possible, as edits
-spam the mailing list and clutter JIRA’s “All” display, which is otherwise
-very useful. Instead, preview descriptions and comments using the preview
-button (on the right) before posting them. Keep descriptions brief and save
-more elaborate proposals for comments, since descriptions are included in
-JIRA’s automatically sent messages. If you change your mind, note this in a
-new comment, rather than editing an older comment. The issue should preserve
-this history of the discussion.</p>
-
-<h3 id="contributing-documentation">Contributing documentation</h3>
-
-<p>Documentation contributions are most welcome and there are many
opportunities for them including</p>
-
-<ol>
- <li>features which have been implemented but not completely documented
and</li>
- <li>HOWTOs for using Drill with other popular software.</li>
-</ol>
-
-<p>Documentation committed into the <code class="language-plaintext
highlighter-rouge">gh-pages</code> branch does not have any effect on the Drill
code base and so does not require a JIRA ticket or a corresponding PR from a
repo fork. It does still require a Drill committer to check it and push it
into the Drill code repo. This means</p>
-
-<ol>
- <li>Drill committers can add documentation with little bureaocratic
overhead.</li>
- <li>Anyone can send documentation to a Drill committer (find us on Slack or
the mailing lists) as
-markdown or plain text and the committer can incorporate it with little
bureaocratic overhead.</li>
-</ol>
-
-<h3 id="see-also">See Also</h3>
-
-<ul>
- <li><a href="http://www.apache.org/dev/contributors.html";>Apache contributor
documentation</a></li>
- <li><a href="http://www.apache.org/foundation/voting.html";>Apache voting
documentation</a></li>
-</ul>
-
+ <ul>
+
+ </ul>
<div class="doc-nav">
- <span class="previous-toc"><a href="/docs/contribute-to-drill/">← Contribute
to Drill</a></span><span class="next-toc"><a
href="/docs/apache-drill-contribution-ideas/">Apache Drill Contribution Ideas
→</a></span>
+ <span class="previous-toc"><a href="">← </a></span><span class="next-toc"><a
href=""> →</a></span>
</div>
diff --git a/docs/rest-api-introduction/index.html
b/docs/rest-api-introduction/index.html
index 54399b9..f69ae0e 100644
--- a/docs/rest-api-introduction/index.html
+++ b/docs/rest-api-introduction/index.html
@@ -1454,11 +1454,14 @@
<p><strong>Parameters</strong></p>
<ul>
- <li>queryType–SQL, PHYSICAL, or LOGICAL are valid types. Use only “SQL”.
Other types are for internal use only.</li>
- <li>query–A SQL query that runs in Drill.</li>
- <li>autoLimit–Limits the number of rows returned from the result set. (Drill
1.16+)</li>
+ <li><code class="language-plaintext highlighter-rouge">queryType</code>–SQL,
PHYSICAL, or LOGICAL are valid types. Use only “SQL”. Other types are for
internal use only.</li>
+ <li><code class="language-plaintext highlighter-rouge">query</code>–A SQL
query that runs in Drill.</li>
+ <li><code class="language-plaintext
highlighter-rouge">autoLimit</code>–Limits the number of rows returned from the
result set. (Drill 1.16+)</li>
+ <li><code class="language-plaintext
highlighter-rouge">defaultSchema</code>–Sets the default schema for the query.
Equavalent to executing a <code class="language-plaintext
highlighter-rouge">USE <schema></code> prior to the query. (Drill
1.18+)</li>
</ul>
+<p>For Drill 1.19+ Drill switched to a streaming HTTP connection for REST
queries. The result being that</p>
+
<p><strong>Request Body</strong></p>
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code> {
@@ -1490,6 +1493,75 @@
}
</code></pre></div></div>
+<p><strong>Error Reporting</strong>
+Drill 1.19 added a streaming REST interface with the goal of reducing the
response times from REST calls. As of Drill 1.19, error reporting is no longer
enabled by default and in the event of a failed query, you will just get
results as shown below:</p>
+
+<div class="language-json highlighter-rouge"><div class="highlight"><pre
class="highlight"><code><span class="p">{</span><span class="w">
+ </span><span class="nl">"queryId"</span><span class="p">:</span><span
class="w"> </span><span
class="s2">"1fa0acc2-e507-6688-69fe-02fc627c8c47"</span><span
class="p">,</span><span class="w">
+ </span><span class="nl">"queryState"</span><span class="p">:</span><span
class="w"> </span><span class="s2">"FAILED"</span><span class="w">
+</span><span class="p">}</span><span class="w">
+</span></code></pre></div></div>
+<p>To re-enable error reporting you will have to set the <code
class="language-plaintext highlighter-rouge">http.rest.errors.verbose</code> to
<code class="language-plaintext highlighter-rouge">true</code> as shown
below:</p>
+
+<div class="language-json highlighter-rouge"><div class="highlight"><pre
class="highlight"><code><span class="p">{</span><span class="w">
+ </span><span class="nl">"query"</span><span class="p">:</span><span
class="w"> </span><span class="s2">"SELECT * FROM
cp.`employee123321123321.json` LIMIT 20"</span><span class="p">,</span><span
class="w">
+ </span><span class="nl">"queryType"</span><span class="p">:</span><span
class="w"> </span><span class="s2">"SQL"</span><span class="p">,</span><span
class="w">
+ </span><span class="nl">"options"</span><span class="p">:</span><span
class="w"> </span><span class="p">{</span><span class="w">
+ </span><span
class="nl">"drill.exec.http.rest.errors.verbose"</span><span
class="p">:</span><span class="w"> </span><span class="s2">"true"</span><span
class="w">
+ </span><span class="p">}</span><span class="w">
+</span><span class="p">}</span><span class="w">
+</span></code></pre></div></div>
+<p>The above call will result in the response shown below. Note that the
response will contain the <code class="language-plaintext
highlighter-rouge">exception</code>, the <code class="language-plaintext
highlighter-rouge">errorMessage</code> and the <code class="language-plaintext
highlighter-rouge">stackTrace</code> in separate fields.</p>
+
+<div class="language-json highlighter-rouge"><div class="highlight"><pre
class="highlight"><code><span class="p">{</span><span class="w">
+ </span><span class="nl">"queryId"</span><span class="p">:</span><span
class="w"> </span><span
class="s2">"1f9c72aa-bafb-2d58-ebfa-5cd3f21f4ddd"</span><span
class="p">,</span><span class="w">
+ </span><span class="nl">"exception"</span><span class="p">:</span><span
class="w"> </span><span
class="s2">"org.apache.calcite.runtime.CalciteContextException"</span><span
class="p">,</span><span class="w">
+ </span><span class="nl">"errorMessage"</span><span class="p">:</span><span
class="w"> </span><span class="s2">"From line 1, column 15 to line 1, column
16: Object 'employee123321123321.json' not found within 'cp': Object
'employee123321123321.json' not found within 'cp'"</span><span
class="p">,</span><span class="w">
+ </span><span class="nl">"stackTrace"</span><span class="p">:</span><span
class="w"> </span><span class="p">[</span><span class="w">
+ </span><span
class="s2">"org.apache.calcite.runtime.CalciteContextException: From line 1,
column 15 to line 1, column 16: Object 'employee123321123321.json' not found
within 'cp': Object 'employee123321123321.json' not found within
'cp'"</span><span class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at .......(:0)"</span><span class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.calcite.runtime.Resources$ExInstWithCause.ex(Resources.java:463)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.calcite.sql.SqlUtil.newContextException(SqlUtil.java:835)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.calcite.sql.SqlUtil.newContextException(SqlUtil.java:820)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.calcite.sql.validate.SqlValidatorImpl.newValidationError(SqlValidatorImpl.java:4881)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.calcite.sql.validate.IdentifierNamespace.resolveImpl(IdentifierNamespace.java:127)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.calcite.sql.validate.IdentifierNamespace.validateImpl(IdentifierNamespace.java:177)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.calcite.sql.validate.AbstractNamespace.validate(AbstractNamespace.java:84)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.calcite.sql.validate.SqlValidatorImpl.validateNamespace(SqlValidatorImpl.java:1009)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.calcite.sql.validate.SqlValidatorImpl.validateQuery(SqlValidatorImpl.java:969)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.calcite.sql.validate.SqlValidatorImpl.validateFrom(SqlValidatorImpl.java:3129)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.drill.exec.planner.sql.conversion.DrillValidator.validateFrom(DrillValidator.java:63)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.calcite.sql.validate.SqlValidatorImpl.validateFrom(SqlValidatorImpl.java:3111)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.drill.exec.planner.sql.conversion.DrillValidator.validateFrom(DrillValidator.java:63)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.calcite.sql.validate.SqlValidatorImpl.validateSelect(SqlValidatorImpl.java:3383)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.calcite.sql.validate.SelectNamespace.validateImpl(SelectNamespace.java:60)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.calcite.sql.validate.AbstractNamespace.validate(AbstractNamespace.java:84)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.calcite.sql.validate.SqlValidatorImpl.validateNamespace(SqlValidatorImpl.java:1009)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.calcite.sql.validate.SqlValidatorImpl.validateQuery(SqlValidatorImpl.java:969)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.calcite.sql.SqlSelect.validate(SqlSelect.java:216)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.calcite.sql.validate.SqlValidatorImpl.validateScopedExpression(SqlValidatorImpl.java:944)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.calcite.sql.validate.SqlValidatorImpl.validate(SqlValidatorImpl.java:651)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.drill.exec.planner.sql.conversion.SqlConverter.validate(SqlConverter.java:189)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.drill.exec.planner.sql.handlers.DefaultSqlHandler.validateNode(DefaultSqlHandler.java:641)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.drill.exec.planner.sql.handlers.DefaultSqlHandler.validateAndConvert(DefaultSqlHandler.java:195)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.drill.exec.planner.sql.handlers.DefaultSqlHandler.getPlan(DefaultSqlHandler.java:169)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.drill.exec.planner.sql.DrillSqlWorker.getQueryPlan(DrillSqlWorker.java:283)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.drill.exec.planner.sql.DrillSqlWorker.getPhysicalPlan(DrillSqlWorker.java:163)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.drill.exec.planner.sql.DrillSqlWorker.convertPlan(DrillSqlWorker.java:128)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.drill.exec.planner.sql.DrillSqlWorker.getPlan(DrillSqlWorker.java:93)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.drill.exec.work.foreman.Foreman.runSQL(Foreman.java:592)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.drill.exec.work.foreman.Foreman.run(Foreman.java:273)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at .......(:0)"</span><span class="p">,</span><span class="w">
+ </span><span class="s2">"Caused by:
org.apache.calcite.sql.validate.SqlValidatorException: Object
'employee123321123321.json' not found within 'cp'"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at .......(:0)"</span><span class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.calcite.runtime.Resources$ExInstWithCause.ex(Resources.java:463)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">at
org.apache.calcite.runtime.Resources$ExInst.ex(Resources.java:572)"</span><span
class="p">,</span><span class="w">
+ </span><span class="s2">"</span><span class="se">\t</span><span
class="s2">... 31 more"</span><span class="w">
+ </span><span class="p">],</span><span class="w">
+ </span><span class="nl">"queryState"</span><span class="p">:</span><span
class="w"> </span><span class="s2">"FAILED"</span><span class="w">
+</span><span class="p">}</span><span class="w">
+</span></code></pre></div></div>
+
<h2 id="profiles">Profiles</h2>
<p>These methods get query profiles.</p>
diff --git a/docs/string-manipulation/index.html
b/docs/string-manipulation/index.html
index 24377a8..6a368bb 100644
--- a/docs/string-manipulation/index.html
+++ b/docs/string-manipulation/index.html
@@ -2020,14 +2020,15 @@ SELECT RTRIM('1.0 Apache Tomcat 1.0', 'Drill 1.0') from
(VALUES(1));
</code></pre></div></div>
<h2 id="split_part">SPLIT_PART</h2>
-<p>Return the string part at <em>index</em> after splitting the input string
using the specified delimiter.</p>
+<p>Return the string part at <em>start</em> or from <em>start</em> to
<em>end</em> after splitting the input string using the specified delimiter.</p>
<h3 id="split_part-syntax">SPLIT_PART Syntax</h3>
-<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>SPLIT_PART(string, delimiter, index)
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>SPLIT_PART(string, delimiter, start[, end])
</code></pre></div></div>
<h3 id="split_part-usage-notes">SPLIT_PART Usage Notes</h3>
-<p>The <em>delimiter</em> string may be multiple characters long. The
<em>index</em> must be a positive integer.</p>
+<p>The <em>delimiter</em> string may be multiple characters long. The
<em>start</em> must be a positive integer.
+The <em>end</em> must be greater than or equal to <em>start</em> if
provided.</p>
<h3 id="split_part-examples">SPLIT_PART Examples</h3>
@@ -2038,6 +2039,22 @@ SELECT RTRIM('1.0 Apache Tomcat 1.0', 'Drill 1.0') from
(VALUES(1));
|--------|
| fox |
|--------|
+
+SELECT split_part('The | quick | brown | fox | jumps', ' | ', 4, 5);
+
+|--------------|
+| EXPR$0 |
+|--------------|
+| fox | jumps |
+|--------------|
+
+SELECT split_part('The | quick | brown | fox | jumps', ' | ', 4, 10);
+
+|--------------|
+| EXPR$0 |
+|--------------|
+| fox | jumps |
+|--------------|
</code></pre></div></div>
<h2 id="strpos">STRPOS</h2>
diff --git a/feed.xml b/feed.xml
index a6876e5..fc64763 100644
--- a/feed.xml
+++ b/feed.xml
@@ -4,10 +4,10 @@
<title>Apache Drill - Schema-free SQL for Hadoop, NoSQL and Cloud
Storage</title>
<description>The official user documentation for Apache Drill.
</description>
- <link>http://localhost:4000/</link>
- <atom:link href="http://localhost:4000/feed.xml"; rel="self"
type="application/rss+xml"/>
- <pubDate>Sun, 09 May 2021 11:57:55 +0200</pubDate>
- <lastBuildDate>Sun, 09 May 2021 11:57:55 +0200</lastBuildDate>
+ <link>/</link>
+ <atom:link href="/feed.xml" rel="self" type="application/rss+xml"/>
+ <pubDate>Fri, 04 Jun 2021 16:50:26 +0200</pubDate>
+ <lastBuildDate>Fri, 04 Jun 2021 16:50:26 +0200</lastBuildDate>
<generator>Jekyll v3.9.0</generator>
<item>
@@ -26,8 +26,8 @@
<p>You can find a complete list of improvements and JIRAs resolved in
the 1.18.0 release <a
href="/docs/apache-drill-1-18-0-release-notes/">here</a>.</p>
</description>
<pubDate>Sat, 05 Sep 2020 00:00:00 +0200</pubDate>
- <link>http://localhost:4000/blog/2020/09/05/drill-1.18-released/</link>
- <guid
isPermaLink="true">http://localhost:4000/blog/2020/09/05/drill-1.18-released/</guid>
+ <link>/blog/2020/09/05/drill-1.18-released/</link>
+ <guid isPermaLink="true">/blog/2020/09/05/drill-1.18-released/</guid>
<category>blog</category>
@@ -68,8 +68,8 @@
</description>
<pubDate>Thu, 26 Dec 2019 00:00:00 +0200</pubDate>
- <link>http://localhost:4000/blog/2019/12/26/drill-1.17-released/</link>
- <guid
isPermaLink="true">http://localhost:4000/blog/2019/12/26/drill-1.17-released/</guid>
+ <link>/blog/2019/12/26/drill-1.17-released/</link>
+ <guid isPermaLink="true">/blog/2019/12/26/drill-1.17-released/</guid>
<category>blog</category>
@@ -81,8 +81,8 @@
<description>
</description>
<pubDate>Thu, 02 May 2019 00:00:00 +0200</pubDate>
- <link>http://localhost:4000/blog/2019/05/02/drill-user-meetup/</link>
- <guid
isPermaLink="true">http://localhost:4000/blog/2019/05/02/drill-user-meetup/</guid>
+ <link>/blog/2019/05/02/drill-user-meetup/</link>
+ <guid isPermaLink="true">/blog/2019/05/02/drill-user-meetup/</guid>
<category>blog</category>
@@ -117,8 +117,8 @@
</description>
<pubDate>Thu, 02 May 2019 00:00:00 +0200</pubDate>
- <link>http://localhost:4000/blog/2019/05/02/drill-1.16-released/</link>
- <guid
isPermaLink="true">http://localhost:4000/blog/2019/05/02/drill-1.16-released/</guid>
+ <link>/blog/2019/05/02/drill-1.16-released/</link>
+ <guid isPermaLink="true">/blog/2019/05/02/drill-1.16-released/</guid>
<category>blog</category>
@@ -150,8 +150,8 @@
</description>
<pubDate>Mon, 31 Dec 2018 00:00:00 +0200</pubDate>
- <link>http://localhost:4000/blog/2018/12/31/drill-1.15-released/</link>
- <guid
isPermaLink="true">http://localhost:4000/blog/2018/12/31/drill-1.15-released/</guid>
+ <link>/blog/2018/12/31/drill-1.15-released/</link>
+ <guid isPermaLink="true">/blog/2018/12/31/drill-1.15-released/</guid>
<category>blog</category>
@@ -185,8 +185,8 @@
</ul>
</description>
<pubDate>Sat, 01 Dec 2018 00:00:00 +0200</pubDate>
-
<link>http://localhost:4000/blog/2018/12/01/learning-apache-drill-book/</link>
- <guid
isPermaLink="true">http://localhost:4000/blog/2018/12/01/learning-apache-drill-book/</guid>
+ <link>/blog/2018/12/01/learning-apache-drill-book/</link>
+ <guid
isPermaLink="true">/blog/2018/12/01/learning-apache-drill-book/</guid>
<category>blog</category>
@@ -198,8 +198,8 @@
<description>
</description>
<pubDate>Tue, 16 Oct 2018 21:18:04 +0200</pubDate>
- <link>http://localhost:4000/blog/2018/10/16/drill-user-meetup/</link>
- <guid
isPermaLink="true">http://localhost:4000/blog/2018/10/16/drill-user-meetup/</guid>
+ <link>/blog/2018/10/16/drill-user-meetup/</link>
+ <guid isPermaLink="true">/blog/2018/10/16/drill-user-meetup/</guid>
<category>blog</category>
@@ -211,8 +211,8 @@
<description>
</description>
<pubDate>Tue, 16 Oct 2018 21:18:04 +0200</pubDate>
- <link>http://localhost:4000/blog/2018/10/16/drill-developer-day/</link>
- <guid
isPermaLink="true">http://localhost:4000/blog/2018/10/16/drill-developer-day/</guid>
+ <link>/blog/2018/10/16/drill-developer-day/</link>
+ <guid isPermaLink="true">/blog/2018/10/16/drill-developer-day/</guid>
<category>blog</category>
@@ -245,8 +245,8 @@ See <a
href="/docs/image-metadata-format-plugin/">Image Metadata
</description>
<pubDate>Sun, 05 Aug 2018 00:00:00 +0200</pubDate>
- <link>http://localhost:4000/blog/2018/08/05/drill-1.14-released/</link>
- <guid
isPermaLink="true">http://localhost:4000/blog/2018/08/05/drill-1.14-released/</guid>
+ <link>/blog/2018/08/05/drill-1.14-released/</link>
+ <guid isPermaLink="true">/blog/2018/08/05/drill-1.14-released/</guid>
<category>blog</category>
@@ -285,8 +285,8 @@ See <a
href="/docs/image-metadata-format-plugin/">Image Metadata
</description>
<pubDate>Sun, 18 Mar 2018 00:00:00 +0200</pubDate>
- <link>http://localhost:4000/blog/2018/03/18/drill-1.13-released/</link>
- <guid
isPermaLink="true">http://localhost:4000/blog/2018/03/18/drill-1.13-released/</guid>
+ <link>/blog/2018/03/18/drill-1.13-released/</link>
+ <guid isPermaLink="true">/blog/2018/03/18/drill-1.13-released/</guid>
<category>blog</category>
