drill-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tshi...@apache.org
Subject [02/50] [abbrv] drill git commit: Blog post update
Date Fri, 01 May 2015 18:07:58 GMT
Blog post update


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

Branch: refs/heads/gh-pages
Commit: 12c8c2f7ee54b79c6b6687793890e003daae4816
Parents: 4ea5e80
Author: Tomer Shiran <tshiran@gmail.com>
Authored: Wed Apr 29 14:37:30 2015 -0700
Committer: Tomer Shiran <tshiran@gmail.com>
Committed: Wed Apr 29 14:37:30 2015 -0700

----------------------------------------------------------------------
 blog/_posts/2015-05-04-drill-0.9-released.md | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/drill/blob/12c8c2f7/blog/_posts/2015-05-04-drill-0.9-released.md
----------------------------------------------------------------------
diff --git a/blog/_posts/2015-05-04-drill-0.9-released.md b/blog/_posts/2015-05-04-drill-0.9-released.md
index 23c868a..20e5ca4 100644
--- a/blog/_posts/2015-05-04-drill-0.9-released.md
+++ b/blog/_posts/2015-05-04-drill-0.9-released.md
@@ -7,10 +7,13 @@ authors: ["tshiran", "jnadeau"]
 ---
 It has been about a month since the release of Drill 0.8, which included [more than 240 improvements]({{
site.baseurl }}/blog/drill-0.8-released/). Today we're happy to announce the availability
of Drill 0.9, providing additional enhancements and bug fixes. In fact, this release includes
[199 resolved JIRAs](https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313820&version=12328813).
Some of the noteworthy features in Drill 0.9 are:
 
-* **Authentication** ([DRILL-2674](https://issues.apache.org/jira/browse/DRILL-2674)). Drill
now supports username/password authentication through the Java and C++ clients, as well as
JDBC and ODBC. On the server-side, Drill leverages Linux PAM to securely validate the credentials.
Users can choose to use an external user directory such as Active Directory or LDAP. To enable
authentication, set the `security.user.auth` option in `drill-override.conf`. 
+* **Authentication** ([DRILL-2674](https://issues.apache.org/jira/browse/DRILL-2674)). Drill
now supports username/password authentication through the Java and C++ clients, as well as
JDBC and ODBC. On the server-side, Drill leverages Linux PAM to securely validate the credentials.
Users can choose to use an external user directory such as Active Directory or LDAP. To enable
authentication, set the `security.user.auth` option in `drill-override.conf`.
 * **Impersonation** ([DRILL-2363](https://issues.apache.org/jira/browse/DRILL-2363)). Queries
now execute and access resources using the identity of the user who submitted the query. Previously,
all queries would run as the same user (eg, `drill`). With the new impersonation capability,
the query will fail if the submitting user does not have permission to read the requested
file(s) in the distributed file system. To enable impersonation, set the `drill.exec.impersonation`
option in `drill-override.conf`.
+* **Ownership chaining**. Drill now allows views with different owners to be chained. This
represents a very flexible access control solution. For example, an administrator with access
to raw, sensitive data could create a view called `masked` which would expose only a subset
of the data to other users. The administrator would enable users to read the `masked` view
but not the raw data. Note that Drill provides an option `max_chained_user_hops` that specifies
how many ownership changed are allowed in a chain, thereby providing administrators (or data
stewards) more control over sharing of data.
+* **Extended JSON datatypes**. Our friends at MongoDB invented [extended JSON](http://docs.mongodb.org/manual/reference/mongodb-extended-json/)
- a set of extensions to the JSON format for supporting additional data types. We decided
to embrace extended JSON in Drill. For example, standard JSON doesn't have a time type, so
a time could be represented as either a string or a number: `{"foo": "19:20:30.450Z"}` is
just a string. With extended JSON, the `$time` qualifier can be used to specify that `foo`
is a time `{"foo": {"$time": "19:20:30.450Z"}}`.
+  We now support a number of qualifiers including `$bin`, `$date`, `$time`, `$interval`,
`$numberLong` and `$dateDay` (see [the example](https://github.com/apache/drill/blob/master/exec/java-exec/src/test/resources/vector/complex/extended.json)).
We're in the process of adding some additional qualifiers to make sure that all of MongoDB's
extended types are supported (this is particularly important when querying data in MongoDB).
 * **Improved error messages** ([DRILL-2675](https://issues.apache.org/jira/browse/DRILL-2675)
and more). It can be challenging for a complex distributed system like Drill to translate
low-level internal conditions into actionable messages to the user. This release includes
several enhancements that enable Drill to accomplish just that in a variety of cases.
-* **Parquet and Calcite enhancements** ([DRILL-1410](https://issues.apache.org/jira/browse/DRILL-1410)
and [DRILL-1384](https://issues.apache.org/jira/browse/DRILL-1384)). Drill isn't a traditional
query engine. It's the first analytical query engine with a JSON data model. It utilizes a
shredded, columnar, in-memory representation of complex data, and automatically compiles and
re-compiles queries on-the-fly during execution based on the actual data (we sometimes call
this 'schema discovery on-the-fly'). These unique capabilities have required us to enhance
Parquet (our columnar format) and Calcite (our SQL parser). These enhancements have now been
contributed back to those projects, and Drill is using the latest versions which include these
enhancements.
+* **Parquet and Calcite enhancements** ([DRILL-1410](https://issues.apache.org/jira/browse/DRILL-1410)
and [DRILL-1384](https://issues.apache.org/jira/browse/DRILL-1384)). Drill isn't a traditional
query engine - it's the first analytical query engine with a JSON data model. This has required
us to enhance Parquet (our columnar format) and Calcite (our SQL parser). These enhancements
have now been contributed back to those projects, and Drill is using the latest versions which
include these enhancements.
 * **Avro support** ([DRILL-1512](https://issues.apache.org/jira/browse/DRILL-1512)). Drill
can now read Avro files. This patch was contributed by Andrew Selden at Elastic.co (formerly
known as Elasticsearch).
 * **New sys tables for memory and thread information** ([DRILL-2275](https://issues.apache.org/jira/browse/DRILL-2275)).
Drill includes two new `sys` tables that provide real-time metrics about memory utilization
and threads on each of the nodes in the cluster. You can run a simple `SELECT *` to see what
information is available:
 


Mime
View raw message