This is an automated email from the ASF dual-hosted git repository.
git-site-role 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 74b0800 Automatic Site Publish by Buildbot
74b0800 is described below
commit 74b0800fc0615e57686e73d48d9fd61532516873
Author: buildbot <[email protected]>
AuthorDate: Sun Oct 31 07:34:06 2021 +0000
Automatic Site Publish by Buildbot
---
output/blog/2021/10/30/reports-of-my-death/index.html | 6 +++---
output/blog/index.html | 2 +-
output/feed.xml | 10 +++++-----
output/zh/blog/2021/10/30/reports-of-my-death/index.html | 6 +++---
output/zh/blog/index.html | 2 +-
output/zh/feed.xml | 10 +++++-----
6 files changed, 18 insertions(+), 18 deletions(-)
diff --git a/output/blog/2021/10/30/reports-of-my-death/index.html
b/output/blog/2021/10/30/reports-of-my-death/index.html
index 27399a5..96e5f9e 100644
--- a/output/blog/2021/10/30/reports-of-my-death/index.html
+++ b/output/blog/2021/10/30/reports-of-my-death/index.html
@@ -154,13 +154,13 @@
<div class="addthis_sharing_toolbox"></div>
<article class="post-content">
- <p>There’s a somewhat breathless post entitled “The Death of Apache Drill”
in a blog that has as a theme the imminent demise of technologies previously or
currently associated with Hadoop, with the exception of the query engine
formerly known as PrestoSQL, or Trino. It’s ultimately a promotional piece for
the website’s owner, which is entirely normal and usually it wouldn’t warrant
further mention. But it’s done whatever it is that it takes to climb up to the
first page of the sear [...]
+ <p>There’s a somewhat breathless post entitled “The Death of Apache Drill”
in a blog that has as a theme the imminent demise of technologies previously or
currently associated with Hadoop, with the exception of Trino (formerly known
as PrestoSQL). It’s ultimately a promotional piece for the website’s owner,
which is entirely normal and usually it wouldn’t warrant further mention. But
it’s done whatever it is that it takes to climb up to the first page of the
search results for “Apa [...]
-<p>Firstly, the title proclaims a little too much. Drill did suffer the loss
of its primary corporate backer, and of course its pulse has been faint as a
result, but we invite the author to visit the project and reconsider his
declaration of death. We don’t have hundreds of active contributors making
thousands of commits a year but there are enough of us to get bugs fixed, new
data sources supported, performance and reliability improved. We’ve started
talking about speeding up our re [...]
+<p>Firstly, the title proclaims a little too much. Drill did suffer the loss
of its primary corporate backer, and of course its pulse has been faint as a
result, but we invite the author to visit the project and reconsider his
declaration of death. We don’t have hundreds of active contributors making
thousands of commits a year but there are enough of us to get bugs fixed, new
data sources supported, performance and reliability improved. We’ve started
talking about speeding up our re [...]
<p>Next, the notion that Drill is “tied”, locked in, to MapR and Hadoop. As
far as <em>Apache</em> Drill is concerned, this has never been true in the time
I’ve worked on it . You require nothing from MapR, nor do you need to run a
single Hadoop service, in order to starting querying using the Drill binaries
we distribute with default settings. That is not to say that you
<em>cannot</em> integrate Drill with MapR products and Hadoop, it supports
these things well and its history is ce [...]
-<p>On performance and concurrency issues, I don’t have enough information to
add anything useful to this. I can say that we would treat fixing such issues
as a priority if their magnitude was anything more than minor. It’s worth
noting that, While there are projects that focus on speed to the exclusion of
all else, contemporary Drill places as much weight on flexibility as it does on
speed. The dichotomy implied by the post’s “Proprietary Solutions vs. Open
Source” section heading? I [...]
+<p>On performance and concurrency issues, I don’t have enough information to
add anything useful to this. If they’re code problems, rather than
misconfiguration, then we’ll certainly make them a priority. It’s worth noting
that, while there are projects that focus on speed to the exclusion of all
else, contemporary Drill places as much weight on flexibility as it does on
speed. On to the dichotomy implied by the post’s “Proprietary Solutions vs.
Open Source” section heading. It is a [...]
<p>What of the need for users of Hadoop to be “fearful”? Hadoop probably was
overdeployed as many of us rushed to cargo cult another FAANG technology that
was developed for a context that only some of us actually share. But it’s a
mature technology that solves a certain set of problems very well, it lives at
Apache, and it is not about to vanish in a puff of smoke. In my opinion there
is no need for users of Hadoop to feel afraid, regardless of how their big data
stacks might evolve i [...]
diff --git a/output/blog/index.html b/output/blog/index.html
index 4476ed7..469e4f3 100644
--- a/output/blog/index.html
+++ b/output/blog/index.html
@@ -144,7 +144,7 @@
<p><a class="post-link" href="/blog/2021/10/30/reports-of-my-death/">The
reports of my death have been greatly exaggerated</a><br/>
<span class="post-date">Posted on Oct 30, 2021
by James Turton</span>
-<br/>There's a somewhat breathless post entitled "The Death of Apache Drill"
in a blog that has as a theme the imminent demise of technologies previously or
currently associated with Hadoop, with the exception of the query engine
formerly known as PrestoSQL, or Trino.</p>
+<br/>There's a somewhat breathless post entitled "The Death of Apache Drill"
in a blog that has as a theme the imminent demise of technologies previously or
currently associated with Hadoop, with the exception Trino (formerly known as
PrestoSQL).</p>
<!-- previously: site.posts -->
<p><a class="post-link"
href="/blog/2021/08/05/drill-provider-for-airflow/">Drill provider for
Airflow</a><br/>
<span class="post-date">Posted on Aug 5, 2021
diff --git a/output/feed.xml b/output/feed.xml
index cce9b87..47743ce 100644
--- a/output/feed.xml
+++ b/output/feed.xml
@@ -6,19 +6,19 @@
</description>
<link>/</link>
<atom:link href="/feed.xml" rel="self" type="application/rss+xml"/>
- <pubDate>Sun, 31 Oct 2021 07:17:19 +0000</pubDate>
- <lastBuildDate>Sun, 31 Oct 2021 07:17:19 +0000</lastBuildDate>
+ <pubDate>Sun, 31 Oct 2021 07:31:37 +0000</pubDate>
+ <lastBuildDate>Sun, 31 Oct 2021 07:31:37 +0000</lastBuildDate>
<generator>Jekyll v3.9.1</generator>
<item>
<title>The reports of my death have been greatly exaggerated</title>
- <description><p>There’s a somewhat breathless post entitled “The
Death of Apache Drill” in a blog that has as a theme the imminent demise of
technologies previously or currently associated with Hadoop, with the exception
of the query engine formerly known as PrestoSQL, or Trino. It’s ultimately a
promotional piece for the website’s owner, which is entirely normal and usually
it wouldn’t warrant further mention. But it’s done whatever it is that it
takes to climb up to the [...]
+ <description><p>There’s a somewhat breathless post entitled “The
Death of Apache Drill” in a blog that has as a theme the imminent demise of
technologies previously or currently associated with Hadoop, with the exception
of Trino (formerly known as PrestoSQL). It’s ultimately a promotional piece
for the website’s owner, which is entirely normal and usually it wouldn’t
warrant further mention. But it’s done whatever it is that it takes to climb
up to the first page of the [...]
-<p>Firstly, the title proclaims a little too much. Drill did suffer the
loss of its primary corporate backer, and of course its pulse has been faint as
a result, but we invite the author to visit the project and reconsider his
declaration of death. We don’t have hundreds of active contributors making
thousands of commits a year but there are enough of us to get bugs fixed, new
data sources supported, performance and reliability improved. We’ve started
talking about speeding up [...]
+<p>Firstly, the title proclaims a little too much. Drill did suffer the
loss of its primary corporate backer, and of course its pulse has been faint as
a result, but we invite the author to visit the project and reconsider his
declaration of death. We don’t have hundreds of active contributors making
thousands of commits a year but there are enough of us to get bugs fixed, new
data sources supported, performance and reliability improved. We’ve started
talking about speeding up [...]
<p>Next, the notion that Drill is “tied”, locked in, to MapR and Hadoop.
As far as <em>Apache</em> Drill is concerned, this has never been
true in the time I’ve worked on it . You require nothing from MapR, nor do you
need to run a single Hadoop service, in order to starting querying using the
Drill binaries we distribute with default settings. That is not to say that
you <em>cannot</em> integrate Drill with MapR products and Hadoop,
it supports these thi [...]
-<p>On performance and concurrency issues, I don’t have enough
information to add anything useful to this. I can say that we would treat
fixing such issues as a priority if their magnitude was anything more than
minor. It’s worth noting that, While there are projects that focus on speed to
the exclusion of all else, contemporary Drill places as much weight on
flexibility as it does on speed. The dichotomy implied by the post’s
“Proprietary Solutions vs. Open Source” section headi [...]
+<p>On performance and concurrency issues, I don’t have enough
information to add anything useful to this. If they’re code problems, rather
than misconfiguration, then we’ll certainly make them a priority. It’s worth
noting that, while there are projects that focus on speed to the exclusion of
all else, contemporary Drill places as much weight on flexibility as it does on
speed. On to the dichotomy implied by the post’s “Proprietary Solutions vs.
Open Source” section heading. It [...]
<p>What of the need for users of Hadoop to be “fearful”? Hadoop
probably was overdeployed as many of us rushed to cargo cult another FAANG
technology that was developed for a context that only some of us actually
share. But it’s a mature technology that solves a certain set of problems very
well, it lives at Apache, and it is not about to vanish in a puff of smoke. In
my opinion there is no need for users of Hadoop to feel afraid, regardless of
how their big data stacks might ev [...]
diff --git a/output/zh/blog/2021/10/30/reports-of-my-death/index.html
b/output/zh/blog/2021/10/30/reports-of-my-death/index.html
index 7bb3d0c..e998051 100644
--- a/output/zh/blog/2021/10/30/reports-of-my-death/index.html
+++ b/output/zh/blog/2021/10/30/reports-of-my-death/index.html
@@ -154,13 +154,13 @@
<div class="addthis_sharing_toolbox"></div>
<article class="post-content">
- <p>There’s a somewhat breathless post entitled “The Death of Apache Drill”
in a blog that has as a theme the imminent demise of technologies previously or
currently associated with Hadoop, with the exception of the query engine
formerly known as PrestoSQL, or Trino. It’s ultimately a promotional piece for
the website’s owner, which is entirely normal and usually it wouldn’t warrant
further mention. But it’s done whatever it is that it takes to climb up to the
first page of the sear [...]
+ <p>There’s a somewhat breathless post entitled “The Death of Apache Drill”
in a blog that has as a theme the imminent demise of technologies previously or
currently associated with Hadoop, with the exception of Trino (formerly known
as PrestoSQL). It’s ultimately a promotional piece for the website’s owner,
which is entirely normal and usually it wouldn’t warrant further mention. But
it’s done whatever it is that it takes to climb up to the first page of the
search results for “Apa [...]
-<p>Firstly, the title proclaims a little too much. Drill did suffer the loss
of its primary corporate backer, and of course its pulse has been faint as a
result, but we invite the author to visit the project and reconsider his
declaration of death. We don’t have hundreds of active contributors making
thousands of commits a year but there are enough of us to get bugs fixed, new
data sources supported, performance and reliability improved. We’ve started
talking about speeding up our re [...]
+<p>Firstly, the title proclaims a little too much. Drill did suffer the loss
of its primary corporate backer, and of course its pulse has been faint as a
result, but we invite the author to visit the project and reconsider his
declaration of death. We don’t have hundreds of active contributors making
thousands of commits a year but there are enough of us to get bugs fixed, new
data sources supported, performance and reliability improved. We’ve started
talking about speeding up our re [...]
<p>Next, the notion that Drill is “tied”, locked in, to MapR and Hadoop. As
far as <em>Apache</em> Drill is concerned, this has never been true in the time
I’ve worked on it . You require nothing from MapR, nor do you need to run a
single Hadoop service, in order to starting querying using the Drill binaries
we distribute with default settings. That is not to say that you
<em>cannot</em> integrate Drill with MapR products and Hadoop, it supports
these things well and its history is ce [...]
-<p>On performance and concurrency issues, I don’t have enough information to
add anything useful to this. I can say that we would treat fixing such issues
as a priority if their magnitude was anything more than minor. It’s worth
noting that, While there are projects that focus on speed to the exclusion of
all else, contemporary Drill places as much weight on flexibility as it does on
speed. The dichotomy implied by the post’s “Proprietary Solutions vs. Open
Source” section heading? I [...]
+<p>On performance and concurrency issues, I don’t have enough information to
add anything useful to this. If they’re code problems, rather than
misconfiguration, then we’ll certainly make them a priority. It’s worth noting
that, while there are projects that focus on speed to the exclusion of all
else, contemporary Drill places as much weight on flexibility as it does on
speed. On to the dichotomy implied by the post’s “Proprietary Solutions vs.
Open Source” section heading. It is a [...]
<p>What of the need for users of Hadoop to be “fearful”? Hadoop probably was
overdeployed as many of us rushed to cargo cult another FAANG technology that
was developed for a context that only some of us actually share. But it’s a
mature technology that solves a certain set of problems very well, it lives at
Apache, and it is not about to vanish in a puff of smoke. In my opinion there
is no need for users of Hadoop to feel afraid, regardless of how their big data
stacks might evolve i [...]
diff --git a/output/zh/blog/index.html b/output/zh/blog/index.html
index 086b679..0127266 100644
--- a/output/zh/blog/index.html
+++ b/output/zh/blog/index.html
@@ -144,7 +144,7 @@
<p><a class="post-link" href="/zh/blog/2021/10/30/reports-of-my-death/">The
reports of my death have been greatly exaggerated</a><br/>
<span class="post-date">Posted on Oct 30, 2021
by James Turton</span>
-<br/>There's a somewhat breathless post entitled "The Death of Apache Drill"
in a blog that has as a theme the imminent demise of technologies previously or
currently associated with Hadoop, with the exception of the query engine
formerly known as PrestoSQL, or Trino.</p>
+<br/>There's a somewhat breathless post entitled "The Death of Apache Drill"
in a blog that has as a theme the imminent demise of technologies previously or
currently associated with Hadoop, with the exception Trino (formerly known as
PrestoSQL).</p>
<!-- previously: site.posts -->
<p><a class="post-link"
href="/zh/blog/2021/08/05/drill-provider-for-airflow/">Drill provider for
Airflow</a><br/>
<span class="post-date">Posted on Aug 5, 2021
diff --git a/output/zh/feed.xml b/output/zh/feed.xml
index a5d02be..4aa85f5 100644
--- a/output/zh/feed.xml
+++ b/output/zh/feed.xml
@@ -6,19 +6,19 @@
</description>
<link>/</link>
<atom:link href="/zh/feed.xml" rel="self" type="application/rss+xml"/>
- <pubDate>Sun, 31 Oct 2021 07:17:19 +0000</pubDate>
- <lastBuildDate>Sun, 31 Oct 2021 07:17:19 +0000</lastBuildDate>
+ <pubDate>Sun, 31 Oct 2021 07:31:37 +0000</pubDate>
+ <lastBuildDate>Sun, 31 Oct 2021 07:31:37 +0000</lastBuildDate>
<generator>Jekyll v3.9.1</generator>
<item>
<title>The reports of my death have been greatly exaggerated</title>
- <description><p>There’s a somewhat breathless post entitled “The
Death of Apache Drill” in a blog that has as a theme the imminent demise of
technologies previously or currently associated with Hadoop, with the exception
of the query engine formerly known as PrestoSQL, or Trino. It’s ultimately a
promotional piece for the website’s owner, which is entirely normal and usually
it wouldn’t warrant further mention. But it’s done whatever it is that it
takes to climb up to the [...]
+ <description><p>There’s a somewhat breathless post entitled “The
Death of Apache Drill” in a blog that has as a theme the imminent demise of
technologies previously or currently associated with Hadoop, with the exception
of Trino (formerly known as PrestoSQL). It’s ultimately a promotional piece
for the website’s owner, which is entirely normal and usually it wouldn’t
warrant further mention. But it’s done whatever it is that it takes to climb
up to the first page of the [...]
-<p>Firstly, the title proclaims a little too much. Drill did suffer the
loss of its primary corporate backer, and of course its pulse has been faint as
a result, but we invite the author to visit the project and reconsider his
declaration of death. We don’t have hundreds of active contributors making
thousands of commits a year but there are enough of us to get bugs fixed, new
data sources supported, performance and reliability improved. We’ve started
talking about speeding up [...]
+<p>Firstly, the title proclaims a little too much. Drill did suffer the
loss of its primary corporate backer, and of course its pulse has been faint as
a result, but we invite the author to visit the project and reconsider his
declaration of death. We don’t have hundreds of active contributors making
thousands of commits a year but there are enough of us to get bugs fixed, new
data sources supported, performance and reliability improved. We’ve started
talking about speeding up [...]
<p>Next, the notion that Drill is “tied”, locked in, to MapR and Hadoop.
As far as <em>Apache</em> Drill is concerned, this has never been
true in the time I’ve worked on it . You require nothing from MapR, nor do you
need to run a single Hadoop service, in order to starting querying using the
Drill binaries we distribute with default settings. That is not to say that
you <em>cannot</em> integrate Drill with MapR products and Hadoop,
it supports these thi [...]
-<p>On performance and concurrency issues, I don’t have enough
information to add anything useful to this. I can say that we would treat
fixing such issues as a priority if their magnitude was anything more than
minor. It’s worth noting that, While there are projects that focus on speed to
the exclusion of all else, contemporary Drill places as much weight on
flexibility as it does on speed. The dichotomy implied by the post’s
“Proprietary Solutions vs. Open Source” section headi [...]
+<p>On performance and concurrency issues, I don’t have enough
information to add anything useful to this. If they’re code problems, rather
than misconfiguration, then we’ll certainly make them a priority. It’s worth
noting that, while there are projects that focus on speed to the exclusion of
all else, contemporary Drill places as much weight on flexibility as it does on
speed. On to the dichotomy implied by the post’s “Proprietary Solutions vs.
Open Source” section heading. It [...]
<p>What of the need for users of Hadoop to be “fearful”? Hadoop
probably was overdeployed as many of us rushed to cargo cult another FAANG
technology that was developed for a context that only some of us actually
share. But it’s a mature technology that solves a certain set of problems very
well, it lives at Apache, and it is not about to vanish in a puff of smoke. In
my opinion there is no need for users of Hadoop to feel afraid, regardless of
how their big data stacks might ev [...]
