drill-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tshi...@apache.org
Subject drill git commit: Drill top-level project announcement updates
Date Tue, 02 Dec 2014 06:27:55 GMT
Repository: drill
Updated Branches:
  refs/heads/gh-pages 7afc003a1 -> f49cff081

Drill top-level project announcement updates

Project: http://git-wip-us.apache.org/repos/asf/drill/repo
Commit: http://git-wip-us.apache.org/repos/asf/drill/commit/f49cff08
Tree: http://git-wip-us.apache.org/repos/asf/drill/tree/f49cff08
Diff: http://git-wip-us.apache.org/repos/asf/drill/diff/f49cff08

Branch: refs/heads/gh-pages
Commit: f49cff0815dcee0064045405bfd8c6e37c8f70c2
Parents: 7afc003
Author: Tomer Shiran <tshiran@gmail.com>
Authored: Mon Dec 1 22:27:36 2014 -0800
Committer: Tomer Shiran <tshiran@gmail.com>
Committed: Mon Dec 1 22:27:36 2014 -0800

 _includes/footer.html                           |  6 +--
 _includes/footer.html.old                       | 55 --------------------
 _includes/head.html.old                         | 12 -----
 blog.html                                       |  2 +-
 .../2014-12-03-drill-top-level-project.md       | 47 +++++++++++++++++
 index.html                                      | 15 +++---
 6 files changed, 58 insertions(+), 79 deletions(-)

diff --git a/_includes/footer.html b/_includes/footer.html
index a20d861..c0888ff 100644
--- a/_includes/footer.html
+++ b/_includes/footer.html
@@ -1,10 +1,6 @@
 <div id="footer" class="mw">
 <div class="wrapper">
 Copyright © 2012-2014 The Apache Software Foundation, licensed under the Apache License,
Version 2.0.<br>
-Apache Incubator, Apache, and the Apache feather logo are trademarks of The Apache Software
Foundation. Other names appearing on the site may be trademarks of their respective owners.<br/><br/>
-Apache Drill is an effort undergoing incubation at The Apache Software Foundation sponsored
by the Apache Incubator PMC. Incubation is required of all newly accepted projects until a
-review indicates that the infrastructure, communications, and decision making process have
stabilized in a manner consistent with other successful ASF projects. While incubation status
is not<br/>
-necessarily a reflection of the completeness or stability of the code, it does indicate that
the project has yet to be fully endorsed by the ASF.
+Apache and the Apache feather logo are trademarks of The Apache Software Foundation. Other
names appearing on the site may be trademarks of their respective owners.<br/><br/>

diff --git a/_includes/footer.html.old b/_includes/footer.html.old
deleted file mode 100644
index be3976f..0000000
--- a/_includes/footer.html.old
+++ /dev/null
@@ -1,55 +0,0 @@
-<footer class="site-footer">
-  <div class="wrapper">
-    <h2 class="footer-heading">{{ site.title }}</h2>
-    <div class="footer-col-wrapper">
-      <div class="footer-col  footer-col-1">
-        <ul class="contact-list">
-          <li>{{ site.title }}</li>
-          <li><a href="mailto:{{ site.email }}">{{ site.email }}</a></li>
-        </ul>
-      </div>
-      <div class="footer-col  footer-col-2">
-        <ul class="social-media-list">
-          {% if site.github_username %}
-          <li>
-            <a href="https://github.com/{{ site.github_username }}">
-              <span class="icon  icon--github">
-                <svg viewBox="0 0 16 16">
-                  <path fill="#828282" d="M7.999,0.431c-4.285,0-7.76,3.474-7.76,7.761
-                </svg>
-              </span>
-              <span class="username">{{ site.github_username }}</span>
-            </a>
-          </li>
-          {% endif %}
-          {% if site.twitter_username %}
-          <li>
-            <a href="https://twitter.com/{{ site.twitter_username }}">
-              <span class="icon  icon--twitter">
-                <svg viewBox="0 0 16 16">
-                  <path fill="#828282" d="M15.969,3.058c-0.586,0.26-1.217,0.436-1.878,0.515c0.675-0.405,1.194-1.045,1.438-1.809
-                  c-0.632,0.375-1.332,0.647-2.076,0.793c-0.596-0.636-1.446-1.033-2.387-1.033c-1.806,0-3.27,1.464-3.27,3.27
-                </svg>
-              </span>
-              <span class="username">{{ site.twitter_username }}</span>
-            </a>
-          </li>
-          {% endif %}
-        </ul>
-      </div>
-      <div class="footer-col  footer-col-3">
-        <p class="text">{{ site.description }}</p>
-      </div>
-    </div>
-  </div>

