GitHub user NicoK opened a pull request:

    https://github.com/apache/flink/pull/5231

    [FLINK-8346][docs] add v4 signature workaround for manual S3 setups

    ## What is the purpose of the change
    
    As per 
https://lists.apache.org/thread.html/dd59f94d76ae809f83dc36958006974d0a13dc0798856d1d64bb7293@%3Cuser.flink.apache.org%3E,
 we should add a hint to enable signature v4 for older Hadoop versions to work 
with S3 (for the non-shaded S3 file systems and regions only accepting v4, e.g. 
eu-central-1)
    
    ## Brief change log
    
    - extend the `common issues` section's `400: Bad Request` section with a 
better workaround than changing the region
    
    ## Verifying this change
    
    This change is a trivial rework / code cleanup without any test coverage.
    
    ## Does this pull request potentially affect one of the following parts:
    
      - Dependencies (does it add or upgrade a dependency): **no**
      - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: **no**
      - The serializers: **no**
      - The runtime per-record code paths (performance sensitive): **no**
      - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Yarn/Mesos, ZooKeeper: **no**
      - The S3 file system connector: **no**
    
    ## Documentation
    
      - Does this pull request introduce a new feature? **no**
      - If yes, how is the feature documented? **not applicable**


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/NicoK/flink flink-8346

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/5231.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #5231
    
----
commit d3fda9004457d1ae70d91826143192a63b93d55f
Author: Nico Kruber <nico@...>
Date:   2018-01-02T13:06:18Z

    [FLINK-8346][docs] add v4 signature workaround for manual S3 setups

----


---

Reply via email to