This is an automated email from the ASF dual-hosted git repository.
bridgetb pushed a commit to branch gh-pages
in repository https://gitbox.apache.org/repos/asf/drill.git
The following commit(s) were added to refs/heads/gh-pages by this push:
new 6d82de1 update doc
6d82de1 is described below
commit 6d82de1a760721abffe4810cf3116bf03dc59319
Author: Bridget Bevens <[email protected]>
AuthorDate: Mon Dec 10 19:07:15 2018 -0800
update doc
---
_docs/sql-reference/sql-commands/071-lateral-join.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/_docs/sql-reference/sql-commands/071-lateral-join.md
b/_docs/sql-reference/sql-commands/071-lateral-join.md
index c123ff0..b33f9c1 100644
--- a/_docs/sql-reference/sql-commands/071-lateral-join.md
+++ b/_docs/sql-reference/sql-commands/071-lateral-join.md
@@ -1,10 +1,10 @@
---
title: "LATERAL Join"
-date: 2018-08-06 23:12:05 UTC
+date: 2018-12-11
parent: "SQL Commands"
---
-**NOTE:** Drill 1.14 provides an early release of lateral join. The lateral
join functionality is disabled by default because feature testing is in
progress. If you want to experiment with lateral joins in your queries, enable
the `planner.enable_unnest_lateral` option using the
[SET]({{site.baseurl}}/docs/set/) command.
+Starting in Drill 1.15, the lateral join functionality is enabled by default.
If you are running earlier versions of Drill, use the
[SET]({{site.baseurl}}/docs/set/) command to enable the
`planner.enable_unnest_lateral` option.
A lateral join is essentially a foreach loop in SQL. A lateral join is
represented by the keyword LATERAL with an inner subquery in the FROM clause,
as shown in the following simple representation:
