.
Thanks,
Peter
-Original Message-
From: Joe Witt [mailto:joe.w...@gmail.com]
Sent: Friday, November 9, 2018 2:36 PM
To: dev@nifi.apache.org
Subject: Re: [EXT] Re: New Standard Pattern - Put Exception that caused failure
in an attribute
Peter
Ok cool. So i think we agree on the state
ove the fragileness into NiFi, where it's hard coded until
> the next release.
>
> Thank you,
> Peter
>
> -Original Message-
> From: Joe Witt [mailto:joe.w...@gmail.com]
> Sent: Friday, November 9, 2018 12:23 PM
> To: dev@nifi.apache.org
> Subject: Re: [EXT]
> Sent: Friday, November 2, 2018 11:54 AM
> To: dev@nifi.apache.org
> Subject: RE: [EXT] Re: New Standard Pattern - Put Exception that
> caused failure in an attribute
>
> Dev Team,
>
> I don’t think we've reached a conclusion on this discussion, but would like
> too. I had
: dev@nifi.apache.org
> Subject: RE: [EXT] Re: New Standard Pattern - Put Exception that caused
> failure in an attribute
>
> Dev Team,
>
> I don’t think we've reached a conclusion on this discussion, but would like
> too. I had not done enough research when I originally suggeste
A one week bump on this thread. --Peter
-Original Message-
From: Peter Wicks (pwicks)
Sent: Friday, November 2, 2018 11:54 AM
To: dev@nifi.apache.org
Subject: RE: [EXT] Re: New Standard Pattern - Put Exception that caused failure
in an attribute
Dev Team,
I don’t think we've reached
rom: James Srinivasan [mailto:james.sriniva...@gmail.com]
Sent: Tuesday, October 30, 2018 3:00 PM
To: dev@nifi.apache.org
Subject: Re: [EXT] Re: New Standard Pattern - Put Exception that caused failure
in an attribute
Apologies if I've missed this in the discussion so far - we use the InvokeHTTP
proce
he exception text could be included in an attribute.
>
> Thanks,
> Peter
>
> -Original Message-----
> From: u...@moosheimer.com [mailto:u...@moosheimer.com]
> Sent: Saturday, October 27, 2018 10:46 AM
> To: dev@nifi.apache.org
> Subject: Re: [EXT] Re: New Standa
ache.org
Subject: Re: [EXT] Re: New Standard Pattern - Put Exception that caused failure
in an attribute
Do you really want to mix provenance and data lineage with logging/error
information?
Writing exception information/logging information within an attribute is not a
bad idea in my opinion.
If
t;> files and could grep the error out, but a normal user who checks in on the
>> flow and sees a FlowFile in the error queue will not know what the cause
>> was; this is especially frustrating if retrying the file works without
>> failure the second time... Capturing
ng the error message in an attribute
> makes this easy to find.
> > > >
> > > > One thing I worry about too is adding new relationships to core
> processors. After an upgrade, won't users need to go to each instance of
> that processor and handle the new relation
parate this into its own relationship, I do not think
> > most users would appreciate it being a condition silently not handled by
> > the normal failure path.
> >
> > Thanks,
> > Peter
> >
> > -----Original Message-
> > From: Matt Burgess [mailto:mat
NiFi team, I would not want to encounter this
> > without that.
> >
> > Thanks,
> > Peter
> >
> > -Original Message-
> > From: Mark Payne [mailto:marka...@hotmail.com]
> > Sent: Thursday, October 25, 2018 10:38 PM
> > To: dev@nifi.ap
Burgess [mailto:mattyb...@apache.org]
Sent: Friday, October 26, 2018 10:18 AM
To: dev@nifi.apache.org
Subject: Re: [EXT] Re: New Standard Pattern - Put Exception that caused failure
in an attribute
NiFi (as of the last couple releases I think) has the ability to set
auto-terminating
ripting skills in my NiFi team, I would not want to encounter this without
> that.
>
> Thanks,
> Peter
>
> -Original Message-
> From: Mark Payne [mailto:marka...@hotmail.com]
> Sent: Thursday, October 25, 2018 10:38 PM
> To: dev@nifi.apache.org
> Subject:
Pattern - Put Exception that caused failure in
an attribute
I agree - the notion of adding a "failure.reason" attribute is, in my opinion,
an anti-pattern that should be avoided. Relationships are not a workaround but
rather the preferred approach in this scenario - an attribute I woul
15 matches
Mail list logo
