You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/09/13 03:31:20 UTC

[jira] [Commented] (NIFI-2763) S3 processors do not work with older S3-compatible object stores

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

ASF GitHub Bot commented on NIFI-2763:
--------------------------------------

GitHub user baank opened a pull request:

    https://github.com/apache/nifi/pull/1008

    NIFI-2763 S3 processors do not work with older S3-compatible object s…

    …tores

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

    $ git pull https://github.com/baank/nifi master

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

    https://github.com/apache/nifi/pull/1008.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 #1008
    
----
commit d62123a3285bdb5d7566799e737a95e7c1b29995
Author: d810146 <na...@team.telstra.com>
Date:   2016-09-13T03:30:12Z

    NIFI-2763 S3 processors do not work with older S3-compatible object stores

----


> S3 processors do not work with older S3-compatible object stores
> ----------------------------------------------------------------
>
>                 Key: NIFI-2763
>                 URL: https://issues.apache.org/jira/browse/NIFI-2763
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 1.0.0
>            Reporter: Franco
>              Labels: easyfix
>             Fix For: 1.1.0
>
>
> In the 1.0.0 release of NiFi it is using the AWS library for connecting to S3 and S3-compatible object stores.
> This library by default expects V4 signer support which if you are using an older object store will not be available and so NiFi will be unusable.
> The fix is simple:
> Allow the user to specify (if they wish) the signer type that AWS library should use.



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