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 629b40a Automatic Site Publish by Buildbot
629b40a is described below
commit 629b40a3b62b50c76359e49802b8fb7c3f58efc9
Author: buildbot <[email protected]>
AuthorDate: Mon Nov 1 04:47:30 2021 +0000
Automatic Site Publish by Buildbot
---
output/blog/2021/10/30/reports-of-my-death/index.html | 12 +++++++-----
output/feed.xml | 16 +++++++++-------
output/zh/blog/2021/10/30/reports-of-my-death/index.html | 12 +++++++-----
output/zh/feed.xml | 16 +++++++++-------
4 files changed, 32 insertions(+), 24 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 1fc22cb..5d8f19d 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,17 @@
<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, 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. In the near
future I’ll blog about our work on [...]
-<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 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 [...]
+<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>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 to the exclusion of all
else, contemporary Drill places as much weight on flexibility as it does on
speed. Moving to the dichotomy implied by the post’s “Proprietary Solutions
vs. Open Source” section heading: it is [...]
+<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 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 c [...]
-<p>What of the idea that users of Hadoop should be “fearful”? Hadoop probably
was overdeployed as many of us rushed to cargo cult another Big Tech 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 its users to feel afraid, regardless of how their big data
stacks might evolve [...]
+<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>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 [...]
<p>Drill is it a very interesting point in its history. It presents a unique
opportunity to developers who would like to challenge themselves in that
individual contributions are not diluted in a sea of commits from others, and
even newcomers can have a major impact. If you’d like to come and pick an
interesting problem in Drill to solve please feel welcomed, you’ll find us a
friendly bunch. If you’d like a job working full time on Drill then send an
email to me at dzamo at apache.org.</p>
diff --git a/output/feed.xml b/output/feed.xml
index 03813fc..1c0e3f1 100644
--- a/output/feed.xml
+++ b/output/feed.xml
@@ -6,21 +6,23 @@
</description>
<link>/</link>
<atom:link href="/feed.xml" rel="self" type="application/rss+xml"/>
- <pubDate>Sun, 31 Oct 2021 08:33:19 +0000</pubDate>
- <lastBuildDate>Sun, 31 Oct 2021 08:33:19 +0000</lastBuildDate>
+ <pubDate>Mon, 01 Nov 2021 04:45:03 +0000</pubDate>
+ <lastBuildDate>Mon, 01 Nov 2021 04:45:03 +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, 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. In the near
future I’ll blog about our w [...]
-<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 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 t [...]
+<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>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 to the exclusion of
all else, contemporary Drill places as much weight on flexibility as it does on
speed. Moving to the dichotomy implied by the post’s “Proprietary Solutions
vs. Open Source” section heading: [...]
+<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 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 th [...]
-<p>What of the idea that users of Hadoop should be “fearful”? Hadoop
probably was overdeployed as many of us rushed to cargo cult another Big Tech
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 its users to feel afraid, regardless of how
their big data stacks might [...]
+<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>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 [...]
<p>Drill is it a very interesting point in its history. It presents a
unique opportunity to developers who would like to challenge themselves in that
individual contributions are not diluted in a sea of commits from others, and
even newcomers can have a major impact. If you’d like to come and pick an
interesting problem in Drill to solve please feel welcomed, you’ll find us a
friendly bunch. If you’d like a job working full time on Drill then send an
email to me at dzamo at apac [...]
</description>
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 05f68b3..1a1cd24 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,17 @@
<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, 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. In the near
future I’ll blog about our work on [...]
-<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 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 [...]
+<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>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 to the exclusion of all
else, contemporary Drill places as much weight on flexibility as it does on
speed. Moving to the dichotomy implied by the post’s “Proprietary Solutions
vs. Open Source” section heading: it is [...]
+<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 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 c [...]
-<p>What of the idea that users of Hadoop should be “fearful”? Hadoop probably
was overdeployed as many of us rushed to cargo cult another Big Tech 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 its users to feel afraid, regardless of how their big data
stacks might evolve [...]
+<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>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 [...]
<p>Drill is it a very interesting point in its history. It presents a unique
opportunity to developers who would like to challenge themselves in that
individual contributions are not diluted in a sea of commits from others, and
even newcomers can have a major impact. If you’d like to come and pick an
interesting problem in Drill to solve please feel welcomed, you’ll find us a
friendly bunch. If you’d like a job working full time on Drill then send an
email to me at dzamo at apache.org.</p>
diff --git a/output/zh/feed.xml b/output/zh/feed.xml
index fee6e8f..f5fdd7a 100644
--- a/output/zh/feed.xml
+++ b/output/zh/feed.xml
@@ -6,21 +6,23 @@
</description>
<link>/</link>
<atom:link href="/zh/feed.xml" rel="self" type="application/rss+xml"/>
- <pubDate>Sun, 31 Oct 2021 08:33:19 +0000</pubDate>
- <lastBuildDate>Sun, 31 Oct 2021 08:33:19 +0000</lastBuildDate>
+ <pubDate>Mon, 01 Nov 2021 04:45:03 +0000</pubDate>
+ <lastBuildDate>Mon, 01 Nov 2021 04:45:03 +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, 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. In the near
future I’ll blog about our w [...]
-<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 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 t [...]
+<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>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 to the exclusion of
all else, contemporary Drill places as much weight on flexibility as it does on
speed. Moving to the dichotomy implied by the post’s “Proprietary Solutions
vs. Open Source” section heading: [...]
+<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 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 th [...]
-<p>What of the idea that users of Hadoop should be “fearful”? Hadoop
probably was overdeployed as many of us rushed to cargo cult another Big Tech
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 its users to feel afraid, regardless of how
their big data stacks might [...]
+<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>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 [...]
<p>Drill is it a very interesting point in its history. It presents a
unique opportunity to developers who would like to challenge themselves in that
individual contributions are not diluted in a sea of commits from others, and
even newcomers can have a major impact. If you’d like to come and pick an
interesting problem in Drill to solve please feel welcomed, you’ll find us a
friendly bunch. If you’d like a job working full time on Drill then send an
email to me at dzamo at apac [...]
</description>
