with the reaction to issues/ bugs etc. in this community.
Regards
Conrad
From: Mark Payne <marka...@hotmail.com>
Reply-To: "users@nifi.apache.org" <users@nifi.apache.org>
Date: Tuesday, 15 November 2016 at 18:09
To: "users@nifi.apache.org" <users@nifi.apache.org>
S
>> Does this help at all?
>> If you need anything else just shout.
>> Regards
>> Conrad
>>
>>
>>
>>
>>
>> additional out of shot
>> · compression level : 1
>> · Keep Path : false
>>
>>
>> From:
oes this help at all?
>> If you need anything else just shout.
>> Regards
>> Conrad
>>
>>
>>
>>
>>
>> additional out of shot
>> · compression level : 1
>> · Keep Path : false
>>
>>
>> From: Ole
; Conrad
>
>
>
>
>
> additional out of shot
> · compression level : 1
> · Keep Path : false
>
>
> From: Oleg Zhurakousky <ozhurakou...@hortonworks.com>
> Reply-To: "users@nifi.apache.org" <users@nifi.apache.org>
> Date: Th
quot;
<users@nifi.apache.org<mailto:users@nifi.apache.org>>
Subject: Re: NPE MergeContent processor
Conrad
Any chance you an provide a bit more info about your flow?
I was able to find a condition when something like this can happen, but it
would have to be with some legacy NiFi dis
@nifi.apache.org<mailto:users@nifi.apache.org>"
<users@nifi.apache.org<mailto:users@nifi.apache.org>>
Date: Thursday, 10 November 2016 at 14:59
To: "users@nifi.apache.org<mailto:users@nifi.apache.org>"
<users@nifi.apache.org<mailto:users@nifi.apache.or
.
Regards
Conrad
From: Bryan Bende <bbe...@gmail.com>
Reply-To: "users@nifi.apache.org" <users@nifi.apache.org>
Date: Thursday, 10 November 2016 at 14:59
To: "users@nifi.apache.org" <users@nifi.apache.org>
Subject: Re: NPE MergeContent processor
Conrad
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,
>
>
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