diff --git a/_includes/head.html.old b/_includes/head.html.old
deleted file mode 100644
index 557e4cc..0000000
--- a/_includes/head.html.old
+++ /dev/null
@@ -1,12 +0,0 @@
-  <meta charset="utf-8">
-  <meta http-equiv="X-UA-Compatible" content="IE=edge">
-  <meta name="viewport" content="width=device-width initial-scale=1">
-  <title>{% if page.title %}{{ page.title }}{% else %}{{ site.title }}{% endif %}</title>
-  <meta name="description" content="{% if page.excerpt %}{{ page.excerpt | strip_html
| strip_newlines | truncate: 160 }}{% else %}{{ site.description }}{% endif %}">
-  <link rel="stylesheet" href="{{ "/css/main.css" | prepend: site.baseurl }}">
-  <link rel="canonical" href="{{ page.url | replace:'index.html','' | prepend: site.baseurl
| prepend: site.url }}">
-  <link rel="alternate" type="application/atom+xml" title="{{ site.title }}" href="{{
"/feed.xml" | prepend: site.baseurl | prepend: site.url }}" />

diff --git a/blog.html b/blog.html
index 86866b3..977a085 100644
--- a/blog.html
+++ b/blog.html
@@ -5,7 +5,7 @@ title: Blog
 {% for post in site.categories.blog %}<!-- previously: site.posts -->
 <p><a class="post-link" href="{{ post.url | prepend: site.baseurl }}">{{ post.title
}}</a>{% if post.date %} ({{ post.date | date: "%b %-d, %Y" }}){% endif %}{% if post.excerpt
%}<br/>{{ post.excerpt }}{% endif %}</p>
 {% endfor %}
-<p class="info">Want to contribute a blog post? Check out the source for some of the
<a href="https://github.com/tshiran/drill-website/tree/gh-pages/blog/_posts">existing
posts</a> to see how it's done. When you're ready, email your Markdown file to <a
+<p class="info">Want to contribute a blog post? Check out the source for some of the
<a href="https://github.com/apache/drill/tree/gh-pages/blog/_posts">existing posts</a>
to see how it's done. When you're ready, email your Markdown file to <a href="mailto:dev@drill.apache.org">dev@drill.apache.org</a>.</p>
 <h1>Third-Party Articles</h1>
 {% for article in site.data.articles %}<!-- previously: site.posts -->
 <p><a class="post-link" href="{{ article.url }}">{{ article.title }}</a>{%
if article.date %} ({{ article.date | date: "%b %-d, %Y" }}){% endif %}{% if article.excerpt
%}<br/>{{ article.excerpt }}{% endif %}</p>

