[GitHub] nifi issue #321: Nifi 1214

[ToivoAdams]

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 wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request #321: Nifi 1214

[ToivoAdams]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi issue #321: Nifi 1214

[ToivoAdams]

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, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Target version for new procesors

[Andrew Psaltis]

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  and I think targeting it would
> just add to the stress.
>
> On the the other hand, targeting 1.x gives the reviewers the small courtesy
> of extra time to go through your code.
>
> Cheers
> On 18 Jun 2016 05:15, "Andrew Psaltis"  wrote:
>
> > All,
> > With the what appears to be a soon cut of 0.7.0 and 1.0.0 just around the
> > corner, if one were to start on developing a new processor what
> version(s)
> > should be targeted?
> >
> > --
> > Thanks,
> > Andrew
> >
>



-- 
Thanks,
Andrew

Subscribe to my book: Streaming Data 

twiiter: @itmdata 

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

[jdye64]

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 --

@mattyb149 this is an empty configuration file. It can be used in 
conjunction with whitelisting of detected words so I thought it would make 
sense to leave it there in case someone wanted to add unit testing around those 
capabilities at a later time.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[apiri]

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 
/usr/local/Cellar/squid/3.5.19/libexec/basic_ncsa_auth 
/usr/local/etc/squid.passwords
auth_param basic realm proxy
acl authenticated proxy_auth REQUIRED
http_access allow authenticated
http_port 3128
```

and created a proxy user via:
```
htpasswd -c /usr/local/etc/squid.passwords testuser
```

I read through some of your commentary on the ticket and was not able to 
recreate the conditions you were seeing for HTTPS sites.  I tried a few, and 
all seemed to work as anticipated.  I did, however, see the "Too many follow up 
requests" when using wrong credentials (invalid username/password combination). 
 

In terms of handling this, I saw the folks on square/okhttp#2464 
recommended using the `Response.priorResponse()` to track such issues in the 
Authenticator.

Let me know your thoughts on how to address that, but overall functions as 
anticipated and code looks fine.



---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[JPercivall]

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 wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[olegz]

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 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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[asfgit]

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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---