[
https://issues.apache.org/jira/browse/NIFI-2763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496880#comment-15496880
]
ASF GitHub Bot commented on NIFI-2763:
--------------------------------------
Github user jvwing commented on the issue:
https://github.com/apache/nifi/pull/1008
Our current intentions are specific to S3, as are the implementation and
tests, so I would prefer starting with S3 alone and refactoring later if/when
there is demand for a wider option. Also, I think we can provide a stronger
user experience as an S3-specific field, helping users either ignore the field
or pick an appropriate Signer class without Googling for it. Specifically,
* Provide the currently supported class names as examples in the
description text, or
* Present the options in a drop-down list of the S3 signers. Something
similar came up in another PR with respect to server-side encryption and
enforcing signature v4, and I think a list like "Default Signature", "Signature
v4", "Signature v2", would be nice. No, this isn't required, but it seems like
a nice extra for usability (via extra work for you, I admit it's feature creep).
> 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)
