[GitHub] nifi pull request #257: NIFI-1537 Added SNMP processors

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/257 --- 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

[GitHub] nifi issue #257: NIFI-1537 Added SNMP processors

Github user olegz commented on the issue: https://github.com/apache/nifi/pull/257 @pvillard31 Had a merge conflict again, but fixed it myself. Nothing to do, just making comment for traceability. --- If your project is set up for it, you can reply to this email and have your reply

[GitHub] nifi issue #272: NIFI-1620 Allow empty Content-Type in InvokeHTTP processor

Github user JPercivall commented on the issue: https://github.com/apache/nifi/pull/272 Thanks for the assist @apiri --- 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

[GitHub] nifi issue #398: NIFI-1751 Added proxy authentication in InvokeHttp processo...

Github user apiri commented on the issue: https://github.com/apache/nifi/pull/398 Hey @pvillard31, I did a review of this and it seems to work mostly well using Squid with the following config: ``` auth_param basic program

[GitHub] nifi pull request #397: NIFI-1815

Github user jdye64 commented on a diff in the pull request: https://github.com/apache/nifi/pull/397#discussion_r67618912 --- Diff: nifi-nar-bundles/nifi-ocr-bundle/nifi-ocr-processors/src/test/resources/tessdata/tessconfigs/nobatch --- @@ -0,0 +1 @@ + --- End diff --

Re: Target version for new procesors

Thanks Joe and Andre -- this definitely helps point me in the correct direction. On Fri, Jun 17, 2016 at 6:19 PM, Andre wrote: > Andrew, > > If you plan to submit it as a PR I would say go with 1.0 (I have been doing > that). > > The wrapping up of 0.7 is at full steam

[GitHub] nifi issue #321: Nifi 1214

Github user ToivoAdams commented on the issue: https://github.com/apache/nifi/pull/321 This closes #321 --- 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,

[GitHub] nifi pull request #321: Nifi 1214

Github user ToivoAdams closed the pull request at: https://github.com/apache/nifi/pull/321 --- 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

[GitHub] nifi issue #321: Nifi 1214

Github user ToivoAdams commented on the issue: https://github.com/apache/nifi/pull/321 Yes, this replaced by #388 --- 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

[GitHub] nifi pull request #414: NIFI-1843 Default log level for LogAttribute.

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/414 --- 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

[GitHub] nifi issue #414: NIFI-1843 Default log level for LogAttribute.

Github user apiri commented on the issue: https://github.com/apache/nifi/pull/414 @ijokarumawak Thanks for addressing this. Verified build and contrib locally and will merge. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub