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 bcf09ee edit
bcf09ee is described below
commit bcf09eeb3e5189b3a7c44fc8bb9f25da9964a5fa
Author: Bridget Bevens <[email protected]>
AuthorDate: Fri Dec 21 20:10:48 2018 -0800
edit
---
_docs/connect-a-data-source/plugins/110-s3-storage-plugin.md | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/_docs/connect-a-data-source/plugins/110-s3-storage-plugin.md
b/_docs/connect-a-data-source/plugins/110-s3-storage-plugin.md
index ac693d1..d688576 100644
--- a/_docs/connect-a-data-source/plugins/110-s3-storage-plugin.md
+++ b/_docs/connect-a-data-source/plugins/110-s3-storage-plugin.md
@@ -77,7 +77,8 @@ Starting in Drill 1.15, the S3 storage plugin supports the
[Hadoop Credential Pr
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 `core-site.xml` file or S3 configuration,
unless the `hadoop.security.credential.clear-text-fallback` property is set to
`false`.
-**Configuring the S3 Plugin to use an External Provider**
+**Configuring the S3 Plugin to use an External Provider**
+
Add the bucket name, `hadoop.security.credential.provider.path` and
`fs.s3a.impl.disable.cache` properties to the S3 storage plugin configuration,
as shown in the following example:
{
