This is an automated email from the ASF dual-hosted git repository.
dzamo pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/drill-site.git
The following commit(s) were added to refs/heads/master by this push:
new b1d2ad9 Blog post update.
b1d2ad9 is described below
commit b1d2ad9f7eefad7b762ed9fd9b0caca855efbc8f
Author: James Turton <[email protected]>
AuthorDate: Tue Nov 2 07:51:34 2021 +0200
Blog post update.
---
blog/_posts/en/2021-10-30-reports-of-my-death.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/blog/_posts/en/2021-10-30-reports-of-my-death.md
b/blog/_posts/en/2021-10-30-reports-of-my-death.md
index ca6fdca..1b81d86 100644
--- a/blog/_posts/en/2021-10-30-reports-of-my-death.md
+++ b/blog/_posts/en/2021-10-30-reports-of-my-death.md
@@ -7,15 +7,15 @@ excerpt: There's a somewhat breathless post entitled "The
Death of Apache Drill"
authors: ["jturton"]
---
-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 "Apache Dri [...]
+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 "Apache Dri [...]
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 recent [...]
-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 [downloads of
Drill-related software](https://pepy.tech/project/sqlalchemy-drill) 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 allowed ourselve [...]
+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 [downloads of
Drill-related software](https://pepy.tech/project/sqlalchemy-drill) 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 allowed ourselv [...]
-Next, the notion that Drill is "tied", locked in, to MapR and Hadoop. As far
as _Apache_ 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 _cannot_
integrate Drill with MapR products and Hadoop. It supports these things well
and its history is certainly intertwine [...]
+Let's turn next to the notion that Drill is "tied", locked in, to MapR and
Hadoop. As far as _Apache_ 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
_cannot_ integrate Drill with MapR products and Hadoop. It supports these
things well and its history is certain [...]
-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 in [...]
+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 at [...]
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 amount [...]
