[drill-site] branch master updated: Blog post updates.

[dz...@apache.org]

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 934f56f  Blog post updates.
934f56f is described below

commit 934f56fe387b80a3b48e718c999539d510eec608
Author: James Turton <ja...@somecomputer.xyz>
AuthorDate: Sun Oct 31 09:31:03 2021 +0200

    Blog post updates.
---
 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 7901229..4972f9e 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
@@ -2,18 +2,18 @@
 layout: post
 title: "The reports of my death have been greatly exaggerated"
 code: reports-of-my-death
-excerpt: 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.
+excerpt: 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).
 
 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 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 search resu [...]
+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, performance and reliability improved.  We've started talking about speeding up our relea [...]
+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 relea [...]
 
 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 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 _cannot_ integrate Drill with MapR products and Hadoop, it supports these things well and its history is certainly intertwin [...]
 
-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?  It i [...]
+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 fal [...]
 
 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 in t [...]