[jira] [Commented] (PIG-4247) S3 properties are not picked up from core-site.xml in local mode

["Daniel Dai (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PIG-4247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546631#comment-14546631 ] 

Daniel Dai commented on PIG-4247:
---------------------------------

The patch break the local mode in some cases. Will create a new ticket for it.

> S3 properties are not picked up from core-site.xml in local mode
> ----------------------------------------------------------------
>
>                 Key: PIG-4247
>                 URL: https://issues.apache.org/jira/browse/PIG-4247
>             Project: Pig
>          Issue Type: Bug
>            Reporter: Cheolsoo Park
>            Assignee: Cheolsoo Park
>             Fix For: 0.15.0
>
>         Attachments: PIG-4247-1.patch
>
>
> Even in local mode, {{fs.s3}} properties need to be set if the job accesses s3 files (for eg, registering jars on s3, loading input files on s3, etc). In particular, {{fs.s3.awsSecretAccessKey}} and {{fs.s3.awsAccessKey}} are usually set in {{core-site.xml}}, but since local mode doesn't load {{core-site.xml}}, these properties have to be set again in pig.properties. This adds operational overhead because whenever rotating aws keys, {{pig.properties}} also needs to be updated. So it would be nice if {{fs.s3}} properties can be set even in local mode.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)