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 efed711 Automatic Site Publish by Buildbot
efed711 is described below
commit efed711cce80fb456e5f2c05b974b118a1da3daa
Author: buildbot <[email protected]>
AuthorDate: Tue Nov 2 06:34:33 2021 +0000
Automatic Site Publish by Buildbot
---
output/blog/2021/10/30/reports-of-my-death/index.html | 8 ++++----
output/feed.xml | 12 ++++++------
output/zh/blog/2021/10/30/reports-of-my-death/index.html | 8 ++++----
output/zh/feed.xml | 12 ++++++------
4 files changed, 20 insertions(+), 20 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 b55806b..8aa7a95 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,15 +154,15 @@
<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 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>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, and performance and reliability improved. In the near
future I’ll blog about our rec [...]
-<p>We’ve started talking about speeding up our release cadence to better
reflect our recent activity. We’re rekindling the project’s communication
channels, and improving and translating our documentation. Metrics like <a
href="https://pepy.tech/project/sqlalchemy-drill";>downloads of Drill-related
software</a> suggest to us that interest has stopped trending down and started
trending up. If this is death, in short, then the phenomenon is a lot less
about resting in peace than we’ve al [...]
+<p>We’ve started talking about speeding up our release cadence to better
reflect our recent activity. We’re rekindling the project’s communication
channels, and improving and translating our documentation. Metrics like <a
href="https://pepy.tech/project/sqlalchemy-drill";>downloads of Drill-related
software</a> suggest to us that interest has stopped trending down and started
trending up. If this is death, in short, then that phenomenon is a lot less
about resting in peace than we’ve a [...]
-<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 with it. You require nothing from MapR, nor do you need to run a
single Hadoop service, in order to start querying using the Drill binaries we
distribute with default settings. This 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 cer [...]
+<p>Let’s turn next to 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 with it. You require nothing from MapR, nor do you
need to run a single Hadoop service, in order to start querying using the Drill
binaries we distribute with default settings. This is not to say that you
<em>cannot</em> integrate Drill with MapR products and Hadoop. It supports
these things well and its h [...]
-<p>On, to the sentiment that users of Hadoop should be “fearful”. Hadoop
probably was overdeployed as many of us rushed to cargo cult another Big Tech
innovation that was developed for a context that only some of us actually
share. Some of those deployments will likely revert to something simpler or
better matched to the problem at hand. Nevertheless Hadoop is mature and
capable software that solves a certain set of problems very well, it lives at
Apache, and it is not about to vanish [...]
+<p>We move on, to the sentiment that users of Hadoop should be fearful.
Hadoop probably was overdeployed as many of us scrambled for another scrap of
open source to drop from Big Tech’s banquet table where it was developed for a
context that only some of us actually share. Some of those deployments will
likely revert to something simpler or better matched to the problem at hand.
Nevertheless Hadoop is mature and capable software that solves a certain set of
problems very well, lives [...]
<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’d certainly make them a priority. It’s worth noting
that, while there are projects that focus on speed above all else, contemporary
Drill places as much weight on flexibility as it does on speed. And what
about all the praise heaped on Trino? Well, we agree: this impressive project
has accomplished a tremendous amou [...]
diff --git a/output/feed.xml b/output/feed.xml
index d2a4dc5..17a2118 100644
--- a/output/feed.xml
+++ b/output/feed.xml
@@ -6,21 +6,21 @@
</description>
<link>/</link>
<atom:link href="/feed.xml" rel="self" type="application/rss+xml"/>
- <pubDate>Mon, 01 Nov 2021 09:22:40 +0000</pubDate>
- <lastBuildDate>Mon, 01 Nov 2021 09:22:40 +0000</lastBuildDate>
+ <pubDate>Tue, 02 Nov 2021 06:32:02 +0000</pubDate>
+ <lastBuildDate>Tue, 02 Nov 2021 06:32:02 +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 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 [...]
+ <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, and performance and reliability improved. In the near
future I’ll blog about o [...]
-<p>We’ve started talking about speeding up our release cadence to better
reflect our recent activity. We’re rekindling the project’s communication
channels, and improving and translating our documentation. Metrics like <a
href="https://pepy.tech/project/sqlalchemy-drill">downloads of
Drill-related software</a> suggest to us that interest has stopped
trending down and started trending up. If this is death, in short, then the
phenomenon is a lot less about re [...]
+<p>We’ve started talking about speeding up our release cadence to better
reflect our recent activity. We’re rekindling the project’s communication
channels, and improving and translating our documentation. Metrics like <a
href="https://pepy.tech/project/sqlalchemy-drill">downloads of
Drill-related software</a> suggest to us that interest has stopped
trending down and started trending up. If this is death, in short, then that
phenomenon is a lot less about r [...]
-<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 with it. You require nothing from MapR, nor do
you need to run a single Hadoop service, in order to start querying using the
Drill binaries we distribute with default settings. This is not to say that
you <em>cannot</em> integrate Drill with MapR products and Hadoop.
It supports these thin [...]
+<p>Let’s turn next to 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 with it. You require nothing
from MapR, nor do you need to run a single Hadoop service, in order to start
querying using the Drill binaries we distribute with default settings. This is
not to say that you <em>cannot</em> integrate Drill with MapR
products and Hadoop. It suppor [...]
-<p>On, to the sentiment that users of Hadoop should be “fearful”.
Hadoop probably was overdeployed as many of us rushed to cargo cult another Big
Tech innovation that was developed for a context that only some of us actually
share. Some of those deployments will likely revert to something simpler or
better matched to the problem at hand. Nevertheless Hadoop is mature and
capable software that solves a certain set of problems very well, it lives at
Apache, and it is not about to [...]
+<p>We move on, to the sentiment that users of Hadoop should be fearful.
Hadoop probably was overdeployed as many of us scrambled for another scrap of
open source to drop from Big Tech’s banquet table where it was developed for a
context that only some of us actually share. Some of those deployments will
likely revert to something simpler or better matched to the problem at hand.
Nevertheless Hadoop is mature and capable software that solves a certain set of
problems very well, [...]
<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’d certainly make them a priority. It’s worth
noting that, while there are projects that focus on speed above all else,
contemporary Drill places as much weight on flexibility as it does on speed.
And what about all the praise heaped on Trino? Well, we agree: this impressive
project has accomplished a tremendou [...]
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 5b700e4..8a71ba4 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,15 +154,15 @@
<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 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>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, and performance and reliability improved. In the near
future I’ll blog about our rec [...]
-<p>We’ve started talking about speeding up our release cadence to better
reflect our recent activity. We’re rekindling the project’s communication
channels, and improving and translating our documentation. Metrics like <a
href="https://pepy.tech/project/sqlalchemy-drill";>downloads of Drill-related
software</a> suggest to us that interest has stopped trending down and started
trending up. If this is death, in short, then the phenomenon is a lot less
about resting in peace than we’ve al [...]
+<p>We’ve started talking about speeding up our release cadence to better
reflect our recent activity. We’re rekindling the project’s communication
channels, and improving and translating our documentation. Metrics like <a
href="https://pepy.tech/project/sqlalchemy-drill";>downloads of Drill-related
software</a> suggest to us that interest has stopped trending down and started
trending up. If this is death, in short, then that phenomenon is a lot less
about resting in peace than we’ve a [...]
-<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 with it. You require nothing from MapR, nor do you need to run a
single Hadoop service, in order to start querying using the Drill binaries we
distribute with default settings. This 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 cer [...]
+<p>Let’s turn next to 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 with it. You require nothing from MapR, nor do you
need to run a single Hadoop service, in order to start querying using the Drill
binaries we distribute with default settings. This is not to say that you
<em>cannot</em> integrate Drill with MapR products and Hadoop. It supports
these things well and its h [...]
-<p>On, to the sentiment that users of Hadoop should be “fearful”. Hadoop
probably was overdeployed as many of us rushed to cargo cult another Big Tech
innovation that was developed for a context that only some of us actually
share. Some of those deployments will likely revert to something simpler or
better matched to the problem at hand. Nevertheless Hadoop is mature and
capable software that solves a certain set of problems very well, it lives at
Apache, and it is not about to vanish [...]
+<p>We move on, to the sentiment that users of Hadoop should be fearful.
Hadoop probably was overdeployed as many of us scrambled for another scrap of
open source to drop from Big Tech’s banquet table where it was developed for a
context that only some of us actually share. Some of those deployments will
likely revert to something simpler or better matched to the problem at hand.
Nevertheless Hadoop is mature and capable software that solves a certain set of
problems very well, lives [...]
<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’d certainly make them a priority. It’s worth noting
that, while there are projects that focus on speed above all else, contemporary
Drill places as much weight on flexibility as it does on speed. And what
about all the praise heaped on Trino? Well, we agree: this impressive project
has accomplished a tremendous amou [...]
diff --git a/output/zh/feed.xml b/output/zh/feed.xml
index de285de..827f18e 100644
--- a/output/zh/feed.xml
+++ b/output/zh/feed.xml
@@ -6,21 +6,21 @@
</description>
<link>/</link>
<atom:link href="/zh/feed.xml" rel="self" type="application/rss+xml"/>
- <pubDate>Mon, 01 Nov 2021 09:22:40 +0000</pubDate>
- <lastBuildDate>Mon, 01 Nov 2021 09:22:40 +0000</lastBuildDate>
+ <pubDate>Tue, 02 Nov 2021 06:32:02 +0000</pubDate>
+ <lastBuildDate>Tue, 02 Nov 2021 06:32:02 +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 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 [...]
+ <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, and performance and reliability improved. In the near
future I’ll blog about o [...]
-<p>We’ve started talking about speeding up our release cadence to better
reflect our recent activity. We’re rekindling the project’s communication
channels, and improving and translating our documentation. Metrics like <a
href="https://pepy.tech/project/sqlalchemy-drill">downloads of
Drill-related software</a> suggest to us that interest has stopped
trending down and started trending up. If this is death, in short, then the
phenomenon is a lot less about re [...]
+<p>We’ve started talking about speeding up our release cadence to better
reflect our recent activity. We’re rekindling the project’s communication
channels, and improving and translating our documentation. Metrics like <a
href="https://pepy.tech/project/sqlalchemy-drill">downloads of
Drill-related software</a> suggest to us that interest has stopped
trending down and started trending up. If this is death, in short, then that
phenomenon is a lot less about r [...]
-<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 with it. You require nothing from MapR, nor do
you need to run a single Hadoop service, in order to start querying using the
Drill binaries we distribute with default settings. This is not to say that
you <em>cannot</em> integrate Drill with MapR products and Hadoop.
It supports these thin [...]
+<p>Let’s turn next to 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 with it. You require nothing
from MapR, nor do you need to run a single Hadoop service, in order to start
querying using the Drill binaries we distribute with default settings. This is
not to say that you <em>cannot</em> integrate Drill with MapR
products and Hadoop. It suppor [...]
-<p>On, to the sentiment that users of Hadoop should be “fearful”.
Hadoop probably was overdeployed as many of us rushed to cargo cult another Big
Tech innovation that was developed for a context that only some of us actually
share. Some of those deployments will likely revert to something simpler or
better matched to the problem at hand. Nevertheless Hadoop is mature and
capable software that solves a certain set of problems very well, it lives at
Apache, and it is not about to [...]
+<p>We move on, to the sentiment that users of Hadoop should be fearful.
Hadoop probably was overdeployed as many of us scrambled for another scrap of
open source to drop from Big Tech’s banquet table where it was developed for a
context that only some of us actually share. Some of those deployments will
likely revert to something simpler or better matched to the problem at hand.
Nevertheless Hadoop is mature and capable software that solves a certain set of
problems very well, [...]
<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’d certainly make them a priority. It’s worth
noting that, while there are projects that focus on speed above all else,
contemporary Drill places as much weight on flexibility as it does on speed.
And what about all the praise heaped on Trino? Well, we agree: this impressive
project has accomplished a tremendou [...]
