nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adam Taft <a...@adamtaft.com>
Subject Re: [GitHub] nifi issue #272: NIFI-1620 Allow empty Content-Type in InvokeHTTP processor
Date Thu, 16 Jun 2016 04:15:13 GMT
I added a comment to the JIRA ticket associated with this pull request.  I
think there should be discussion / buy-in from others on the aestetics of
introducing a new processor property for this edge case.  Instead, I think
the goals of this request could be fulfilled without strictly introducing a
new property, which I think would be a likely improved approach.

https://issues.apache.org/jira/browse/NIFI-1620

Maybe we should postpone this ticket resolution and not merge in 0.7.x
until more discussion has occurred?  I wouldn't want to merge this change
without at least a few nods agreeing to the proposed property.


On Wed, Jun 15, 2016 at 5:05 PM, JPercivall <git@git.apache.org> wrote:

> Github user JPercivall commented on the issue:
>
>     https://github.com/apache/nifi/pull/272
>
>     @taftster I'll let you finish it up tonight if you have time since
> you've already had eyes on it. If you're not able to, I'll take a look
> tomorrow.
>
>
> ---
> If your project is set up for it, you can reply to this email and have your
> reply appear on GitHub as well. If your project does not have this feature
> enabled and wishes so, or if the feature is enabled but not working, please
> contact infrastructure at infrastructure@apache.org or file a JIRA ticket
> with INFRA.
> ---
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message