This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/drill-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new f23362b71 Automatic Site Publish by Buildbot
f23362b71 is described below
commit f23362b71255c7ff6b98174685142f3c5fb9c351
Author: buildbot <[email protected]>
AuthorDate: Mon Jan 23 14:00:04 2023 +0000
Automatic Site Publish by Buildbot
---
output/docs/using-the-jdbc-driver/index.html | 8 ++++----
output/feed.xml | 4 ++--
output/zh/docs/using-the-jdbc-driver/index.html | 8 ++++----
output/zh/feed.xml | 4 ++--
4 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/output/docs/using-the-jdbc-driver/index.html
b/output/docs/using-the-jdbc-driver/index.html
index 83e4ebf37..bf1c5e341 100644
--- a/output/docs/using-the-jdbc-driver/index.html
+++ b/output/docs/using-the-jdbc-driver/index.html
@@ -1611,17 +1611,17 @@ System.out.println(rs.getString(1));
<span class="n">ctasResults</span><span class="o">.</span><span
class="na">close</span><span class="o">();</span>
<span class="n">ctasStatement</span><span class="o">.</span><span
class="na">close</span><span class="o">();</span>
</code></pre></div></div>
-<p>then it may be that the CTAS statement is still executing, and that is
unintentionally cancelled before completing depending on good or bad luck with
respect to timing.</p>
+<p>then it may be that the CTAS statement is still executing, and that it is
unintentionally cancelled before completing depending on luck with respect to
timing.</p>
-<p>The cancellation of the CTAS statement is usually benign if it spawned only
one writer fragment, but if it spawned more than one then the chances increase
that at least one writer will be interrupted before it has finished writing,
resulting in incomplete or even corrupted output. Even in the benign case, such
queries conclude in the CANCELLED state rather than the COMPLETED state
resulting in misleading query logs and profiles.</p>
+<p>This unintended cancellation of the CTAS statement is usually benign if it
spawned only one writer fragment, but if it spawned more than one then the
chances increase that at least one writer will be interrupted before it has
finished writing, resulting in incomplete or even corrupted output. Even the
benign cases of such queries conclude in the CANCELLED state rather than the
COMPLETED state resulting in misleading query logs and profiles.</p>
-<p>To have CTAS queries reliably run to completion the JDBC client should wait
for all of the writer fragments to complete before it closes its JDBC resources
by scrolling through the ResultSet before closing it. Using try-with-resources
syntax,</p>
+<p>To have CTAS queries reliably run to completion the JDBC client should wait
for all of the writer fragments to complete by scrolling through the returned
ResultSet before closing it or the Statement that created it. Using
try-with-resources syntax,</p>
<div class="language-java highlighter-rouge"><div class="highlight"><pre
class="highlight"><code><span class="k">try</span> <span class="o">(</span>
<span class="nc">Statement</span> <span class="n">ctasStatement</span> <span
class="o">=</span> <span class="n">conn</span><span class="o">.</span><span
class="na">createStatement</span><span class="o">();</span>
<span class="nc">ResultSet</span> <span class="n">ctasResults</span> <span
class="o">=</span> <span class="n">ctasStatement</span><span
class="o">.</span><span class="na">executeQuery</span><span
class="o">(</span><span class="n">ctasQueryText</span><span class="o">);</span>
<span class="o">)</span> <span class="o">{</span>
- <span class="k">while</span> <span class="o">(</span><span
class="n">ctasResults</span><span class="o">.</span><span
class="na">next</span><span class="o">());</span> <span class="c1">// scroll
through results to ensure that we wait for query completion</span>
+ <span class="k">while</span> <span class="o">(</span><span
class="n">ctasResults</span><span class="o">.</span><span
class="na">next</span><span class="o">());</span> <span class="c1">// scroll
through results to ensure that we wait for CTAS completion</span>
<span class="o">}</span>
</code></pre></div></div>
diff --git a/output/feed.xml b/output/feed.xml
index 03a9afe7c..55d12c48f 100644
--- a/output/feed.xml
+++ b/output/feed.xml
@@ -6,8 +6,8 @@
</description>
<link>/</link>
<atom:link href="/feed.xml" rel="self" type="application/rss+xml"/>
- <pubDate>Sat, 21 Jan 2023 10:25:29 +0000</pubDate>
- <lastBuildDate>Sat, 21 Jan 2023 10:25:29 +0000</lastBuildDate>
+ <pubDate>Mon, 23 Jan 2023 13:57:56 +0000</pubDate>
+ <lastBuildDate>Mon, 23 Jan 2023 13:57:56 +0000</lastBuildDate>
<generator>Jekyll v3.9.1</generator>
<item>
diff --git a/output/zh/docs/using-the-jdbc-driver/index.html
b/output/zh/docs/using-the-jdbc-driver/index.html
index 111386299..d76b253e7 100644
--- a/output/zh/docs/using-the-jdbc-driver/index.html
+++ b/output/zh/docs/using-the-jdbc-driver/index.html
@@ -1611,17 +1611,17 @@ System.out.println(rs.getString(1));
<span class="n">ctasResults</span><span class="o">.</span><span
class="na">close</span><span class="o">();</span>
<span class="n">ctasStatement</span><span class="o">.</span><span
class="na">close</span><span class="o">();</span>
</code></pre></div></div>
-<p>then it may be that the CTAS statement is still executing, and that is
unintentionally cancelled before completing depending on good or bad luck with
respect to timing.</p>
+<p>then it may be that the CTAS statement is still executing, and that it is
unintentionally cancelled before completing depending on luck with respect to
timing.</p>
-<p>The cancellation of the CTAS statement is usually benign if it spawned only
one writer fragment, but if it spawned more than one then the chances increase
that at least one writer will be interrupted before it has finished writing,
resulting in incomplete or even corrupted output. Even in the benign case, such
queries conclude in the CANCELLED state rather than the COMPLETED state
resulting in misleading query logs and profiles.</p>
+<p>This unintended cancellation of the CTAS statement is usually benign if it
spawned only one writer fragment, but if it spawned more than one then the
chances increase that at least one writer will be interrupted before it has
finished writing, resulting in incomplete or even corrupted output. Even the
benign cases of such queries conclude in the CANCELLED state rather than the
COMPLETED state resulting in misleading query logs and profiles.</p>
-<p>To have CTAS queries reliably run to completion the JDBC client should wait
for all of the writer fragments to complete before it closes its JDBC resources
by scrolling through the ResultSet before closing it. Using try-with-resources
syntax,</p>
+<p>To have CTAS queries reliably run to completion the JDBC client should wait
for all of the writer fragments to complete by scrolling through the returned
ResultSet before closing it or the Statement that created it. Using
try-with-resources syntax,</p>
<div class="language-java highlighter-rouge"><div class="highlight"><pre
class="highlight"><code><span class="k">try</span> <span class="o">(</span>
<span class="nc">Statement</span> <span class="n">ctasStatement</span> <span
class="o">=</span> <span class="n">conn</span><span class="o">.</span><span
class="na">createStatement</span><span class="o">();</span>
<span class="nc">ResultSet</span> <span class="n">ctasResults</span> <span
class="o">=</span> <span class="n">ctasStatement</span><span
class="o">.</span><span class="na">executeQuery</span><span
class="o">(</span><span class="n">ctasQueryText</span><span class="o">);</span>
<span class="o">)</span> <span class="o">{</span>
- <span class="k">while</span> <span class="o">(</span><span
class="n">ctasResults</span><span class="o">.</span><span
class="na">next</span><span class="o">());</span> <span class="c1">// scroll
through results to ensure that we wait for query completion</span>
+ <span class="k">while</span> <span class="o">(</span><span
class="n">ctasResults</span><span class="o">.</span><span
class="na">next</span><span class="o">());</span> <span class="c1">// scroll
through results to ensure that we wait for CTAS completion</span>
<span class="o">}</span>
</code></pre></div></div>
diff --git a/output/zh/feed.xml b/output/zh/feed.xml
index 843507afd..ac44b1b54 100644
--- a/output/zh/feed.xml
+++ b/output/zh/feed.xml
@@ -6,8 +6,8 @@
</description>
<link>/</link>
<atom:link href="/zh/feed.xml" rel="self" type="application/rss+xml"/>
- <pubDate>Sat, 21 Jan 2023 10:25:29 +0000</pubDate>
- <lastBuildDate>Sat, 21 Jan 2023 10:25:29 +0000</lastBuildDate>
+ <pubDate>Mon, 23 Jan 2023 13:57:56 +0000</pubDate>
+ <lastBuildDate>Mon, 23 Jan 2023 13:57:56 +0000</lastBuildDate>
<generator>Jekyll v3.9.1</generator>
<item>
