[drill-site] branch asf-site updated: edits

[br...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

bridgetb 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 b6e783f  edits
b6e783f is described below

commit b6e783fc3d5d1c3e4a0706fb50762ae05e867529
Author: Bridget Bevens <bb...@maprtech.com>
AuthorDate: Thu Jan 10 16:08:00 2019 -0800

    edits
---
 docs/s3-storage-plugin/index.html | 11 +++++------
 feed.xml                          |  4 ++--
 2 files changed, 7 insertions(+), 8 deletions(-)

diff --git a/docs/s3-storage-plugin/index.html b/docs/s3-storage-plugin/index.html
index 94b0748..7de8525 100644
--- a/docs/s3-storage-plugin/index.html
+++ b/docs/s3-storage-plugin/index.html
@@ -1295,7 +1295,7 @@
 
     </div>
 
-     Jan 10, 2019
+     Jan 11, 2019
 
     <link href="/css/docpage.css" rel="stylesheet" type="text/css">
 
@@ -1376,7 +1376,7 @@
 
 <h3 id="using-an-external-provider-for-credentials">Using an External Provider for Credentials</h3>
 
-<p>Starting in Drill 1.15, the S3 storage plugin supports the <a href="https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-common/CredentialProviderAPI.html%5D">Hadoop Credential Provider API</a>, which allows you to store secret keys and other sensitive data in an encrypted file in an external provider versus storing them in plain text in a configuration file or directly in the storage plugin configuration.</p>
+<p>Starting in Drill 1.15, the S3 storage plugin supports the <a href="https://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/CredentialProviderAPI.html">Hadoop Credential Provider API</a>, which allows you to store secret keys and other sensitive data in an encrypted file in an external provider versus storing them in plain text in a configuration file or directly in the storage plugin configuration.</p>
 
 <p>When you configure the S3 storage plugin to use an external provider, Drill first checks the external provider for the keys. If the keys are not available via the provider, or the provider is not configured, Drill can fall back to using the plain text data in the <code>core-site.xml</code> file or S3 storage plugin configuration. </p>
 
@@ -1426,8 +1426,7 @@ Add the bucket name and the <code>hadoop.security.credential.provider.path</code
 <p>Whether you store credentials in the S3 storage plugin configuration directly or in an external provider, you can reconnect to an existing S3 bucket using different credentials when you include the <code>fs.s3a.impl.disable.cache</code> property in the S3 storage plugin configuration. The <code>fs.s3a.impl.disable.cache</code> property disables the S3 file system cache when set to &#39;true&#39;. If <code>fs.s3a.impl.disable.cache</code> is set to &#39;false&#39; when Drill reconnects [...]
 
 <p>The following example S3 storage plugin configuration includes the fs.s3a.impl.disable.cache property:</p>
-
-<p>{
+<div class="highlight"><pre><code class="language-text" data-lang="text">{
  &quot;type&quot;:
 &quot;file&quot;,
   &quot;connection&quot;: &quot;s3a://bucket-name/&quot;,
@@ -1438,8 +1437,8 @@ Add the bucket name and the <code>hadoop.security.credential.provider.path</code
     },
   &quot;workspaces&quot;: {
     ...
-  }</p>
-
+  }
+</code></pre></div>
 <h2 id="quering-parquet-format-files-on-s3">Quering Parquet Format Files On S3</h2>
 
 <p>Drill uses the Hadoop distributed file system (HDFS) for reading S3 input files, which ultimately uses the Apache HttpClient. The HttpClient has a default limit of four simultaneous requests, and it puts the subsequent S3 requests in the queue. A Drill query with large number of columns or a Select * query, on Parquet formatted files ends up issuing many S3 requests and can fail with ConnectionPoolTimeoutException.   </p>
diff --git a/feed.xml b/feed.xml
index 64765a0..a8afdbb 100644
--- a/feed.xml
+++ b/feed.xml
@@ -6,8 +6,8 @@
 </description>
     <link>/</link>
     <atom:link href="/feed.xml" rel="self" type="application/rss+xml"/>
-    <pubDate>Thu, 10 Jan 2019 15:57:08 -0800</pubDate>
-    <lastBuildDate>Thu, 10 Jan 2019 15:57:08 -0800</lastBuildDate>
+    <pubDate>Thu, 10 Jan 2019 16:06:27 -0800</pubDate>
+    <lastBuildDate>Thu, 10 Jan 2019 16:06:27 -0800</lastBuildDate>
     <generator>Jekyll v2.5.2</generator>
     
       <item>