It will not be blocked by penalized things. The queues are setup to
basically put those aside and move on to other things until their
penalty period passes. If you're seeing different behavior please
advise.
Thanks
Joe
On Thu, Sep 1, 2016 at 1:11 PM, McDermott, Chris Kevin (MSDU -
STaTS/Storefro
Thanks, everyone for the feedback. I’ll file a JIRA for this and see if I can
find some time to address it.
Does anyone have any thoughts on my related question?
(with spelling and grammar corrections:)
➢ If a penalized file is routed to a funnel that’s s connect to a processor via
a connectio
Adam,
A PenalizeFlowFile processor could be pretty useful, please feel free
to file a New Feature Jira for this if you like.
In the meantime you could use ExecuteScript (with Groovy for this
example) and the following:
def flowFile = session.get()
if(!flowFile) return
flowFile = session.penalize
In the wild west of HTTP response codes, a 500 Server Error could mean
practically anything. In my experience, you can't infer any semantic
meaning for what a 500 status code could mean, unless you're very familiar
with the server application.
I'd even go so far as to suggest, if a modification i
Sven
If it is being invoked at all you'll see entries in the
nifi/logs/nifi-bootstrap.log. After a restart is there anything there?
If yes and it looks normal check nifi/logs/nifi-app.log and see if it
is dying for some reason.
Thanks
Joe
On Thu, Sep 1, 2016 at 9:38 AM, Sven Davison wrote:
> I
I can run the service via nifi.sh start or sudo service nifi start and all’s
well.. BUT.. it start on its own after reboot.
chkconfig shows it’s on, and systemctl redirects to chkconfig.. but still it
wont start at reboot.
Sent from Mail for Windows 10
Apache NiFi community,
I am pleased to announce that the inaugural release of MiNiFi C++, 0.0.1,
passes with:
7 +1 (binding) votes
4 +1 (non-binding) votes
0 0 votes
0 -1 votes
Thanks to all who helped make this release possible.
Here is the PMC vote thread:
https://li
+1 (binding)
On Wed, Aug 31, 2016 at 4:45 PM, Joe Witt wrote:
> +1 (binding)
>
> hash, signature, licensing, build check out.
>
> Great start for MiNiFi C++!
>
> Thanks
>
> On Thu, Sep 1, 2016 at 3:31 AM, Bryan Rosander
> wrote:
> > Verified GPG, checksums, built with:
> > https://github.com/b
Based on Version Scheme and API Compatibility[1] the recently released 1.0
(congratulations to all) could have some breaking changes for code
written against 0.* releases. I was wondering if there are any resources
about what has broken with the new release? I looked at the release notes
but there
Debug logging can be set in a processor itself in the UI, too.
On Wed, Aug 31, 2016, 5:34 PM James Wing wrote:
> Keren,
>
> Which version of NiFi are you using?
>
> One thing I noticed in your configuration of FetchS3Object is you are
> setting both the Access Key and Secret Key properties with
Keren,
Which version of NiFi are you using?
One thing I noticed in your configuration of FetchS3Object is you are
setting both the Access Key and Secret Key properties with the AWS
Credentials Provider. When you are using the AWS Credentials Provider
Service, you should not specify keys.
A more
Oops, I sent this out to the developer list serve, will send it out to the
Users list serve now.
My bad for flooding your inbox (but if you have suggestions please send
them my way)!
Best,
Keren
On 8/31/16, 4:44 PM, "Tseytlin, Keren"
wrote:
>Hi All!
>
>Looking for some help on enabling Cross A
+1 (binding)
hash, signature, licensing, build check out.
Great start for MiNiFi C++!
Thanks
On Thu, Sep 1, 2016 at 3:31 AM, Bryan Rosander wrote:
> Verified GPG, checksums, built with:
> https://github.com/brosander/dev-dockerfiles/tree/master/minifi/cpp/build/ubuntu
>
> Ran example flow send
Hi All!
Looking for some help on enabling Cross Account communication within Nifi!
My goal: There are files stored from CloudTrail in an S3 bucket in VPC B. My
Nifi machines are in VPC A. I want Nifi to be able to get those files from VPC
B. VPC A and VPC B need to be communicating in the Fetch
Wasn't HTTP 400 Bad Request meant for that? 500 only means the server
failed, not necessarily due to user input.
Andrew
On Wed, Aug 31, 2016, 10:16 AM Mark Payne wrote:
> Hey Chris,
>
> I think it is reasonable to penalize when we receive a 500 response. 500
> means Internal Server Error, and i
Verified GPG, checksums, built with:
https://github.com/brosander/dev-dockerfiles/tree/master/minifi/cpp/build/ubuntu
Ran example flow sending data to local nifi from Ubuntu-based docker
container with only libxml2-dev:
https://github.com/brosander/dev-dockerfiles/tree/master/minifi/cpp/run/ubuntu
Hey Chris,
I think it is reasonable to penalize when we receive a 500 response. 500 means
Internal Server Error, and it is
very reasonable to believe that the Internal Server Error occurred due to the
specific input (i.e., that it may not
always occur with different input). So penalizing the Flo
I wanted to ask if it would be at all sane to have the PostHTTP processor
penalize a flowfile on 5xx response. 5xx indicates that the request may be
good but it cannot be handle by the server Currently it seems the processor
routes files eliciting this response to the failure output but does no
18 matches
Mail list logo