diff --git a/blog/_posts/2014-12-03-drill-top-level-project.md b/blog/_posts/2014-12-03-drill-top-level-project.md
new file mode 100644
index 0000000..1628fa1
--- /dev/null
+++ b/blog/_posts/2014-12-03-drill-top-level-project.md
@@ -0,0 +1,47 @@
+layout: post
+title: "Apache Drill Graduates to a Top-Level Project"
+code: drill-top-level-project
+excerpt: Drill has graduated to a Top-Level Project at Apache. This marks a significant accomplishment
for the Drill community, which now includes dozens of developers working at a variety of companies.
+date: 2014-12-02 08:00
+authors: ["Tomer Shiran, Apache Drill Founder and PMC member"]
+The Apache Software Foundation has just announced that it has promoted Drill to a top-level
project at Apache, similar to other well-known projects like Apache Hadoop and httpd (the
world's most popular Web server). This marks a significant accomplishment for the Drill community,
and I wanted to personally thank everyone who has contributed to the project. It takes many
people, and countless hours, to develop something as complex and innovative as Drill.
+In this post I wanted to reflect on the past and future of Drill.
+## Why We Started Drill
+### The Evolution of Application Development and Data
+Over the last decade, organizations have been striving to become more agile and data-driven,
seeking to gain competitive advantage in their markets. This trend has led to dramatic changes
in the way applications are built and delivered, and in the type and volume of data that is
being leveraged.
+**Applications**: In previous decades, software development was a carefully orchestrated
and planned process. The release cycles were often measured in years, and upgrades were infrequent.
Today, Web and mobile applications are developed in a much more iterative fashion. The release
cycles are measured in days or weeks, and upgrades are a non-issue. (What version of Salesforce.com
or Google Maps are you using?)
+**Data**: In previous decades, data was measured in MBs or GBs, and it was highly structured
and denormalized. Today's data is often measured in TBs or PBs, and it tends to be multi-structured
— a combination of unstructured, semi-structured and structured. The data comes from many
different sources, including a variety of applications, devices and services, and its structure
changes much more frequently.
+### A New Generation of Datastores
+The relational database, which was invented in 1970, was not designed for these new processes
and data volumes and structures. As a result, a new generation of datastores has emerged,
including HDFS, NoSQL (HBase, MongoDB, etc.) and search (Elasticsearch, Solr).  These systems
are schema-free (also known as "dynamic schema"). Applications, as opposed to DBAs, control
the data structure, enabling more agility and flexibility. For example, an application developer
can independently evolve the data structure with each application release (which could be
daily or weekly) without filing a ticket with IT and waiting for the schema of the databae
to be modified.
+## The Need for a New Query Engine
+With data increasingly being stored in schema-free datastores (HDFS, HBase, MongoDB, etc.)
and a variety of cloud services, users need a way to explore and analyze this data, and a
way to visualize it with BI tools (reports, dashboards, etc.). In 2012 we decided to embark
on a journey to create the world's next-generation SQL engine. We had several high-level requirements
in mind:
+* **A schema-free data model.** Schema-free datastores (HDFS, NoSQL, search) need a schema-free
SQL engine. These datastores became popular for a reason, and we shouldn't expect organizations
to sacrifice those advantages in order to enjoy SQL-based analytics and BI. Today's organizations
need agility and flexibility to cope with the volume, variety and velocity associated with
modern applications and data.  
+* **A standalone query engine that supports multiple data sources.** Most companies now use
a variety of best-of-breed datastores and services to store data. This is true not just for
large Global 2000 companies, but also for small startups. For example, it is not uncommon
for a startup to have data in MySQL, MongoDB, HBase and HDFS, as well as a variety of online
services. ETL was hard even 10 years ago when data was static and 100x smaller than it is
today, and in today's era of Big Data it's often impractical or impossible to ingest all the
data into a single system.
+* **Ease of use.** The SQL engine can't be hard to setup and use. Analysts and developers
should be able to download and use it without deploying any complex infrastructure such as
+* **Scalability and performance.** The SQL engine must support interactive queries. It can't
be batch-oriented like Hive. In addition, it must be able to scale linearly from a small laptop
or virtual machine to a large cluster with hundreds or thousands of powerful servers.
+With these requirements in mind, we decided to incubate a new project in 2012 in the Apache
Software Foundation so that a community of vendors and developers could come together and
develop the technology. (One little known fact is that the name "Drill" was actually suggested
by Google engineers due to its inspiration from Google's Dremel execution engine.)
+After almost two years of research and development, we released Drill 0.4 in August, and
continued with monthly releases since then.
+## What's Next
+Graduating to a top-level project is a significant milestone, but it's really just the beginning
of the journey. In fact, we're currently wrapping up Drill 0.7, which includes hundreds of
fixes and enhancements, and we expect to release that in the next couple weeks.
+Drill is currently being used by dozens of organizations, ranging from small startups to
some of the largest Fortune 100s. These organizations are already gaining tremendous business
value with Drill. As we march towards a 1.0 release early next year, these organizations are
helping us shape the project and ensure that it meets the needs of a broad range of organizations
as well as users (business analysts, technical analysts, data scientists and application developers).
I would like to encourage you to join the ride today by [downloading Drill](http://drill.apache.org/download/)
and [letting us know](mailto:user@drill.apache.org) what you think.
+Happy Drilling!  
+Tomer Shiran
\ No newline at end of file

diff --git a/index.html b/index.html
index b573a9a..fac26ec 100755
--- a/index.html
+++ b/index.html
@@ -1,6 +1,7 @@
 layout: default
 <div id="header" class="mw">
 <div class="nav-circlepop">
@@ -9,18 +10,20 @@ layout: default
 <div class="dots"></div>
 <div class="scroller">
   <div class="item">
     <div class="tc">
       <h1>Apache Drill</h1>
-      <h1 style="font-size:20px">Self-Service Data Exploration</h1>
-      <a href="{{ site.baseurl }}/download/" class="btn btn-1 btn-1c"><span>NOW
+      <h1 style="font-size:20px">Schema-free SQL Query Engine for Hadoop and NoSQL</h1>
+      <a href="{{ site.baseurl }}/download/" class="btn btn-1 btn-1c"><span>DOWNLOAD
 </div><!-- header -->
+<div id="alertbar" style="background-color:#ffc; text-align: center;display: block;padding:10px;
border-bottom: solid 1px #cc9">
+<strong>News:</strong> <a href="{{ site.baseurl }}/blog/2014/12/02/drill-top-level-project/">Apache
Drill Graduates to a Top-Level Project</a> (December 2, 2014)
 <div class="mw introWrapper">
   <table class="intro" cellpadding="0" cellspacing="0" align="center" width="940">
@@ -46,11 +49,11 @@ layout: default
   <h2>Apache Drill is an open source, low latency SQL query engine for Hadoop and NoSQL.</h2>
   <p>Modern big data applications such as social, mobile, web and IoT deal with a larger
number of users and larger amount of data than the traditional transactional applications.
The datasets associated with these applications evolve rapidly, are often self-describing
and can include complex types such as JSON and Parquet. Apache Drill is built from the ground
up to provide low latency queries natively on such rapidly evolving multi-structured datasets
at scale.</p>
   <a name="agility" class="anchor"></a>
-  <h1>Day-Zero Analytics &amp; Rapid<br>Application Development</h1>
+  <h1>Day-zero analytics &amp; rapid<br>application development</h1>
   <!-- <h2>Evolution towards Self-Service Data Exploration</h2> -->
-  <img src="images/home-img1.jpg" alt="Day-Zero Analytics & Rapid Application Development"
+  <img src="images/home-img1.jpg" alt="Day-zero analytics & rapid application development"
-  <p>Apache Drill provides direct queries on self-describing and semi-structured data
in files (such as JSON, Parquet) and HBase tables without needing to specify metadata definitions
in a centralized store such as Hive metastore. This means that the users can explore live
data on their own as it arrives on Hadoop versus spending weeks or months on data preparation,
modeling and ETL and subsequent schema management.</p>
+  <p>Apache Drill provides direct queries on self-describing and semi-structured data
in files (such as JSON, Parquet) and HBase tables without needing to define and maintain schemas
in a centralized store such as Hive metastore. This means that  users can explore live data
on their own as it arrives versus spending weeks or months on data preparation, modeling,
ETL and subsequent schema management.</p>
   <a name="flexibility" class="anchor"></a>
   <h1>Purpose-built for semi-structured/nested data</h1>
   <!-- <h2>A Flexible Data Model for Modern Apps</h2> -->

View raw message