reaction to issues/ bugs etc. in this community.
Regards
Conrad
From: Mark Payne
Reply-To: "users@nifi.apache.org"
Date: Tuesday, 15 November 2016 at 18:09
To: "users@nifi.apache.org"
Subject: Re: NPE MergeContent processor
Conrad,
Good news - I have been able to replicate
king with us to give us all we
needed to investigate. And thanks for being patient as we've diagnosed and dug
in.
Cheers
-Mark
From: Oleg Zhurakousky
Sent: Friday, November 11, 2016 2:07 PM
To: users@nifi.apache.org
Subject: Re: NPE MergeContent proces
d
>>
>>
>>
>>
>>
>> additional out of shot
>> · compression level : 1
>> · Keep Path : false
>>
>>
>> From: Oleg Zhurakousky
>> Reply-To: "users@nifi.apache.org"
>> Date: Thurs
ot
> · compression level : 1
> · Keep Path : false
>
>
> From: Oleg Zhurakousky
> Reply-To: "users@nifi.apache.org"
> Date: Thursday, 10 November 2016 at 18:40
> To: "users@nifi.apache.org"
> Subject: Re: NPE MergeContent processor
>
> Co
users@nifi.apache.org<mailto:users@nifi.apache.org>"
mailto:users@nifi.apache.org>>
Date: Thursday, 10 November 2016 at 18:40
To: "users@nifi.apache.org<mailto:users@nifi.apache.org>"
mailto:users@nifi.apache.org>>
Subject: Re: NPE MergeContent processor
Conrad
Any
mailto:users@nifi.apache.org>>
Date: Thursday, 10 November 2016 at 14:59
To: "users@nifi.apache.org<mailto:users@nifi.apache.org>"
mailto:users@nifi.apache.org>>
Subject: Re: NPE MergeContent processor
Conrad,
Thanks for reporting this. I wonder if this is also rela
.
Regards
Conrad
From: Bryan Bende
Reply-To: "users@nifi.apache.org"
Date: Thursday, 10 November 2016 at 14:59
To: "users@nifi.apache.org"
Subject: Re: NPE MergeContent processor
Conrad,
Thanks for reporting this. I wonder if this is also related to:
https://issues.apache.
Conrad,
Thanks for reporting this. I wonder if this is also related to:
https://issues.apache.org/jira/browse/NIFI-2015
Seems like there is some case where the UUID is ending up as null.
-Bryan
On Wed, Nov 9, 2016 at 11:57 AM, Conrad Crampton <
conrad.cramp...@secdata.com> wrote:
> Hi,
>
> I
Hi,
I saw this error after I upgraded to 1.0.0 but thought it was maybe due to the
issues I had with that upgrade (entirely my fault it turns out!), but I have
seen it a number of times since so I turned debugging on to get a better
stacktrace. Relevant log section as below.
Nothing out of the o
